But more importantly, keeping these things in mind.

• 0. Keep it simple Simplicity > complex, even if complex sells better. Don't overcomplicate your solutions. Simple code is easier to understand, maintain, and evolve. Remember KISS (Keep It Simple, Stupid)!

👉 Why it matters: Complex systems are prone to bugs and are harder to scale. By keeping things simple, you're setting yourself and your team up for long-term success.

• 1. Write clear code Nothing beats a clear code structure. Always write code for humans first, machines second. Use meaningful variable names, add comments where necessary, and structure your code logically.

👉 Pro tip: Imagine explaining your code to a developer outside your team. If you can't do it easily, it's probably not clear enough.

• 2. Tests aren't optional Automated tests are a force multiplier. Build robust test suites from day one. They catch bugs early, serve as documentation, and give you confidence when refactoring.

👉 Did you know: According to a study by IBM, fixing a bug found during the testing phase costs 15 times more than fixing it during the design phase.

• 3. Design for flexibility Make your code flexible for future changes. Loose coupling between components allows for easier modifications and extensions. Think of your code as a living entity that will evolve over time.

👉 Example: Service-oriented architecture allows teams to work independently and evolve their services without breaking the entire system.

• 4. Never stop learning Whether it's old concepts or new technologies, stay hungry for knowledge. Experiment with new languages, frameworks, and techniques. The tech world moves fast, and continuous learning is your best defense against that.

👉 Tip: Dedicate at least 10% of your work week to learning something new.

• 5. Work as a team Software development is a team sport. Succeed or fail together. Share knowledge, give and receive feedback. Remember, alone you go faster, but together you go further.

👉 Fun fact: Studies show that diverse teams make better decisions 87% of the time (no surprises here).

• 6. Optimize only when needed Don't over-engineer everything from the start. Follow the motto: make it work, make it right, make it fast - in that order. Premature optimization is the root of all evil in programming.

👉 Quote to remember: "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." - Donald Knuth

• 7. Automation scales Build tools to avoid repetitive work. Whether it's snippets, scripts, or full-fledged apps, anything that saves time in a common process can yield significant benefits in the long run.

👉 Case study: I personally heavily invest in automation. Deployment pipelines, testing frameworks, and monitoring systems save countless hours of manual work.

• 8. When to start coding Gather clear requirements before writing a single line of code. Unclear requirements lead to unclear code and wasted effort. Spend time understanding the problem before jumping to solutions.

👉 Statistic: According to the Project Management Institute, 39% of projects fail due to inadequate or poor requirements management.

• 9. Work hard, have fun, make history Software engineering is both a science and an art. Take pride in your work, seek out stimulating problems to solve, but don't forget to enjoy the process. Your passion will shine through in your code.

👉 Remember: Happy developers write better code!

These principles are credited to - Alexandre Zajac and they are here to remind myself to always do better in areas i can.