7 ms·
This is ridiculous. Yes, engineering managers absolutely should understand how to code, and understanding concepts like technical debt, unreliability of estima
by crazygringo 13y ago
This is ridiculous.
Yes, engineering managers absolutely should understand how to code, and understanding concepts like technical debt, unreliability of estimation, etc. goes without saying. And it's awesome for a manager to be familiar enough with the tools and work to be able to implement a quick critical bugfix or similar when unexpectedly necessary.
But if they're a good manager, it's far better for the organization for them to be spending their full time managing. Let coders code and managers manage, as long as they're both good at their jobs. The author's argument makes as much sense as saying a professional baseball coach should be spending 30% of his game time actually playing with his team.
And honestly, this is just BS:
> Once a person stops coding for a significant portion of time, critical connections to the concerns of developers atrophy.
Citation needed. It sounds as fake as supposed facts like we only use 10 percent of our brains, or other hogwash.
- alexandros 13y agoIf you're looking for anecdata, I can tell you that after stopping coding and doing "business stuff" for a while, including the "engineering management" role, I did catch my perspective shifting away from that of a developer, towards that of a business guy. Adding some coding to my routine has helped get that back, besides a number of other benefits.
- nawitus 13y agoI don't quite agree with that. Specialization is a good thing, but having managers and coders seems too much specialization. It leads to the situation where a manager could fix something small in the same time he communicates someone to fix it. Or situations where the manager slowly loses touch with technology. It's not likely someone will "understand" programming over the years without doing it constantly. And over time the manager's value to the team withers away. I like this idea that there are no managers who manage and engineers who engineer. Instead, there's maybe one person who takes the responsibility of managing work, but does programming or other non-managing work the rest of the time. The engineers can also do a bit of managing, but they'll focus on the engineering. The assumption is of course, that managing work can be automated away sufficiently and the team is a not huge. These are realistic assumptions, but are often untrue because of organizatonal flaws (or flaws with the manager). The baseball coach argument doesn't really fit here, because baseball is not reinvented every 5 years. Programming quite often is. A C++ systems programmer probably can't understand much about HTML5 frontend programming. But a manager with C++ background can learn.
- edwinnathaniel 13y agoIt is rarely the fix is "something small" when you have dev-manager leading the team of 5. The actual fix might be small (changing one line), but the real effort to: 1) Make sure there's unit-test, integration-test 2) Make sure nothing breaks 3) Maybe test the deployment script 4) Maybe test the database migration is rather involved. If the dev-manager knows all of these steps then sure, why not. But that's like saying that QA should be able to do the same thing too (after all, QA should be a little bit more technical and more in-depth than the dev-manager). While these are nice, I rarely see them work like that. I'm not against it, but I just don't think that there is "simple fix" when a dev-manager present (because it implies the size of the project and the size of the software).
- drdeadringer 13y agoI am reminded of a chart of sorts that described "what the software engineer forgot" when describing how long a task would take. "Oh that's 5 minutes." You forgot logging in, powering on the computer, searching for the particular lines of code, a quick test that the fix didn't break anything, and then [if applicable] shunting over to version control.
- nawitus 13y agoWell, I didn't say that every project and every change is something small. I said that there's a subset of changes that are sufficiently small and don't even require new tests (like some small stylesheet change). I think it's rather strange to claim that small fixes don't exist at all.
- Kluny 13y agoEven a stylesheet change could require the dev manager to pull down a local copy of the site, get it running locally, make the change, then push it - that could take days if something goes wrong. For an engineer who already has a local working copy, it really is a quick change. Of course, it would be very quick if he simply edited the live code - but I, for one, would have some very stern words for a manager who thought he could get away with doing that.
- jasallen 13y agoYour argument sounds good in theory, but a lot of us have the experience that 'good managers' are unicorns. Before my start-up, I was a dev manager. And a damn good developer. I knew what technical difficulties my team had, and understood them, because I was the first place they came for an extra set of eyes. I ran defense from upper management because I knew the concerns, and I was the one with the voice. Because I'm also an open-book style manager I didn't play the "they don't need to know" card, but I could handle those things without them first having to mount a case to me every time. I've watched A LOT of "I used to code" managers, and almost to a man, they are a disasters.
- dxbydt 13y agoExactly this. If you are a PM at a Valley outfit & can't code right now, your team simply pretends to respect you, while going off & doing its own thing. Its just one of those empirical things. Doesn't matter if you "used to code" once upon a time. Things are moving at a breakneck pace & if you don't keep up, you are really going to get left behind. I will also say that if you are a PM at a non-Valley outfit like a bank or one of those outsourcing firms, the exact opposite holds true. You should probably not code & spend all of your time managing. IBs especially frown at MDs & VPs taking on hands-on roles instead of managing & filling out gantt charts. My Manager at Goldman used to write compilers using javacc to automate risk algebras - he regularly got the stink eye. He used to tell me "they just want me to run the spreadsheets" :)
- badclient 13y agoBeing able to code is very different from coding 30% of your time at work.
- peterwwillis 13y agoSeriously. A manager is responsible for controlling, administering and maintaining the work being done by their subordinates. A big chunk of that is determining what work is yet to be done, if it's on time, what needs to be done to support the existing work, communicating with other teams, doing research, quashing harmful discourse and building morale. They organize, prioritize and double-check the tasks assigned and meet with their subordinates to ensure everything is going smoothly. They plan, develop, monitor, communicate, and assess their employees and their work. And of course they attend countless, constant meetings. If as a manager you can do all that and then have 2.5-3.5 hours a day left to write code, bravo.
- eagsalazar2 13y agoI really think you are failing to recognize that to actually understand technical issues managers need to code. Most managers are terrible at their jobs precisely because they are totally out of touch with these technical realities. At best they are clueless. At worst managers actually think they know better than their engineers and develop a hostile relationship with them.
- malbiniak 13y agoAs a manager who doesn't spend any time developing, this was the last response I expected to see here. You even stole my coach/player metaphor.
- joeblau 13y agoThe coach/player metaphor is an extremely weak analogy for Software Engineering. Sports aren't changing nearly as rapidly as software engineering is. If you don't watch a soccer/basketball/football/baseball for 10 years and come back, it's basically the same game. The last 10 years of software engineering have changed so much with mobile, map-reduce, responsive design, P/B/S/I/A - aaS offerings, dev-ops tools, cloud computing systems, new languages, etc... I remember a specific example of a manager I had (great Guy) who wanted to build a searchable database of public certificates. When he asked me about what we should build, I said -- Just make one search box (like Google) and allow them to type in whatever they want and we can do the parsing on the backend. He counters saying, well I think we should go with the 50+ input form (That's what he was used to building on all of his old projects). If it was now, I would definitely be more vocal about his software design decisions because he was just rusty and not in touch with the current state of design/dev. I actually got permission to build both interfaces, since it wasn't really much work to build the single search box, and 95% of the usage came though the single search box. I don't think managers need to program, but they need to be doing the equivalent of watching tape, studying other teams, understanding new/changing game rules, learning tradeoffs of different equipment, and keeping up with their domain. All of my experiences with managers that are active in the development community have been amazing. Managers that weren't have always been terrible.
- fingerprinter 13y ago>The coach/player metaphor is an extremely weak analogy for Software Engineering. Sports aren't changing nearly as rapidly as software engineering is. If you don't watch a soccer/basketball/football/baseball for 10 years and come back, it's basically the same game. The last 10 years of software engineering have changed so much with mobile, map-reduce, responsive design, P/B/S/I/A - aaS offerings, dev-ops tools, cloud computing systems, new languages, etc... Watching? perhaps. Coaching? No. And that is why I don't think the analogy is weak. I'm very familiar with two sports, basketball and football. I'm intimately familiar with football. The subtle changes that most fans, particularly casual fans, don't see is what makes coaches who they are and what makes great coaches worth their weight in gold. Not to mention coaches that can get the most out of specific skillsets of players[1]. As just one example. The pistol became all the rage last year with several running QBs running it for their teams. The good teams could, for the most part, coach their players on this style of offense and how to counter it. It was a different style of offense that wasn't used in the NFL and the teams and players had to react...the coaches had to to actually coach them on how to play the zone reads etc etc. Even further, a coach has to be ready to adapt mid-game, mid-drive and in situations. Game conditions dictate them be ready for quite a bit and ready to coach up their players at an instant...or better still...have previously coached them on such a situation. The game, to the fan, might look the same, but not to the coaches. This is why for people who are familiar with coaching and managing software, they do hold up. Both are at their core about leading a group of people to a common goal, articulating the goal, the way and (sometimes) the how. So, in summation, you still don't want your coach running routes. You want your coach getting ready for the game and coaching everyone in that manner. [1] - I mentioned specific skillsets of players. The pistol was an example of this. You have young, inexperienced mobile QBs who can do a few things well. You adapt to their skills b/c you know, while they have potential, they don't have Peyton Manning's situational football IQ yet (if ever) and ability to read defenses. So you simplify, mold the system around their skills. Good managers do this with developers as well. A manager is not going to just "off you go" to a developer. They need to know strengths and weaknesses. Even with my experienced managers, directors and such, I have a firm grasp on personalities, trigger points, strengths and weaknesses.
- hkarthik 13y ago> The author's argument makes as much sense as saying a professional baseball coach should be spending 30% of his game time actually playing with his team. This is a bad comparison because baseball hasn't significantly changed in the last 100 years, but software development changes significantly every 5 year to 10 years. Over a 40 year career in software development, a typical person will see major fundamental shifts at least 4-5 times. So yes, if you are directly managing engineers, you should be coding at least some of the time. If you can't or don't want to contribute code, you should quickly move into upper management and focus on coaching middle managers.
- gaius 13y agoNo he won't. He'll see the same shift 4-5 times with different marketing buzzwords attached. Anyone who got his first management job managing "systems programmers" 40 years ago will be perfectly au fait with "devops" today. Anyone who did ASN.1 will be perfectly comfortable with XML or JSON. Anyone who did IMS will be perfectly comfortable with NoSQL (in fact anyone who did IMS in the 70s would find MongoDB laughably primitive). I could go on and on...
- hkarthik 13y agoYou're specifically focused on technologies, which I will admit don't change that fundamentally from generation to generation. But the way software gets built, deployed, and used has changed a lot.
- gaius 13y agoIBM was doing virtual machines in the 1970s too. Thin client, which is all a web browser is, has been around a long time, in fact a web browser would be recognizable to anyone who had developer for the old 3270 terminals. Or with the client-side execution of scripts, anyone who remembers NeWS from the 1980s. Very, very little in the 2010's is "new", it's just abit shinier this time 'round.
- hkarthik 13y ago
- joeblau 13y agoThe problem that I've found with engineering managers who don't code anymore is that they are stuck in the mindset of the last project they worked on. I've spent a lot of time talking to managers about decisions that they make which I think are poor, but they "know better." They aren't on the front lines when it comes to knowing about libraries, languages, infrastructure and lots of other development related topics. I agree that if managers stayed in their lane, it would be great; but that rarely happens.
- edwinnathaniel 13y agoThis is absolutely what happened in most cases. Once they quit programming back in the 2000 and they did not learn the newer techniques, they're out of touch. A simple example would be when it comes to test automation. Back in the 2000, automating GUI tests with _high_ coverage might be acceptable. Fast forward to today, we all learned that there is a very high cost on end-to-end functional testing that involves complex UI so we tend to write 10% of UI test automation, 20-30% of integration tests, and the rest falls into the unit-testing bucket. That's just the tip of the iceberg. Other areas of improvement ever since: dealing with build, dealing with continuous integration, continuous deployment, source control, etc.
- bowlofpetunias 13y agoYou really believe that programming is such a unique area that people cannot be fully aware of such developments without actually practicing them? Gimme a break. I'm aware of Coffeescript, Backbone, Angular e.a., and I never did one inch of javascript or front-end coding in my life. Hell, the last time I did anything on the client side we were still doing laying with tables and one pixel transparent gifs... Just because it says "manager" on my business card doesn't mean I had my head stuck up my arse since. It may no longer be my job to do, but it's still my job to know.
- edwinnathaniel 13y agoI specifically mentioned "if they did not learn new techniques". By learning, I'm referring to reading, go through some of the examples a little bit, but does not necessary practice the tools. I'm merely agreeing with the parent that there are cases where managers stop reading the tech side and focus solely on the management aspect (risk management vs JS frameworks). If the manager still hold on the traditional approaches, he/she would insist to have more UI test automation as opposed to spend time and invest more on unit-test.
- nthj 13y ago>> Once a person stops coding for a significant portion of time, critical connections to the concerns of developers atrophy. > Citation needed. It sounds as fake as supposed facts like we only use 10 percent of our brains, or other hogwash. I don't have a citation, but this seems obvious to me. It also bears out in my own experiences. Delivering great software requires deep thought and long, uninterrupted periods of concentration [1], and managing requires rapid context switching. When I was lead developer at a web consultancy in Austin, I mostly attended meetings and context-switched between one of dozens of projects. I never had uninterrupted blocks of time to analyze problems deeply. When I left, it took me a good six weeks of coding before I felt I could really push on hard problems again. I had trained my brain to context switch every 5 minutes, and so it expected to keep doing so. I still knew all the syntax, and remembered how everything played together, but breaking business stories down into their component parts was difficult. I couldn't hold the program in my head. [This bears out in the physical world, too: we would not expect a 100-yard sprinter to necessarily be able to run marathons.] [1] Holding a Program in One's Head | http://paulgraham.com/head.html http://paulgraham.com/head.html
- bowlofpetunias 13y agoAgree 100%. Spending 30% of my time coding is just self-indulgent. My team knows I can code, knows I understand their work, and they need me to do the crap they can't afford to deal with, so they can focus on coding. Also, I'm way to unreliable as a coder because my work can be interrupted at any time. Time blocking a few hours doesn't work, because being a developer is not just writing code for a few hours. If I want to code in production, I have to participate in code reviews, handle pull request, take part in ad hoc discussions. Otherwise I'm just a tourist getting in the way. If I want to code as a hobby, I should just do it in my own time.
- dinkumthinkum 13y agoI'm starting to wonder whether managers are really necessary in most programming firms.
- allochthon 13y agoLet coders code and managers manage That's where managers often go wrong; they think a team of developers is something to be shaped. It's more like a movie director and his or her team, and the manager is a producer, providing resources and clearing away obstacles. In a well-functioning team there may be little need for active "managing," and when a manager takes it upon himself to do this, he can get in the way.