Sr. Software Engineer @Spotify | Tech Blogger π» | Professional Nerd π€ | Musician πΈ | https://prplcode.dev
Sr. Software Engineer @ Spotify | Tech Blogger π» | Professional Nerd π€ | Musician πΈ
Markdown supported Β· ββ΅ to post
Few tips are common that we often forget about them.
And thatβs a reminder is really handy π
It's a great article. I especially liked the points on only abstracting when there are at least three examples, asking questions to become a domain expert, and focusing on valuable code as opposed to perfect code
Golden advice right here
Donβt Over-Engineer
The majority of problems already have tools to solve them π‘
I used to use Visual Studio / C++ almost exclusively back in the 90s and knew dozens of keystrokes. Now I have to jump between many IDEs constantly and I'm forced to use the mouse. Even with VS I apply the old VS6 keystrokes and find many of them are broken.
Learned new things today, and would try to inculcate them in my career. Thanks for sharing!
Awesome article! I learned five new things today.
I would like to add also taking care of yourself.
It can be easy to neglect taking a short break to stretch or step away from the screen
I love overengineering on personal side projects to learn but I agree with the overall sentiment.
Simon Egersand π
Simon Egersand π
Tanish Shrivastava
Thanks for these wonderful tips. I do think engineers who are just starting (like me for example), should read tips like these.