{"id":916,"date":"2021-08-16T08:20:50","date_gmt":"2021-08-16T08:20:50","guid":{"rendered":"https:\/\/deberker.com\/archy\/?p=916"},"modified":"2021-11-06T16:27:08","modified_gmt":"2021-11-06T16:27:08","slug":"minimal-viable-developer-acing-your-first-month-in-software","status":"publish","type":"post","link":"https:\/\/deberker.com\/archy\/minimal-viable-developer-acing-your-first-month-in-software\/","title":{"rendered":"Minimal Viable Developer: acing your first month in software"},"content":{"rendered":"\n

It’s easy to be overwhelmed by the novelty and demands of your first software role, whether that’s an internship or a full-time position. <\/p>\n\n\n\n

This is a guide to the tools, skills, and rituals you’ll encounter in a real software shop. It assumes that you already know the mechanics of coding, and focuses on the key differences between working on school projects and contributing to a business-critical codebase. <\/p>\n\n\n\n

It’s applicable to data science, backend, or frontend roles; it’s about everything that’s not<\/em> writing your favourite flavour of code.<\/p>\n\n\n\n

This guide is going to be more useful for people joining startups than established companies. FAANG <\/span>1<\/sup><\/a><\/span> companies will put you through 4+ weeks of formal onboarding. In a startup you’re more likely to be handed a laptop and a t-shirt, and asked to join your colleagues in desperately trying to steer a sinking ship towards profitability. Let’s get you from deadweight to oarsman in the briefest time possible.
<\/p>\n\n\n\n

\n

Table of Contents<\/p>\n