3 ms·
> You can blame Agile/XP but at root I think it has more to do with many developers abhorring tasks other than just writing code. Documents? Meetings? Talking t
by nine_zeros 3y ago
> You can blame Agile/XP but at root I think it has more to do with many developers abhorring tasks other than just writing code. Documents? Meetings? Talking to future end users? Not fun!!
In whatever BS performance review process in your company, are engineers going to be recognized for writing documents, meetings, talking to future and end users?
If yes, engineers will do it. As it stands, in large companies, management just wants engineers to code their life out.
- wldcordeiro 3y agoIn my experience even when you want to do those things more often than not it's management that sees it as a waste of time and wants you to get to coding. So many times we've had to "pivot" in projects because management couldn't be bothered to let us plan any architecture.
- ChikkaChiChi 3y agoI think this is the failure of the project leaders to incorporate usability into the discussion from the outset. It takes a strong will to sit there and say "We can build you what you want, but without at least one pass on usability and optimization, it's going to be fat, slow, and the end users are going to hate it."
- 8n4vidtmkvmk 3y agoDocuments yes, meetings no but also secretly yes. Documents are an artifact you can point to, and getting comments and references also looks good. Managers don't care how many hours you sit in meetings, but if you magically show leadership by driving meetings and somehow document that, then it counts. No one talks to end users though not engineers anyway. We just build dumb things the PMs want.