Hi All!
Today I'm launching a new project: Bytes of Wisdom. Bytes of Wisdom is where I give you my favourite snippets and bits of wisdom and learnings that I've learned so far in my software journey.
It's all happening primarily over on Instagram, but I'll be sharing them here and writing some additional commentary for DEV.
A big mistake some folks, in all industries, make is following process to the letter. They often don't see the wood for the trees and understand why they're actually doing the process. What was it put in place for? What is it trying to ensure/prevent? Is there a faster way to do this? Is there a more careful way to do this? Ask yourself next time.
Heads up: As with any terse bit of advice, there will be exceptions of course, and subtleties and nuance that can't possibly be captured in a Byte of Wisdom. This has been what I've experienced, I'd love to hear yours in the comments too!
Top comments (2)
I always believe in embracing the process and keep on optimizing the process over a period of time. But what most people do, is to follow the process for the sake of following it, and then patterns start to form in their work/life.
Exactly! Those people are really missing the point. I'd go beyond 'optimising' - even removing it if it becomes redundant etc.