When I first started out in the world of software development I was in business development.
I’d go and talk to big corporate organizations about the challenges they were facing and how they might use software to solve those problems, then I’d bring back the requirements and hand it over to someone else who could then decide how it would be built and someone else would build. I then step back in at the end to take the glory.
However, as my career developed I didn’t want to just hand things over. I wanted to be more involved in determining the solution and to do that you need to understand how the technology works.
I thought, I know, I’ll build a website …
Keep reading with a 7-day free trial
Subscribe to Getting Started in Product to keep reading this post and get 7 days of free access to the full post archives.