I ran across this blog today titled Wide vs Deep and it got me thinking (which is always a scary thought). The blog is about how programmers are promoted to managers even though the thought processes are different. Managers are wide and shallow and programmers are deep and narrow.
While the article specifically references programmers that get promoted to managers I think it’s appropriate to talk about it since many of us are small business owners. That means that we don’t have managers and programmers. Forgive my poor English when I say, “We is it.” So how do those of us that do both deal with being the programmer and the manager?
I’ll start off with a little bit of my background since I think it explains a lot about me and how I think about things. I grew up in farm country in rural Illinois. My role models growing up were men that with bailing wire, chewing gum and a welder could fix any piece of machinery under the sun. None of them were specialists in anything and had a very wide grasp of reality. They were tenacious and didn’t give up. I think that’s the nature of being a farmer.
I attended an engineering college on the south side of Chicago just blocks away from Comiskey Park (and the Robert Taylor homes but that’s a different story!) where I earned a degree in electrical engineering. Going to a private school was a struggle financially so I co-oped, did internships and worked my way through school in six years. My education ran very deep and narrow in areas related to electrical engineering although you can argue that electrical engineering touches many areas of engineering (thank you very much for that lovely class called thermodynamics, by the way).
By the time I had graduated I had two full years of experience as an engineer and landed a great job solely because of my experience. In my new job working in an industrial environment (steel mills and foundries) there was “the problem.” The problem might be simple or complex, but it was my job to figure it out. One day it might be fixing a glitch in a PLC program, looking at the circuitry of a steel hardness testing station, programming a new labor saving device or doing the load calculations for a new transformer. The solutions involved researching the issue, evaluating the solutions, engineering the solution, getting the approvals to do it, and then do it! I would call that the funnel approach since it starts wide and narrows down considerably towards the end.
As a software developer and the owner of a business with programmer employees I find myself being torn between being wide and deep. I can’t do both at the same time and I can’t switch between the two quickly or easily. When I’m in management mode I just can’t go deep without a transition period. Thankfully, going from programmer to manager is an easier process even though it’s frustrating not being able to finish what I was working on.
From a project management standpoint I don’t need to know the details of the class/module that is being used or modified – I just care that there’s a solution. But the programmer is concerned with the implementation details of that class/module. They couldn’t care less (most of the time) if the customer is 30 days past due on an invoice or what the next project is. They’re too deep into the details to care and, besides, that’s a “management problem”.
If you’re the sole developer in your business, it’s all too easy to miss the details or go too deep into the details too soon. If you’ve ever been thinking about the code at the bidding stage and you’re designing classes or thinking about the details of how you’ll implement the project then you’re probably too into the details too soon.
Likewise, when you’re creating your bid, you can’t just guess at how long or much money a project should be. You need to determine some of the details and maybe do some proof-of-concept programming before creating the bid.
So it’s not just as simple as being wide or deep. You have to manage the process – especially if you’re on your own. Here are some recommendations you can try.
1 When you first start looking at a project don’t go too deep at first. Write down all of the major areas you (as the programmer) will need to take care of without getting into implementation details.
2 Identify those areas that you need to research and do some proof-of-concept programming.
3 Do your research and proof of concept programming but do NOT polish it. Do not spend a lot of time on it, but also code like you’re coming back to it later (which hopefully you will if you’re awarded the bid).
4 Stop and re-evaluate your original major areas and assign values to them and finish your bid.
Once you have been awarded the work, you can use the research and proof-of-concept coding as a starting point. You can start going deep into the details and code but keep in mind that the management of the project is not over yet.
As you gain experience it becomes easier to estimate. You just ‘know’ that it takes a certain amount of time to do some task. You’ve done it before and you know the pitfalls and complications that can arise. (Shameless plug coming) Use a product such as Task Timer to track your time. If you don’t know how much time you spent on projects in the past how can you accurately estimate similar projects in the future?
In a future post I’ll talk about how to climb back out of the pit of details. So what are your thoughts? How do you avoid going too deep too soon?