4 ms·
I'm going to oppose this. Like 20% time, it ends up becoming a negative space and, despite the best intentions behind it, backfiring and making our cultural ene
by michaelochurch 11y ago
I'm going to oppose this. Like 20% time, it ends up becoming a negative space and, despite the best intentions behind it, backfiring and making our cultural enemies stronger. "Agile", at its inception, wasn't the toxic micromanagement nightmare that it has become. We have to be more careful about what we put out there. Implying that 10% of an employee's time for this autonomy ought to be enough is dangerous.
Engineers should be able to improve and maintain the open-source libraries on which they rely whenever they fucking want. Working time, weekend time, 6:20 in the morning, whatever. Four fifths of these fucking companies would run better if they were run by people who actually do the work.
If engineers are managed down to 2-day increments of time instead of 2 months, then you need to fire 90% of your managers because there clearly isn't enough real work for them, so they're micromanaging. No one who is smart enough to write good code should ever have to justify days of his own working time. Fuck that, and fuck the whole shit pile of "Agile" nonsense that forces us to pretend that it's OK when senior engineers have to justify weeks and days of their own working time, often to non-producing "scrum masters" and "product owners".
I realize that this is a well-intended statement, but it's wrong-headed because companies where manifestos and official policies are needed just to shore up an engineer's basic autonomy to do valuable open-source work with his own working time are companies that don't deserve to live.