4 ms·
It's a good idea but the whole document comes off as really patronising. I mean - do good engineering teams need to be told to write tests and code review each
by yarper 11y ago
It's a good idea but the whole document comes off as really patronising. I mean - do good engineering teams need to be told to write tests and code review each others work? Do good engineers need to be told that the customer pays their wages?
Good engineers are always focused on delivering value to the customer, and good engineers will always select stable systems rather than be swayed in some kind of hormonal feature porn frenzy.
On top of that, in my experience, humility is not something you have to ask for in an engineer. He or she will be painfully aware of every mistake they make, it's the only thing driving their development.
tl;dr if the head of accounting thought you were a rowdy bunch of code monkeys, then read the agile principles you'd end up with this
- yetanotherjosh 11y agoWe're all always on our way to becoming good engineers. Most of us really aren't good engineers in one way or another. These kind of principles help guide the whole team towards a set of high standards, in which individual team members may be more or less deficient.
- npizzolato 11y agoDo you need to be so negative? Even if everyone agreed that these principles were gold, and I'm sure I know people who don't agree with everything here, it would still be more than worthwhile to say "this is what we think being a good engineer means." I honestly don't know why you would view that document with such disdain.