Might have had a bit too much of the ol' giggle smoke this time, but we press on nonetheless. We talk about games like Factorio or Satisfactory and how they are similar in gameplay to standing up software systems. Then I do a quiiick rant on the idea of logging right before I effortlessly segue into questions. We start with a little bit of career advice and the different paths one could take. We then jump into imposter syndrome where my best idea of advice is like "just 4get 4head". All you can really do is be the sponge. We then cap it all off with me trying my best to articulate the traditional workflow of writing software for a product. Now that I'm more sober I have this list, lol:

1. Requirements Gathering, scope definition, writing a PRD (Product Requirements Document) (also at this time the design team starts their process)


2. Defining user stories (As a user, I should be able to log in)


3. Working with stakeholders to itemize and prioritize requirements (usually done in a ticketing system)


4. SPIKE for choosing Tech Stack based on above (Spike is a type of task, means "do research into")


5. Proof of Concept (Prototyping) and subsequent decisions


6. Building and Iteration


7. MVP (Minimum Viable Product) 


8. Release a.k.a. v1.0

So yeah, pretty similar to what the question had, just with different terms and a few extra steps.

And remember! Always pet the lizard doggo.

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com