This list grew quite a bit during the last days. Thank you all for subscribing. If there are questions or you would like to share a point of view with me, please always feel free to reach out. I literally jump with joy when I get an email from you. We all have too many emails in our inboxes that are unimportant. Your emails are important to me, and I welcome them. Try it out 😉
Last week I wrote about testing. The weeks and days before that, I wrote about continuous integration without branches, configuration management, best practices for modeling business processes in code, code styles, linting and much more.
Wait, but why?
I was lucky enough to start my working career as a software developer in a team that valued improvement. They were open to trying new things, ideas and concepts. We tried a lot of things, kept those that worked well and got rid of everything else. This lead to a highly productive team that regularly outperformed bigger companies. We wrote good code and solved essential problems for our clients. We also made lots of mistakes along the way. Most of the time we were able to learn something from them. We forgot about a few.
It is my goal to help more developers write better code. Many software projects fail because people are not knowledgeable enough to know any better. By people, I do not solely means developers. A team plays this game. We should act like that and hold everyone accountable for it.
From my time working in agencies developing software, I know that not all developers take enough time to learn. Others graduate from coding boot camps where there is only limited time to teach specific things. Fundamentals in software design, knowledge about testing, software architecture—these are often done by try and error. If something works, keep doing it. Throw DevOps and CI into the mix, and things get even more confusing. What are all these buzzwords like Docker and Kubernetes and why should you care?
From my experience and empirical evidence from my clients, I can say with certainty that almost every process can be improved and nearly every software can be bettered. You only have to know in which way—and how.
I am in a fortunate position to have at least some answers that I like to share with you. I do this through writing these emails giving workshops, training and consulting for my clients, grabbing a keyboard and writing some code and (soon) through (more) writing on my website. I hope that you find some of it and try to use it. There is no question that it works.
If I can challenge your assumptions and ideas on how to create software and you enjoy the process even more then before: perfect.
See you around.
- None Found