2 ms·
Tech people (or anyone) controlling the schedule is good in the sense that absolute monarchy is good... if the leader happens to be good. Tech teams are just a
by ethbr0 4y ago
Tech people (or anyone) controlling the schedule is good in the sense that absolute monarchy is good... if the leader happens to be good.
Tech teams are just as capable of dicking around or diving down bullshit rabbit holes that don't deliver value as anyone else.
To parent's point, I find a productive skill is humility: the person on the other side of the desk/screen is assumed to be trying to say something useful, albeit in language or concepts I don't understand.
And specifically, humility whether it's tech or non-tech controlling the schedule: each know something the other doesn't.
- watwut 4y ago> Tech teams are just as capable of dicking around or diving down bullshit rabbit holes that don't deliver value as anyone else. You can dock around even when business controls schedule. It is just different dicking around - you make it seem as if you have done work, but skip on parts like "checking whether you broke something" or "testing it" and waste rest of time in discord. Nevertheless, if actual issue is laziness then it is not that hard to eventually figure it out and address that. Even when tech co tools schedule, business tend to have way more control including political one. And genuinely, both dicking around and rabit holes are minor issues compared to what can happen when people bullshit in software development. The question of schedule control is not about who bulshits tho. It is about systematic motivations and consequences either arrangement has. And business controlling it is in my experience as disastrous as having programmer to do sales.