Amit Rathmore has a thought-provoking essay, Recruiting and the Butterfly Effect. His conclusion is that the people closest to the founding team need to be the ones interviewing candidates, so that the newest hires are as close the ideals and capabilities as the original hires. My only quibble with Amit is that this technique does
Recently, a manager asked how he could detect critical thinking skills in candidates. I had to ask him more questions, so I could answer. Here’s what he meant by critical thinking skills: The ability to think through a problem in a certain architectural domain The ability to deal with people across the organization in planning
I had a discussion recently with a manager who was concerned about his developers meeting their milestones. “We have “Code Complete” as a milestone. The developers say they meet it, but that just means they wrote code until the milestone date. The code isn’t complete. I can’t even tell how complete it is.” Ah,
Christian Sepulveda has a lovely post, Guidelines for Being a Strong Job Candidate. Some of his gems (these are all from his post): A prospective employer has no attention span whatsoever. You are selling yourself to an employer. What would make it a “no-brainer” to hire me? Notice his emphasis on communication skills given that
Alan Weiss, author of Million Dollar Consulting, advises consultants to drop the bottom 10% of their work every year. That way you have to force yourself to grow and offer new (frequently more lucrative) offerings. The same advice applies to managers. When I teach management, I explain that managers have three responsibilities: To deliver
If you don’t read developer.*, consider it. Dan has kindly placed an excerpt from Behind Closed Doors: Secrets of Great Management. Enjoy!
Recently, I gave a talk about useful practices–things to consider adopting/adapting in your organization. (I don’t believe in best practices, the idea that something could be best in all situations is just not credible. See UsefulPractices for more discussion. One of the techniques I discussed was creating smoke tests for the build. We started
I taught a bunch of classes this week at the Software Development conference. At one interviewing class, a participant wanted to know, “How do I hear the other half of the conversation?” I asked for clarification, and he said, “Sometimes I feel as if the candidate has only said part of the answer, and if
I met someone at the Software Development conference this week who told me he had too many people to meet with them all–even on a biweekly basis. I asked him how many people he managed. “30.” That’s not a typo; that’s the number between 29 and 31. I asked why he had so many
I met a manager recently who relayed his technique for making sure his testers stayed focused on their jobs. “Our defect-tracking system logs people off after 30 minutes of idle time. If they’re logged off, I know they’re not working.” This was a new one for me. I’ve heard of counting lines of code.