3 ms·
> I'm honestly surprised, saying "I understand" is pretty friggin' mild language... This was only in context of the rather strawman-like interpretation I devis
by pdimitar 10y ago
> I'm honestly surprised, saying "I understand" is pretty friggin' mild language...
This was only in context of the rather strawman-like interpretation I devised from your original comment. Nothing serious. ;)
> I try to assume that people understand there are always corner cases and subtleties we don't have the time to explain.
Agreed. Apologies for mis-interpretation.
> > But the way you word your responses here makes me think you're more of a business person now and not an engineer.
> Is that somehow bad?
No, not per se. But just tell me this -- didn't you ever had a coding problem that legitimately took weeks to even figure out, let alone solve afterwards? Trust is paramount. We should absolutely try very hard to avoid micro-management, wouldn't you agree?
> Moreover, engineers adding their own unchecked notions of quality is a super common highly documented and much discussed way to incur mountains of technical debt, waste large sums of money, and deliver projects extremely late.
I agree that this is sadly very often the case. My really badly communicated intent here was to implore you to never forget that there are those of us who work better when given bigger breathing room. Nothing else.
> Managers need programmers to work their craft, they generally don't know how to write code, and know it, and broadly speaking they have a deep respect for people that write code.
This hasn't been my experience but yes, it's anecdotal. In my past, while I was still working in an office, the general consensus was that the programmers are "the nerds" and we "need to be put back in reality" and we will somehow go to a dark corner and do something extremely bad if left unchecked for one hour. Needless to say, this didn't work out well. And I am not talking about one organization. I am talking about five past employers.
> ...the programmers are the ones putting themselves in the position of being thought of as assembly line workers.
Mmm, I think this puts the things on the wrong foot and sounds somewhat vengeful.
IMO if programmers are good communicators, are clear and upfront, realists and not grumpy asocial techies only, the need for daily or even weekly standups can be easily eliminated.
- dahart 10y ago> But just tell me this -- didn't you ever had a coding problem that legitimately took weeks to even figure out, let alone solve afterwards? Trust is paramount. We should absolutely try very hard to avoid micro-management, wouldn't you agree? Yes, I've had lots of large problems that took weeks & months to solve, I'd say hundreds in my career so far. And at times I've desperately wanted people to not bother me while I solve them and stop asking for status reports and just trust me. I've argued with PMs so fiercely over this, they've put warnings in my personnel file that followed me for years. I've had jobs where the daily status report for a 1 month project took two hours of work per day, and I tried to explain that the overhead meant it would take a full extra week to complete the job. It didn't matter, and I was wrong, and because I'm stubborn, it took me a long time to realize why I was wrong. I was optimizing for my own experience, and my own efficiency, and not for the team's. That's the problem with the manifesto. Never once have I had a multi-week problem where I delivered the work without either the direction changing or else delivering a solution that was incorrect and had to be partially or completely redone. Never once have I seen another programmer start down the path of a weeks or months long project who didn't require a course correction within days. Usually the problem is incomplete or misunderstood requirements, frequently it is unforseen complexity & unanticipated consequences, sometimes requirements actually change. My experience has been that when a smart, well-intentioned, and trustworthy programmer (including myself) works on a problem without review for more than a week, it has always resulted in delivery of something that didn't solve the problem, because the problem itself was not understood. I now believe it's absolutely critical to continue talking about what the goals are regularly, and what the solution needs to do. Clear communication is harder than it seems, and you can agree completely with someone on very specific implementation details for hours and hours one day, only to find out there was a huge and glaring difference of vision the next day. The efficiency gained by avoiding a 1 hour weekly meeting is lost in very large multiples when the solution is incorrect, and the probability the solution is incorrect is at least proportional to the amount of time it takes to solve. This is why it's a mistake to equate a manager's desire for regular meetings with a lack of trust, and why regular checkins are not micro-management. Micro-managing is when someone tells you how to do your job and hovers constantly and repeatedly requests bad implementations. I've never had a real micro-manager and I suspect they're extremely rare. A weekly or even daily short status report isn't micro-managing. But being asked what you're doing frequently is often mistaken for micro-management, and a lot of programmers think they're being micro-managed when they aren't. > My really badly communicated intent here was to implore you to never forget that there are those of us who work better when given bigger breathing room. Nothing else. I understand completely, and I think this is what the manifesto is saying too. And it's what I want when I'm writing code too. But getting that breathing room and catering to our individual comfort and efficiency doesn't actually help the team as much as you hope, and it can and frequently does do real damage.
- pdimitar 10y agoOne quick meeting a week I handle easily and find common-sensical. 2 hours a day? Absolutely not, and I don't care if you are the Pope, the Illuminati's leader or Zeus himself promising me a minivan full of dollars. That is micro-management and you said it yourself that it retracts from your usefulness to your superiors. Have we forgotten brain context switches penalty? Is there anyone out there who still thinks they are a made-up problem? While you as a manager are in the groove of managing spreadsheets and timelines your entire workday and having a small meeting here and there is mostly not interrupting your overall thought process and vision for the company, a dev being regularly pestered is absolutely destroying their performance. Your job is working with people and the formal tools to manage people -- even if you do 40 small tasks a day you're still mostly on a single reality plane. We need to build mental pictures of a system, simulate how it works, produce a theory what we should do and then start doing it and validating our ideas; 2-3 interruptions on any stage of this process and that forces us back on an entirely different reality plane, and the whole thing goes in flames and we have to rebuild it in our heads again. Very often this leads to forgetting very good ideas on how to address a problem (or add a feature), too. How is that helping you and the organization you manage exactly? This is a somewhat directly measurable loss of productivity. You also admitted this is about trust but also insisted programmers shouldn't treat often check-ins as lack of trust. Well, I can turn this right back at you -- I insist that they are a lack of trust, so please leave me alone; I am a really good professional, I have a lot of skills outside the programming area and I dare to think I have a good chunk of emotional intelligence in me as well. Why is your opinion on this weighing more than mine? I'd say, try me. I'll prove myself to you if you make one compromise about how you work with me. ^ Have you worked with a person like this? I mean, person who actually delivered after being left alone? I've had plenty of such people in my work. (Admittedly, there was also a large number of fakers and posers, of course.) I also strongly disagree that all programmers left alone tend to lose focus and work on made-up issues. Most of them -- sure, you'll never hear me dispute that. All? No. Many of us go through that phase, yes, but you seem to forget that not a small amount of us emerge of the other side of that labyrinth victorious. If (1) you are working on something very tightly integrated with other people's work AND if (2) you all make good progress each day, then I'll agree that quick daily syncs are very valuable, they prevent duplication of efforts or coding against the wrong assumptions. But if the above two conditions aren't satisfied then no, in my eyes it's just the manager forcing a process out of context. That's like insisting the temperature outside is a stable 20^C every day, 365 days a year. The part that's concerning me here is that you seem to want to shoe-horn a singular process on different kinds of people. If you were my supervisor, I'd not be okay with that.