4 ms·
Reminds me of a software architect accurately and confidently providing the wrong spec and accuse later our team of poor performances in an unnecessarily passio
by sebastianconcpt 3y ago
Reminds me of a software architect accurately and confidently providing the wrong spec and accuse later our team of poor performances in an unnecessarily passioned way in a meeting.
Turned out later the cause was later revealed to be what he specifically asked to be set to wasting a week of efforts in the team.
BTW if you have career advice on how to deal with a situation like that, I'd like to hear.
- varjag 3y agoArchitects are usually not stake holders or your direct line of management. Chide them and explain that someone who can't code shouldn't be calling the shots.
- trashtester 3y agoAny software project where instructions must be followed to the letter, instead of having tech leaders communicating the _intent_ of an activity or component, where details are merely to be seen as suggestions, tend to either fail directly or be extremely wasteful. If the dev team is getting such instructions from someone in a different time zone, and communicate with them only once or twice per week, it gets even worse.