Are You Coding Too Fast?


The Latest From Pipeline

Hi past, present or future data professional!

The opening scene of The Social Network, in which a fictionalized Mark Zuckerburg writes enough code to create a website in a single night, has forever skewed new engineers’ perceptions of development pace. If you think about it, media depictions of coding are almost always blisteringly fast and under duress. So, when you start coding in your first job, you might feel like me: Pressured to crank out as much code as quickly as you can.

In the process, however, you will inevitably make mistakes that range from minor infractions to potential career-enders. Just as importantly, you’ll face the very real issue of developer burnout.

One of the best things you can discover for yourself as a developer with less than 1-2 years of experience is your perfect development pace. If you’re new on the job and trying to find a pace comparable to your teammates you can use or create a burndown chart to compare your speed to that of your team and overall org.

However, despite your best efforts, you will encounter and need to overcome obstacles out of your control that can slow or even halt development pace. To learn how to set and stick to a reasonable pace and easily circumvent these issues, read the latest here.

How fast do you tend to code? Do you find yourself finishing tasks early or struggling to keep up?

Let me know: zach@pipelinetode.com

Thanks for ingesting,

-Zach Quinn

Extract. Transform. Read.

Reaching 20k+ readers on Medium and nearly 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! I want to share the single most important realization I had back in the summer of 2021. I was burned out, juggling two part-time jobs, trying to plan a wedding, and drowning in full-time job applications. I felt overwhelmed and underprepared as I plunged into a sea of candidates I perceived to be more intelligent and better "fits" than me. My portfolio was full of the usual Titanic, Iris,...

Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! One of the most validating and terrifying professional moments is reaching the final interview round. It is in this context that you meet candidacy’s final boss, who incidentally, usually ends up being your boss' boss. Specifically I’m referring to the department executive responsible for bringing in additional headcount, i.e. you. While this may sound intimidating, the role of the executive...

Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! If you’re a job seeker in the data space, your GitHub portfolio has only one job: To act as a calling card that gets you to the next step of the hiring process. Too often, I review portfolios for potential referrals and see brilliant code buried under structural mistakes that have nothing to do with programming skill. Your GitHub is not just cloud storage for your code; it’s a public display...