Reaching 20k+ readers on Medium and over 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 over 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 fellow data professional! On a recent holiday, a family member and I were strolling along a beach, talking about AI disruption (relaxing, I know). He, an attorney, assured me his job was AI-proof and jokingly offered to hire me when AI takes my data engineering job. If you ask executives at most companies, they’d find several flaws in that argument. Over 80% of technical executives, including Chief Data Officers and Chief AI Officers, consider data engineering to be an essential role...
Hi fellow data professional! Ken Jee, who you heard from last week, drops some sobering career advice in one of the earliest editions of AI Survival Guide: Making a senior-level tech role is no longer about advancement; it’s about survival. The post talks about the growing moat or "wall" between those breaking into the industry, those in entry-level roles and those in a mid-career phase. In the spirit of AI Survival Guide’s advice to bridge the gap separating the early and mid-career...
Hi fellow data professional!' Today I’m turning the newsletter over to my friend Ken Jee (writer of AI Survival Guide, creator of Newsletter Hero) to share how he cuts through the noise of shiny AI products to find tools that enhance technical work. My Simple Framework For Adopting AI Tools Ken Jee As new AI tools launch almost daily, a quiet tax is emerging. Decision fatigue. Every new model, agent, or workflow tool carries the same implicit question. Should I switch, or should I go deeper...