Drunk Post: Things I've Learned as a Sr Engineer
old.reddit.com
Drunk Post: Things I've Learned as a Sr Engineer
1–10 of 510 posts
Re: Drunk Post: Things I've Learned as a Sr Engineer
#2i see nothing i disagree with here.
so either i’m doing OK, or we’re both fucked…
Re: Drunk Post: Things I've Learned as a Sr Engineer
#3> The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there's any recommendations, I'd seriously pay for a course (like probably a lot of money, maybe 1k for a course if it guaranteed that I could write good docs.)
I agree but think it is more than just _documentation_: effectively communicating ideas through text was one of the most underrated skills in software engineering. I say "was" as I think there is much more focus on it now with remote work and video call fatigue becoming the norm for many.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#4> If I didn't learn something from the junior engineer or intern this past month, I wasn't paying attention.
Amen! Not just junior engineers. PMs, analysts, testers. We all have a lot to learn from the rest of the team!
Re: Drunk Post: Things I've Learned as a Sr Engineer
#5> Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all.
This a thousand times. Having empathy for future devs, maintenance, and bug fixes is so important.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#6> I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so little.
AMEN to this. I've been in the industry for 20+ years and at this point I know so many different frameworks (front-end and back-end), databases (SQL and NoSQL), networking protocols, browser differences, ORMs, it goes on and on.
I'm paid what I barely consider adequate.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#7> I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so…
I think people in the industry are paid based on the potential value they can create (whether real or not), knowing many things or understanding fancy technologies matters little if one can't put them to use for the benefit of the company.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#8Probably people are honest when they are drunk. There is nothing to argue with any of those comments.
But this one stood out for me!
> Titles mostly don't matter. Principal Distinguished Staff Lead Engineer from Whatever Company, whatever. What did you do and what did you accomplish. That's all people care about.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#9> I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so…
From my experience this is true because the team is so focused on getting the backend business logic sorted out, catering to new customer demands, that they develop new features overnight.
Then just assume the front-end will consume it and output a little, inconsequential DOM element here or there.
Re: Drunk Post: Things I've Learned as a Sr Engineer
#10> I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so…
I think people in the industry are paid based on the potential value they can create (whether real or not), knowing many things or understanding fancy technologies matters little if one can't put them to use for the benefit of the company.
Value created plus how easy they are to replace (supply and demand).