-
Do not be a hero – 3 pros and some tradeoffs
Do not be a hero. Why ? . Ever seen that one guy doing midnight fixes, hot releases after hours and then gets praised in front of everyone making You look bad ? When features are delivered on time and on target the team is considered heroes. We all love rewards and recognition but heroism might become … Heroes give up work / life balance. As the ancient wisdom teaches us “no good deed goes unpunished”. Whenever there is a new crisis or a target to achieve is set, yesterday’s heroes are quickly forgotten. Long hours eventually might lead to burnout, anxiety and/or even depression. What “Don’t Be a Hero”…
-
Adr vs readme vs changelog
Adr, readme and changelog are the most valueable pieces of documentation that a project could? / should? maintain. They provide us with crucial, core informations we need to star and continue effective development. Let us look at them closely. Usually we can keep everything in plain text or better yet use a Markdown format. You can even try and use some linter, highlgihts for easier writing. ADR (Architectural Decision Record) ADR (Architectural Decision Record): Document that holds a single, significant architectural decision. Includes the context, options that were considered, chosen solution with consequences. Serves as a traceable rationale for future reference as well as new team members. Readme txt or…
-
First make it work then make it better
First make it work then make it better can sound pretty straight forward and fun. You get to fast prototype something that just “works”. Glue together some pieces and see the rapid progress towards Your goal. Sounds awesome and full and dopamine. In any kind of creative endevour a common trap is waiting for perfect results before launching anything. “First make it work then make it better” isn’t just practical advice, it’s achange in mindset that leads to real results and progress. Whether you’re an entrepreneur, developer or just a creative person. Showing up everyday, consistently, even for a bit, beats talent. If You have trouble with that read about…
-
How to write code – part 1
How to write code ? Writing Code for Future Comprehension. How to write code In the “fast-paced” world of software development is a very tricky question… The ability to “write code so in one year you or anyone else will be able to easily understand what it is about” can be a crucial skill. This practice not only enhances the longevity of your projects but also significantly improves team collaboration and code maintenance. Gives a lot less headaches also. Let’s explore why this approach is essential and how you can implement it in your coding practices. As always.. take a grain of salt with a dose of common sense… The…
-
How to judge code – part I
How to judge code is a tricky question. With all the clean code rules, KISS, DRY, YAGNI, SOLDI and so on and so forth one can go crazy and question ones sanity in the end. What i wanted to throw out there is to judge the code be a very simple rule the encompasses multiple different one, is not straightforward and is very flexible. How to judge code ? Judge the code by how easy it is to debug We all know that one person at a company that knows all the quirks and secret sauce of a language, pipes, default interfaces and so on…. that person also knows the…
