Live data from Hacker News

Man spends entire career mastering crappy codebase

taylor.town

171–180 of 596 posts

Re: Man spends entire career mastering crappy codebase

#171
post #24

For ten years, I worked on codebases written in C++ without using any third party libraries (no, not even STL -- we needed faster, thread safe versions of strings and maps which were not available at the time; Boost? What's that?), its own custom messaging middleware built directly on sockets, its on distributed process management system built with unix syscalls (obviously). There was not a single line of HTML, Java…

I don’t think anyone working with low-level C++ for HFT can face similar fate. Most of skills gained at such job seem very transferable. The article seems to be more about jobs where 95% of work consists in implementing CRUD in accordance with very specific business logic of the company. The only reason to change such job I can imagine is to sit out your non-compete package. But I am not in this industry so maybe I’m…

It's not that you won't have the skills, it's somehow demonstrating them.

I also worked at an HFT C++ shop that used no STL. Every data structure has a weird name and API that you get used to. The whole architecture has its own idioms, and hasn't needed much upgrading in terms of language features.

Imagine you learn the grammar of English. You learn how to pluralise nouns, when to put an s at the end of a verb, how to to use commas, and so on. You then go to work at a place where they have a different word for coffee, drink, and order. Along with every other word. You end up learning where everything is and how to talk about it, and you're productive.

How do you apply for another job? Chances are you will be asked how to order a coffee and drink it.

Very real issue btw, I still have friends there.

Re: Man spends entire career mastering crappy codebase

#173
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.

"... And the AIX machines were a real beast. We had 20 of those things, and each had its own 20 amp circuit. Had a tendency for the grounding to the steel case to fail. If you wanted to upgrade it you'd first need to grab a pair of thick leather gloves...."

I for one do not mind that part of computing getting abstracted away by the cloud, whatever its other failings. :-)

Re: Man spends entire career mastering crappy codebase

#176
post #25

There is something to be said for stability. Since our protagonist retired early, the pay must not have been bad. The glass is half full, or so I tell myself.

I thought so at first too, but the planned "street performance and dumpster diving" tells a different story.

[deleted]

Re: Man spends entire career mastering crappy codebase

#178

Earlier quoted context omitted.

Those stacks can be full of 'not invented here'. They are unique and have their own quirks. Quirks that you more than likely can not google for any sort of guidance as to what is going on. I wrote one of those stacks a few years ago. No std libs at all. Why? must fit in 32k and most of that space is needed to hold data. That means throwing a lot of those helper bits out or spend weeks figuring out how to bend the com…

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…

Game engines have a lot of low-level C++... Often not the best working conditions though from what I hear.

Re: Man spends entire career mastering crappy codebase

#179

Earlier quoted context omitted.

That's mostly the guys fault and not the jobs fault. Even in a bad code base you can start making things better, apply modern techniques and learn new things. Also most of the skill you gain there is transferrable. E.g. just because you have to work with some legacy PHP project, it doesn't mean that you would suck at creating modern applications in JS. It would just take a couple of weeks to get use to it.

Making things better and applying modern techniques don’t map to a feature story. In the environments being discussed you’ll have to wait for a cadre of architects and program managers to convince the C levels to commit to a multi year, millions of dollar effort to have any hope of improving a code base.

You don't have to rewrite everything, to start fixing things.

Re: Man spends entire career mastering crappy codebase

#180
There is something admirable about someone who commits to maintaining a codebase, no matter how crappy it is. We don't see this often in tech and often being a person who is more reliable and stable is more desirable than two junior devs and a Keurig machine. Speaking from my first hand experience when reverse engineering a poorly documented product for a small company these people were the real heroes. Thanks to all the "Arthurs" that keep the world spinning.
Post reply on HN