---
title: "Dave Rogers (@daverogers) | Hashnode"
description: "s o f t w a r e. Read the latest articles by Dave Rogers on Hashnode."
url: "https://hashnode.com/@daverogers"
---

@daverogers

# Dave Rogers

@daverogers · Joined February 2022

s o f t w a r e

## Comments

[definitely true. being a senior dev at this point, i look back and think about the devs who mentored me (which i didn't think of as mentoring at the time, like you pointed out i was trying to make my mark haha) and i'm like "i GET IT!" i see the same mistakes i made (over-engineering solutions, tightly coupling my use case to a proposed solution, trying to write code for a future case that likely will never appear or at least how i think it will, overdoing refactors, etc.) and i try to impart to young devs that they're like baby scorpions putting the stinger to everything in front of them when most things can be done simpler which will make their lives (and the lives of their teammates) so much easier down the road. i also try to help them with growing their career (i was also uncomfortable with these discussions, and thought i'd PROVE why i should get paid as much as my colleagues but the truth is, once you take a reduced rate it's locked in with 95% of employers) and understanding work/life balance more than i did in my 20s. sure, your current task might be "high priority" but there's one right after that, and right after that; you'll never get through all the high priority tasks and be able to relax, so learn how to prioritize yourself and your own health first because most employers are happy to let you work yourself to death for what is very likely an under-salaried workload.](https://hashnode.com/posts/from-an-ex-amazon-team-lead-5-mistakes-i-made-as-a-junior-software-engineer/623c7a772209c88a3de8e1cd/comment/6245d987d1ff58fbe694800c)

Comment · Article · Mar 31, 2022 · [From an ex-Amazon team lead: 5 mistakes I made as a junior software engineer](https://hashnode.com/posts/from-an-ex-amazon-team-lead-5-mistakes-i-made-as-a-junior-software-engineer/623c7a772209c88a3de8e1cd)

[having a strong "why" is important when you're in Stage 2. people are surprised to learn that i must've quit programming a dozen times, but i kept going back to it because i had strong motivations to try again; i had things i really wanted to build, but there were no off-the-shelf solutions nor did i have the money as a teenager to pay anyone to build anything for me anyway. it took time to get a proper foothold where i could really build things, just like learning any spoken language it's pretty rocky up front but you progress more consistently once you get the foundation down. you stack experiences where something was really hard but you persevered and figured it out, so eventually you approach new problems remembering it might not happen overnight and it might be a little painful at times, but you can do it. even as a senior developer with years and years of experience at this point, i still often feel like i don't belong, so i tell young developers that the only real differences between them and i are that i've been around enough to know nearly everybody in the room feels like an imposter at times too (certainly those worth working with), and i've merely had thousand times more failures to know a better starting point on the next attempt. you'll never stop reading documentation, reading blogs like this one, learning new languages and techniques, etc. - you just get to a stage where you can laugh at how much more epic your failures have been.](https://hashnode.com/posts/4-stages-of-the-dunning-kruger-effect/61ee8e1ae247b2151e61c20a/comment/61fa25bd43e34d1181696124)

Comment · Article · Feb 2, 2022 · [4 stages of the Dunning Kruger effect](https://hashnode.com/posts/4-stages-of-the-dunning-kruger-effect/61ee8e1ae247b2151e61c20a)