How to beat perfectionism
Get rid of the imaginary punisher who is supposedly standing behind your shoulders watching all that you do and whipping you for each mistake made.
My ramblings about work, indie hacking, and life.
Get rid of the imaginary punisher who is supposedly standing behind your shoulders watching all that you do and whipping you for each mistake made.
From my experience and by observing other companies, I've concluded that the companies who do estimates and set deadlines regularly move slowly as compared to those who don't.
Memories are made in hindsight and memories pick themselves for us. We don't get to pick them. It's beautiful.
Before you mark your PR ready for review, always test it manually as well. It is not the QA’s job. QA's job is to assure quality. Not to test your code. It is the developer’s job to test their code and make sure it’s functional.
We should define a software engineer as someone who does rock-solid code reviews and writes code in their spare time. Not the other way around.
Think of release as a train that features/PRs/developers have to catch. Not as a tool to ship a fix or features. Set a cadence and release. Do not wait for that one last PR to get merged in the trunk to release.