Man spends entire career mastering crappy codebase
31–40 of 596 posts
Re: Man spends entire career mastering crappy codebase
#32My boss straight up told me a couple of juniors could do my job the other day
Re: Man spends entire career mastering crappy codebase
#33Re: Man spends entire career mastering crappy codebase
#34Funny, but there's nothing wrong with that if Arthur was/is happy (which isn't mentioned).
Exactly this. Guy had a comfortable stable job for years. Probably knew codebase and technology enough to have lots of time for family/friends/hobbies. More than this story scares me how HN reacted
Re: Man spends entire career mastering crappy codebase
#35Funny, but there's nothing wrong with that if Arthur was/is happy (which isn't mentioned).
Re: Man spends entire career mastering crappy codebase
#36Earlier quoted context omitted.
I don't think it's supposed to be a "real" article about a real person, I think it's art (that speaks to some of our fears) do you believe that something has to be purely "productive" to be deserving of space on the internet?
I think it's quite inspiring rather than invoking fear. I would take a job like this any time.
1) You will be paid well, but your code will be destroyed every night.
2) You will be poorly paid, but your code will be useful and appreciated.
Dilbert says "Hey! They're both better than what I have now! Wally, you should come and get some of this!"
Re: Man spends entire career mastering crappy codebase
#37For 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…
Re: Man spends entire career mastering crappy codebase
#38I'm worried this will be me someday. I suppose that's the point.
Does somebody work 35 years in same company, it is usually 2-5 years -> new company grind rather than working at same company.
That said, it is a red flag for me if most people in the team have been there for very long: it means that as a new comer I will always be bottom of the pile and have no career growth opportunity.
Re: Man spends entire career mastering crappy codebase
#39My boss straight up told me a couple of juniors could do my job the other day