10 ms·
I’ve been reading some variant of this, for many years. One of the reasons that I hated being a manager, was because the job involved a lot of sitting around,
by ChrisMarshallNY 5y ago
I’ve been reading some variant of this, for many years.
One of the reasons that I hated being a manager, was because the job involved a lot of sitting around, waiting for stuff to happen.
I couldn’t work on my own projects (because I was on paid work time), and it would have been irresponsible, in the extreme, to put myself into the critical path (because it was no guarantee that I would be able to reliably work). I sometimes tasked myself with projects for work, but they were almost always ignored by my company, and that hurt.
I’ve heard that being a soldier in a combat zone is long hours of idleness, punctuated by short periods of terror and stress.
That pretty much describes my time as a manager, without the “terror” part (and the bullets and explosions).
It sucked.
I now work at home, on my own technical tasks. I get a lot done. My personal productivity is through the roof.
I take a lot of breaks. Sometimes, I even nap.
But I don’t have a time clock. I will often start coding, at 6AM (sometimes, before I even get in the shower, after my morning exercise), and will continue to code, until I hit the sack. I often test my software, while I’m sitting in bed, and will enter issues, from my iPad.
When I have a problem that I’m chasing, or I am in the middle of a big implementation phase, I can work for many hours, straight. I will barely come up for air, and I feel absolutely exhausted, when I finally step back (nap time!).
I’m not particularly concerned about a measured life. I get a lot done; far more than I ever did, when I was being paid.
And I’m having a blast.
- dgb23 5y agoI feel you in terms of the hacker lifestyle you’re describing. I often work from home too (1-3d/w). Fully emersed and free, getting a lot done. But I‘ve found going for a >1h walk a day really helps. The body feels more awake, my eyes are more relaxed, my thoughts are reordered and some new inspirations and ideas emerge.
- ChrisMarshallNY 5y agoI start each day, with a 2-mile walk (not today. Lots of snow, but I’ll be getting my exercise, later). I use the time to triage my day. Works a charm.
- bikingbismuth 5y agoI am currently a manager and the few times where I have said “I am going to write part of this solution my team is working on.” Were the times that I got a big pile of management work and blocked the team. I have since learned my lesson.
- sciprojguy 5y ago"A big steaming pile of management work" might be a more apt description... ;-)
- paulcole 5y agoWhat’s the point of earning the money?
- lloydatkinson 5y ago> I sometimes tasked myself with projects for work, but they were almost always ignored by my company, and that hurt. Experienced this on multiple occasions especially recently and it does indeed hurt - especially when you know what a difference it could make to users or fellow developers and it’s ignored or ignored and then some higher up miraculously suddenly invents an identical idea several months down the line. Bonus points if it’s a whole team effort for almost two years that gets more or less scrapped despite the obvious need for it as a dependency for multiple teams.
- analog31 5y agoAs a manager, I quickly realized that trying to be a technical contributor was a subtle and insidious form of micromanagement. Also, I could give myself my pick of the coolest tasks, which was unfair.
- jzwinck 5y agoWhy did you feel that making direct technical contributions was micromanagement?
- qzx_pierri 5y agoNot the person you replied to, but it's because manager's will never truly fit into a project. Most people don't want to go against the manager, or question decisions made by the manager. Even if the manager specifically says "Hey everyone, give me some feedback. Be open and honest" - That's a trap. No one will ever actually do that, because if you bruise your manager's ego, they have the power to make your life a living hell. As someone who has worked with managers who did tried to get too involved in projects, they just become a dictator. Since the manager will play an oversight role in the project, any small issues will be visible to them at all times. Normally, the team could work out small roadblocks on their own to keep stress low. If the manager is involved, they'll often try to "make themselves useful" and slow things down. Let's not even mention manager statements like "Hey guys, let's keep a note of this so we can work on restructuring our processes in case this happens in the future"... (Because everyone loves redrafting SOPs every 2 months, right?). A good manager is one that stays out of the way and lets you do your job. Having a manager on a project kinda feels like that episode of The Office when Michael comes to Jim's party and everyone was just kinda standing around awkwardly.
- indymike 5y agoI've been a hands on contributor and manager for long time. I do three things that seem to make this a lot more functional: 1) I pick what I'm going to work on after the rest of the team picks their tickets. 2) I fix one bug per day, not matter what. 3) HIPPO (HIghest Paid Person's Opinion) is not an acceptable reason to make a decision. It's worked well for me, your milage may vary.
- PragmaticPulp 5y ago> One of the reasons that I hated being a manager, was because the job involved a lot of sitting around, waiting for stuff to happen. As a manager-of-managers, when I hear that a manager is doing "a lot of sitting around, waiting for stuff to happen", it's usually a sign that something has gone wrong. Don't get me wrong: I don't expect everyone to be productive 100% of the day, but if managers are reaching a point where even they feel like they have too much free time then one of two things has happened: 1) The company has grossly over-hired for the workload at hand. If all the tasks are done and the manager couldn't find anything to do if they tried, it's possible that the company just hired way too many people or greatly under-shot their workloads. This really does happen at some companies that get so big and profitable that executives start chasing headcount and having the biggest department they can get away with. You end up with so many managers that most of them spend their days sitting around or, even worse, inventing new and unnecessary work for their teams just to fill time. It's not good. 2) Or: Managers have too narrow of a view of what their job is. Speaking generally (not accusing the parent comment) - This often happens when developers who haven't experienced good management or managerial mentoring get promoted into their own management positions and assume their job is literally just to delegate to the engineers and then check on them until it's done. In non-stagnant tech companies, there is always more for managers to be doing: Reviewing/updating documentation, helping with hands-on testing of the product, observing or interacting with customers to get a deeper understanding of the problem, coordinating with the sales team to get a better understanding of their domain, and the list goes on. Many of these tasks aren't immediately obvious without proper managerial mentorship, and they might be downright foreign if your only experience with managers has been of the delegate-and-wait variety. Personally, my experience was that I was far busier as a manager than I ever was as an IC. IC work is more narrowly scoped and easier to constrain to specific time limits, or get targets and deadlines shifted according to however much work could be done. As a manager, the amount of work that could be done was both never-ending and also extremely varied, comprising tens or maybe hundreds of possible tasks that often needed attention in parallel, combined with the inter-personal demands of managing people and constant hiring.
- vp8989 5y ago"2) Or: Managers have too narrow of a view of what their job is. Speaking generally (not accusing the parent comment) - This often happens when developers who haven't experienced good management or managerial mentoring get promoted into their own management positions and assume their job is literally just to delegate to the engineers and then check on them until it's done. In non-stagnant tech companies, there is always more for managers to be doing: Reviewing/updating documentation, helping with hands-on testing of the product, observing or interacting with customers to get a deeper understanding of the problem, coordinating with the sales team to get a better understanding of their domain, and the list goes on. Many of these tasks aren't immediately obvious without proper managerial mentorship, and they might be downright foreign if your only experience with managers has been of the delegate-and-wait variety." Big companies tend to hire "specialists" to do all those tasks you mentioned, which I think is a mistake. If the purpose of those tasks is to improve the function of product development, which can be rephrased as "make the coders more effective" then each of those people require a high bandwidth communication channel to the coders. You can only have so many people that you communicate a lot with, and so the effectiveness of those people in improving the effectiveness of product development is limited. Their job is to make sure the devs arent working in silos but they all just end up forming their own silos because its simply not practical to have high bandwidth communication with all these different groups of specialists. Im talking about designers, product managers, project managers, user researchers, data analysts etc ... My broader point is that I agree with your vision of what a manager should do but IME it's not how larger companies tend to be structured.
- _n_b_ 5y agoAs a manager, your main job is to make your ICs effective at doing their work. That means you need to be dealing with poor performers, rewarding with outstanding performers, trying to improve uneven performers, managing expectations from your management and shielding your team from the vicissitudes of your bosses as much as possible, fighting for things your team needs while shielding them from the demoralizing realities of working for a big company where HR and IT etc. don’t give two shits about the actual mission (if applicable), keeping an accurate budget, making sure your team is individually recognized for their success but that you take the blame for their failures, responding to changes in direction and getting your team on board, being the face of management even when that’s unpopular, and doing all the other little things required to keep the team going as effectively as possible. There’s a lot of work to do there, and it can be incredibly rewarding when it’s going well and incredibly frustrating when it’s not. It can also mean you have days when your team is working all out to deliver and the only thing you can do is order pizza and keep distractions away. Those are boring, often frustrating days. It’s not for everybody, but that’s what I think a good manager does. I think it’s often easier when you manage a team and aren’t an expert at what they do (although you still need to understand at a relatively deep level), since that minimizes the chances of you trying to dive in and solve the problem.
- deleted 5y ago[deleted]
- gonehome 5y agoYeah, I agree with all of this. Doing this well also requires building relationships with the team and trust. Recognizing little things like how people can be afraid of a project (and that fear can lead to spinning), and how to break things down/prioritize. In software I think there are also system changes that can make individuals happier (often stuff described in books like the Phoenix project and working effectively with legacy code). A lot of which enable the things you described. People are happy when they’re productive and goals are clear/make sense (and they have the space to focus on the work for them) and they get recognized for it.
- ChrisMarshallNY 5y agoYeah, well...the consensus seems to be that I was a decent manager. I hated the job, but they kept me for 27 years, so I guess something went well. Glad it's behind me, though.
- aprdm 5y agoAs a manager I feel my days are always short, I work in a big company and have 1:1s with other departments to develop relationships, to try to influence other team’s roadmaps , to check how other people are doing that used to be on my team and how can I help, to talk with end users, to mentor junior developers… I can pick and choose what I feel has more impact on above. I also have a vision of where I want the team and the company to be and try to get strategies to achieve it. For example, increases pay bands justification, promotions, career ladder, more training budget, paying for software, approve open source usage requests that are blocking someone etc.
- mywacaday 5y agoWell done, sounds like a great setup you've created for yourself. I'm a manager and looking for a financially viable way out/back. I haven't coded since I left college and and have some small ideas for some side projects, has anyone here hired offshore coders for small projects like an addin for outlook etc?
- ChrisMarshallNY 5y agoIt was a long time coming. My stint as a manager helped me to make some great relationships, and I know that I helped a lot of other ICs have great careers, and great personal lives. None of us got rich, and there wasn't a whole lot of crazy (until the last couple of years, when we worked with an American startup, and I couldn't shield my team from the dysfunction). One of my dreams, was to be in a place, where I could create and craft my own work, without having others take steamers onto it. It's personally gratifying, to know that all the "I could do this better if..." stuff was absolutely right. These days, I have to keep the scope small, and, still, no one is getting rich, but I am pretty chuffed with what I'm doing. Can't put a price on that.
- austincheney 5y ago> I couldn’t work on my own projects (because I was on paid work time) The only problem here is an employer claiming ownership of a personal project, assuming the personal project isn’t interfering with employee product delivery and isn’t violating employer security policies. My solution to this is dual employment. My secondary employer has trouble differentiating work time from personal time so they end up with the most liberal IP assignment policies I have ever seen. Everybody, corporate IP attorneys, know this. So, unless it’s making money or an employer wants to lay down a provision patent they won’t fight you on it. They are fully aware the alternatives are moving to another company or to stop innovating. As a result most employers with silently bless the personal projects even on company time. They won’t bless these efforts directly because personal projects on company time or property are ethical violations that legally compel the employer to take ownership and shut it down. That is the last thing anybody wants.
- ChrisMarshallNY 5y agoIt was that (my employers had very good lawyers -especially wrt IP), but also, I felt a great deal of Responsibility towards my company. I know that my attitude is often derided in this crowd, but it was what it was. I did a great deal of work on the side. The job wasn't super-demanding, and I often spent time at my "day job," thinking about the side work; though not actually tapping on a keyboard. Technically, that was a Bozo no-no, but no one got hurt. In fact, a great many people, all over the world, benefitted from it. I was careful to keep my side work to stuff that did not interfere, or compete, with my corporate employer, so there was never a problem.
- austincheney 5y agoMy primary motivation now for personal projects is a silent anti-Dunning/Kruger. As a JavaScript developer everybody wants to tell me how it’s done, what the right way is, and so forth. It’s not worth arguing over because the most incompetent developers tend to be the most vocal ones. I have been writing JavaScript full time for almost 15 years and most corporate JavaScript I see is complete garbage. How do you know what excellent code is? Numbers. Code size, execution time, maintenance time, defect resolution time, test automation capabilities, new feature delivery time, and so forth. For example if your app takes 4 seconds to load and mine takes 50ms I will just assume I am less wrong, but you can’t advocate for that because will cry about code style and frameworks and other bullshit. So silently I write my personal project.
- soldeace 5y agoI have a blast being a senior data scientist, and I've recently turned down a manager role precisely because of the points you raised, despite the better pay. Your comment made me glad of my decision.