In the last few years, I’ve increasingly heard the term “Product Engineer” in the context of software development. This role isn’t new - it’s just that our understanding of the intersection between product development and software engineering has improved. In reality, we’ve always been product engineers; we’re just making it more explicit now.
Jason Fried, David Heinemeier Hansson “Build half a product, not a half-assed product.” - Rework How is this different from regular software engineering?
Why do newer programming languages like Go, Rust and Zig eschew Exceptions, believing that they cause unpredictable control flow and hidden performance costs? Instead they encourage explicit error tracking. Even Kotlin prefers a more functional style of error handling over unchecked exceptions.
Whether you’ve been working with C# for just a few months, or for several years, have you ever stopped to consider the way that you write code to handle errors?
I have found myself advocating for Development Containers, or Dev Containers for short, more and more
frequently. Stop wasting time fixing dev environments. Dev Containers let you spin up a fully configured setup fast - so
you can focus on coding.
This is my first post, and I’m looking forward to sharing some thoughts and ideas. After talking through my aspirations with a friend, they suggested that I should start a blog to get myself and my ideas out there. So here we are.
Over the years, I have always wondered about starting a blog, but I guess I fell into the trap that many do. With so many other great blogs out there, what could I possibly have to say that hasn’t already been said?
