Every software project has to go through this discussion at least once during its lifespan:

– "Shouldn't we automate this process to avoid problems and increase our velocity?"

– "Nah, we don't have time for that. Let's just fix things manually and hope everything works from there."

If you participate in this topic regularly consider switching to a different project or company. Day spent doing manual work is day wasted.

Hard work and manual labor are acceptable to a point.

The problems arise when we start being proud of the hard work we do instead of inventing solutions to prevent it in the first place.

You don't have to be 'hard at work' or get as much done as possible in given time. These skills do not carry value.

Being creative and able to connect the dots to find the most optimal solution is the shit. It's also totally different than being lazy.

To clarify:

- being lazy = not getting much done, not caring about the results, someone else will handle this
- thinking lazy = figuring out how could I achieve the same or better results with less work

Thanks for coming to my TED talk. Now back to work ➡️

@nikoheikkila or stop presenting silly questions to people who don't know how to answer them. #justdoit

@vegai That's a very valid thing to do given the right kind of culture.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!