Live data from Hacker News

Man spends entire career mastering crappy codebase

taylor.town

511–520 of 596 posts

Re: Man spends entire career mastering crappy codebase

#511

Everyone can build something new and shiny on the green field. If it doesn't work out you can always find someone or something to blame, because what you set out build was an awesome, highly innovative[1] endeavor anyway. Moving on to something else new and shiny after a while is not only ok, it is expected. Sticking to something, through good and bad times, on the other hand, that's not something many people can do,…

You're examples have very little to do with an average org's IT projects. Not in scope, definition of 'success', or definition of 'finished'. If you're company is building a programming language or operating system you need to make sure that is what you love doing.

My point is that grit is undervalued. It exists within and outside organizations but if I'd tell you my examples from inside you wouldn't know them.

Also perseverance is not the same as being stubborn and pivoting is not giving up.

Re: Man spends entire career mastering crappy codebase

#512
post #436

Earlier quoted context omitted.

I recognize the parody about me. ;) Do you know why I am giving you the two hour history? First, I recognize that I need human interaction, but do not really like people. Second, I am hoping that you will learn & understand instead of just memorize & regurgitate so in the future you can resolve it yourself instead of bothering me. Now, go away; I had my week's fill of socializing. /joking - or am I?

> Second, I am hoping that you will learn & understand instead of just memorize & regurgitate so in the future you can resolve it yourself instead of bothering me. Where does all this hope come from? I’m barely 15 years into my career and I’ve nearly given up…

Hope is dangerous, for it's itself very hard to resist.

Re: Man spends entire career mastering crappy codebase

#513

Earlier quoted context omitted.

Yeh it's a rough but rewarding life; I spend most of my hours on problems that aren't on Google, or any LLM, so I'm kinda used to it now. (Stockholm) Would love to know of more spaces which require this level of programming - usually I feel kinda underworked at most shops. Though, true enlightenment is combining the urge to NIH with some, light, sensible borrowing from those smarter than us :) very much a key skill u…

Embedded programming is this 99% of the time. Abstracting hardware away is a silly notion. Docker? Cloud? Hard to do when your code only runs at all on one specific custom board. The protocol you wrote to talk to that one chip isn't working? Time to break out the oscilloscope and look at the actual data going to the pins. Join us, the pay is worse and the work is harder, but also the prestige is lower.

I sometimes really miss embedded programming; it felt like real engineering in a way that higher-level software development often doesn't. Alas, the shop I worked for could not keep me busy enough, the projects began to feel repetitive, and I got really bored; it'd be hard to go back.

Re: Man spends entire career mastering crappy codebase

#514
post #91

I swear this guy exists at every company I've ever worked. He's the guy you go to when you find some legacy code which you have no idea how the hell it works and end up getting a 2 hour history lesson into a decade of company politics and failed replatforming projects. They're hard not to love.

> They're hard not to love. I often search for a clearcut answer to a technical question and I'm met with a 2 hour history lesson into a decade of company politics and failed replatforming projects. Yeah, thanks for telling me why John from accounting was a dick 10 years ago and you had to code this module in a certain way. I really don't care. I'm new to the codebase and I just want to know how it (the codebase) wor…

Sometimes, the 2 hour story isn't worth the time it's told. Sometimes, the 2 hour story gives you the insight necessary to satisfy Chesterton's Fence. It seems like in this instance, that's not the case, but I'd definitely encourage you not to dismiss stories in general because you don't think you need the history to achieve your goal.

Re: Man spends entire career mastering crappy codebase

#515

Earlier quoted context omitted.

Yeh it's a rough but rewarding life; I spend most of my hours on problems that aren't on Google, or any LLM, so I'm kinda used to it now. (Stockholm) Would love to know of more spaces which require this level of programming - usually I feel kinda underworked at most shops. Though, true enlightenment is combining the urge to NIH with some, light, sensible borrowing from those smarter than us :) very much a key skill u…

Embedded programming is this 99% of the time. Abstracting hardware away is a silly notion. Docker? Cloud? Hard to do when your code only runs at all on one specific custom board. The protocol you wrote to talk to that one chip isn't working? Time to break out the oscilloscope and look at the actual data going to the pins. Join us, the pay is worse and the work is harder, but also the prestige is lower.

> Join us, the pay is worse and the work is harder, but also the prestige is lower.

I tip my hat to you!

Re: Man spends entire career mastering crappy codebase

#516
post #192

Earlier quoted context omitted.

You kids sitting there. All you do is change your EC2 instance size and restart it. Back in my day I had to go and install the RAM by hand. And you know 128Mb of RAM then took up a whole suitcase and weighed more than your laptop The I fall asleep at my desk, periodically waking up shouting "STOP-A!" and hallucinating about being bitten by thick ethernet vampires. Going to make myself a coffin...

"Back in my day, we only got one compile a day with our punch cards. Now you can compile willy nilly without having to put in the forethought we did" - ex coworker

> Back in my day, we only got one compile a day with our punch cards

You were lucky! In my computer class at school in 1979 we got one compile a week. Punched into cards which were taken to the local insurance company who actually had a computer.

Re: Man spends entire career mastering crappy codebase

#517

Man spends entire career convincing himself the reason he keeps job hopping is because everyone else is writing crappy code. Karl Hackerman shows up to each meeting complaining. He seems sour that he hasn’t been given the go ahead to rewrite the system in Rust. He knows a lot about bleeding edge frameworks and best practices and always seems annoyed that he can’t use them at work. He thinks it’s because everyone else…

Author here! I love this so much. I've totally been this guy :) Learning how not to be an insufferable doucheb*g was a surprisingly hard challenge for me I've been writing a longer fiction piece about overzealous know-it-all engineers in the style of Confederacy of Dunces . Probably won't be done for a while, 'cause there's a lot more of my soul in it haha

Awesome! Enjoyed the post. Keep up the good work as long as it makes you happy. :)

Re: Man spends entire career mastering crappy codebase

#518

Earlier quoted context omitted.

Working on the hardware directly is more than half of the fun.

> Working on the hardware directly is more than half of the fun. It never really worked until you gave blood to the computing gods on a sharp edge of a metal case.

"Hey, look, I have all five fingers! Three on one hand and two on the other!"

Re: Man spends entire career mastering crappy codebase

#519

Earlier quoted context omitted.

Working on the hardware directly is more than half of the fun.

> Working on the hardware directly is more than half of the fun. It never really worked until you gave blood to the computing gods on a sharp edge of a metal case.

I feel like the general improvement in fit & finish of cases and chassis is overlooked.

I, for one, haven't flayed open a knuckle on a random razor edge or burr on the inside of a case in like 15 years.

Re: Man spends entire career mastering crappy codebase

#520
post #91

I swear this guy exists at every company I've ever worked. He's the guy you go to when you find some legacy code which you have no idea how the hell it works and end up getting a 2 hour history lesson into a decade of company politics and failed replatforming projects. They're hard not to love.

I usually give the history lesson to forestall the endless series of "Oh god, why do we do this?" questions.
Post reply on HN