5 ms·
> Sounds derogatory to the person you're arguing with. Is that your intention? No, I was referring to the manifesto, and circling back around to my initial com
by dahart 10y ago
> Sounds derogatory to the person you're arguing with. Is that your intention?
No, I was referring to the manifesto, and circling back around to my initial comment on the manifesto. Moreover I did intend for this to be self-deprecating, as I said, I have gotten this wrong in the past and been naive in the same way that I critiqued the manifesto for being naive. I am sharing lessons I've learned the hard way.
> IMO you should've chosen milder language
I'm honestly surprised, saying "I understand" is pretty friggin' mild language... I don't see clearly what your interpretation is or why you're finding it offensive (it sounds like you're finding it offensive?), feel free to clarify.
> you do sound like you were dragged in a meeting, and the mystical they "explained how the real world works" to you, and then you took their side
Well, I am summarizing here. We all are. I can't share the subtleties or make this soft without writing my life story. I do try to extend benefit of the doubt in forum discussions, and I hope to receive the same. I try to assume that people understand there are always corner cases and subtleties we don't have the time to explain.
> 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? I have been an engineer in the past, I have been an engineering manager leading teams inside large businesses, and now I am a (startup) business owner and engineer at the same time. I believe my experience doing both gives me a unique perspective that many engineers who have no business experience lack, and I'm sharing that perspective here. I happened to have come to the conclusions I've written down here while engineering, before I ever became a manager or business owner, but I think my management and business experience only makes my case stronger, not weaker.
The manifesto reads as if it was written by an engineer who has no business perspective, and my issue with it is not that it was strongly worded, it is that the goal is misguided. I believe, based on my experience as an engineer and a business person that avoiding timely communication and avoiding budget discussions in the name of a personal definition of "quality" are bad goals that rarely result in actual high quality software that actually helps the business. 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 think the disconnect between managers and programmers always stems from if we should look at the programmers as assembly line workers or craftsmen.
The thing is, this is a fear programmers have that business people, by and large, do not share. 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.
When programmers declare they're not going to participate in estimates, or even just drag their feet and complain that estimates are impossible or inaccurate, and when programmers avoid talking to managers and complain that email is preferable and weekly face time has no point, the programmers are the ones putting themselves in the position of being thought of as assembly line workers.
- 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.