September 5, 2002 .net

Bamboo.Prevalence: a .NET object prevalence engine

Here. Bamboo.Prevalence is a "prevalence engine" for .NET. If you don't know what that means (I didn't), you can check out [1], which gives a good intro and then provides a FAQ for the skeptical. In a nutshell: "For many systems it is already feasible to keep all business objects in RAM. ... To avoid losing data, every night your system server saves a snapshot of all business objects to a file using plain object serialization." I admit to still being skeptical after reading the FAQ, but it's mostly a "this feels wrong, I'll think of a reason later" kind of a skepticism. : ) [1] http://www.prevayler.org/wiki.jsp?topic=ObjectPrevalenceSkepticalFAQ
September 5, 2002

Attracting and Keeping Good Folks

Here. .NET Dan [1] asked me for my opinions on attracting and keeping good folks and here is my reply. [1] http://www.dotnetdan.com
September 4, 2002

Gyro! Gyro!

Here. From John Bristowe: Gyro is a set of files that convert an existing installation of the Microsoft Shared Source CLI to support generic type definitions and generic methods. Gyro extends the CLI, ILAsm assembler, and C# compiler. It also includes several samples, documentation (in the form of specifications) and some new tests. It does not support generics in the JScript® compiler.
September 4, 2002 .net

Updated VS.NET Fun Facts

Here. I know I don't organize things well for finding what's new in my list of VS.NET Fun Facts, but if you haven't checked back in a while, I add new tips and tricks all the time. Today I added Nick Hodapp's tip on reducing the amount of time VC7 spends checking included header files for changes and another on Shawn Van Ness's "grokking" of the VS.NET clipboard ring. If you have a fun fact, send it along!
September 4, 2002

CapeScience Release Free WSDL Editor

Here. "Cape Clear Software released a free graphical WSDL Editor for programmers interested in working with Web Services. The WSDL Editor delivers the first complete environment for rapid Web Services Definition Language (WSDL) development. It supports novice programmers, while also providing sophisticated features for more experienced Web Services developers. The Editor includes powerful wizards, which eliminate the complexity of WSDL, as well as WSDL validation which simplifies testing, and support for the rapid creation of Web Services from XML Schema." We're on fire with free XML tools today! This one is cool because it's free and it allows you to define your web service's WSDL first like you should, just like defining your COM interfaces first in the old days. [staff.develop.com/aarons]
September 4, 2002 .net

New .NET Remoting Open Source Project

Here. "We like .NET Remoting and its extensibility model. We want to show the world that you can do some pretty useful (and some weird) things with this model. We also like the ideas behind SOAP and web services but somehow believe that .NET Remoting is a superset of them and offers features which are needed by today's developers." This open source site for .NET remoting extensions continues to grow with a new bi-directional TCP channel to work in firewall environments.
September 4, 2002 tools

Microsoft XML Diff and Patch 1.0

Here. "Microsoft XML Diff and Patch is a set of tools for comparison of two XML documents and application of the changes (patching). XML Diff detect addition, deletion and other changes between two XML documents. It also detects structural changes like a move of a XML subtree. It produces Xml Diff Language Diffgram (XDL diffgram or just diffgram) that describes the differences between the two XML documents. The diffgram can be then used to display these differences or to perform a patch operation using the XML Patch tool." I know that this tool has been sorely needed in the XML community for a while and now MS has released one.
September 4, 2002 spout

Attracting and Keeping Good Folks

A friend of mine requested an essay on my thoughts of attracting and keeping good employees. I’ve had the privilege of working with some of the best and the brightest over the years and seeing how companies hire and keep them. My take is that companies that attract the best do so with a reputation of excellence. As one example, Google has kick-ass technology, so I’m sure most of you want to work there (I know I do : ). On the other hand, there are plenty of companies that have a reputation for buggy, unusable software that turn us off, all without ever hearing about the salary and benefits package.

If you can attract good folks, you’ll also attract lots of mediocre folks and some not-so-good folks. There are all kinds of ways to screen these folks out. My favorite is to ask them why?” questions. If they can tell me the name of the operator that appears as a colon between the last paren of a C++ constructor signature declaration and the opening curly place, that’s great. But if they can tell me why C++ has it, and why Java and C# doesn’t, they’re hired. Of course, I let the interview candidate pick their own area of expertise and ask them questions about what they know best to see how deeply they’ve gone in their explorations. The ability to figure out the why” is a necessary skill for folks that you’re going to trust to take vague requirements and come up with Google-like results in an environment where no two consecutive projects use the same set of technologies (or even similar ones, increasingly).

To select for personality, as well as technology, I like to whip behavior interviewing questions on folks. Instead of sketching a situation for an interviewee, e.g. how would you deal with conflict in the work place?”, behavioral interview questions ask people to remember real situations they’ve been in and how they reacted, e.g. Imagine a time when you had conflict in the work place. How did you handle it?” Everyone knows the right way to handle conflict in the work place, but far fewer of them have handled it properly when it actually happened. The idea of behavioral interviewing is that past behavior indicates future behavior, so if you don’t like that your candidate punched his last manager in the nose, that’s something to find out up front.

Once a good person has been hired, keeping them is a matter of paying them what they’re worth, letting them do what they’re good at, helping them get better at what they’re not so good at, making sure you don’t waste their time on stuff that doesn’t matter, showing appreciation for a job well done and otherwise staying the hell out of their way.


← Newer Entries Older Entries →