Here is my approach for any kind of task: 1. If the task can be eliminated, eliminate it. 2. If the task can't be eliminated, automate it. 3. If the task can't be automated, delegate it. 4. If the task can't be delegated, do it yourself manually.
Sometimes documenting a task turns an un-delegatable task into a delegatable task. This may be a part of your plan already, but I think it's worth spelling out.
Really triggered by the 'oh no software engineer with nothing to do' part. Whenever I'm not actively defending slack people start managing for max utilisation and break the whole damn system.
Software architects don't have hands on programming experience. If they ever programmed, there knowledge is outdated, That make them totally irrelevant.
As always fantastic, Johan!
Here is my approach for any kind of task:
1. If the task can be eliminated, eliminate it.
2. If the task can't be eliminated, automate it.
3. If the task can't be automated, delegate it.
4. If the task can't be delegated, do it yourself manually.
Sometimes documenting a task turns an un-delegatable task into a delegatable task. This may be a part of your plan already, but I think it's worth spelling out.
This was excellent, thanks!
Bravo! Excellent talk!
Any Chance that the Documentation presentation that was referenced is posted to the channel?
Im waiting for it too😊 pls release it 🔥
Really triggered by the 'oh no software engineer with nothing to do' part. Whenever I'm not actively defending slack people start managing for max utilisation and break the whole damn system.
I was expecting a more lean engineering approach and automation in a practical way and not an agile approach.
Automation is world
I can't believe this has 13k views.
Boring and nothing new.
Exactly
Software architects don't have hands on programming experience. If they ever programmed, there knowledge is outdated, That make them totally irrelevant.
that's why good architects keep on programming...