Lessons for an Engineer from a Corporate Vice President of Product
Few insights for engineers from a product person with over 22 years of experience
Search for a command to run...
Few insights for engineers from a product person with over 22 years of experience
No comments yet. Be the first to comment.
Stacked Commits allow you to deliver code as multiple, small units of change which build on top of each other.

Sometimes Java interop brings bugs along with the benefits

Use GitHub Actions to push changes as part of a PR
How a simple typo means your users receive incorrect data
At my workplace, we have an internal career guidance fair where you can book one-on-one sessions with senior folk from various disciplines. I was fortunate enough to secure a session from a CVP (Corporate Vice President) of product. I wanted to understand software engineering from the perspective of a product person and this was an opportunity I couldn't miss. I have noted few of the questions which I had asked in the session and I'm glad to share these insights with you.
Quick housekeeping before we begin: My idea of a "product person" is vague and for the purpose of this article I will borrow the definition from this article by Noah Weiss: "Great PMs [product persons] live in the future and work backwards, focus on customer and business impact, and amplify their teams."
Now, let us begin!
Liked
Disliked
Wanted More Of
Let me know in the comments if you would like me to expand on any of these points!