bild

Most of my learning was on the job, and in building some open-source projects that I have released over the years, for example: - https://github.com/anthonynsimon/bild - https://github.com/traduora/traduora I still have a lot to learn, but IMO nothing beats struggling with something for a long time, and pushing along until you're no longer terrible at it. I feel that most of what I know I learned by starting projects on topics I initially new nothing about, and sticking to it. Regarding on the job learning, I have been working with Python/Scala for my full-time job over the past 3.5 years, and that helped too. Specially in terms of running multi-regional services, and the challenges that come with that. We run several applications on Kubernetes using AWS (combined >2k req/s at peak time), and that was a big challenge for me from which I l

I agree with you. As the author of a few popular open source projects [1] [2], it has been a fun ride, and I have learned a lot. However, the honeymoon period is over for me. The vast majority of the time it’s a lonely, thankless effort. The problem is that after several years and thousands of people and businesses using the software every day, very few actually take part in improving the project. Or even saying "thank you" to be honest. I’m happy to work on my project and fix issues, but please don’t abuse it. Being open source means that you can change the code if you want to, not to get a developer to work for you “out of love”. That’s why for my most recent project [3], I have decided to no longer start with an “open core” product. Instead it's a SaaS with a generous free tier. Price goes up the more value a customer gets out of it. Y

You might be better off looking through the code of a mature image processing library like OpenCV or this one (recent HN post) written in Go which is very clean: https://github.com/anthonynsimon/bild