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.
Are You Coding Too Fast?
The Latest From PipelineHi 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.
Hi past, present or future data professional! If you’re in the U.S., Happy Thanksgiving! I’m prepping for my food coma, so I’ll make this week’s newsletter quick. Like millions of Americans, I’ll be watching NFL football (go Ravens!). The average NFL game is 3 hours. If you can skip just one of today’s games and carve out that time for professional development, here’s how I’d spend it. In the spirit of football, I’ll split the time designation into 4 quarters. Documentation pass - if you read...
Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! In 2 weeks or so The Oxford English Dictionary will reveal its 2025 word of the year, a semi-democratic process that lends academic legitimacy to words like “rizz” (2023’s pick). If you’re currently employed or interact with white collar workers, you would think the word of the year is “headwinds.” Used in a sentence: “We’ve pivoted our AI strategy but still encountered headwinds that...
Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! After choosing a dataset, one of the most significant decisions you must make when creating displayable work is: How am I going to build this thing? For some, you may try to “vibe code” along with an LLM doing the grunt technical work. If you choose this approach, be warned: Nearly half of all “vibe code” generated contains security vulnerabilities and that’s before you even consider its...