KarachiWalaDeveloper

Software Engineers require instructions in order to build apps and tools. And most of us don't know what these instructions should look like. One of the ways these instructions can be shared is in the form of user stories, and it's not just about writing a bunch of text, but comprehensive check list of how this should be structured so the right information can be given to the builder. Ofcourse its a two way effort Product and Engineering need to work closely to build up such requirements so they make sense from a functionality perspective, and a technical perspective.

This session is based on the article linked below:

https://martinfowler.com/articles/product-backlog-building-canvas.html

Google, or any of the FAANG companies for that matter, are an awesome place to work. When I started by bachelors - I was thinking of graduating and then getting a job there, or build a pathway to a job there. However by the time I graduated, my mind set had changed. In this episode I explore my thoughts and reasoning on what changed my mind and why I havnt applied since.

With startups going bust left right and center, high inflation and a global recession - are startups still the right choice to be at? In this episode I talk about the difference between the companies treating engineering teams as a profit center vs a cost center, to show why startup engineering teams as usually a better choice even if there is a slightly higher risk being there.