Hacker News new | past | comments | ask | show | jobs | submit login

I have also found that when I enter a new workplace, everything done before me was a mess of unwieldy, poorly documented and unstructured code. Worse it uses an old, archaic platform that is long overdue for a complete overhaul.

Then when I arrive, I make everything logical, nice, structured and proper.

After I leave, once again the place falls prey to disorganized minds who take my work and mess it up for flashy new technologies that are not as reliable as what I had done.

For some reason, this keeps happening.

edit: corrected word thanks to @brlewis

The easiest scapegoat in software history: the previous developer(s).

The same dev(s) that allowed the place to run with all the long hours and the most check-ins, are the cause of all the woes when the next dev(s) take over (usually to justify a version 2).

The second easiest scapegoat: third parties, component builders and providers.

All of these can be attributed to Not invented here (NIH) syndrome. [1]

Devs always know more about a system they themselves worked on, and noone wants to be liable for a system that they didn't build that can have hidden gotchas simply because it was NIH.

At every iteration in every single system, even outside of software (you can see this in generations and politics), each iteration teaches lessons and uncovers unknown problems or creates them. Many times this is no fault of the creators but the simple iteration attempt progressed knowledge enough to be able to learn about a new problem that could not be found without said iteration/advancement. In this sense iterations and different teams aren't bad, but they will always blame the former because it uncovered new problems, which is ultimately a gift to solutions and progression.

New problems create new solutions which are what we call progression and innovation, and the next in line should be happy those problems were found that they can solve, for they themselves will eventually be providing this service to those after them.

[1] https://en.wikipedia.org/wiki/Not_invented_here

This is a nice joke.

However I've seen it for real too: a former boss calling me about a problem with a Sybase Adaptive Server Anywhere problem. So I tell him I've forgotten it all but it is all documented in the wiki I set up with the guy who supported the system after me so, just search for Sybase.

Well... Turns out that documentation is gone.

I, too, would like to pat myself on the back for having excellent code management skills, and problem solving. But most of all, for going completely meta on people.

You are also the people before and after you

That's the joke.

I needed that laugh

The best is when you work on something, then shift to another part of the business, come back, and uncover some crazy construction that has you scratching your head and what the hell the person who made it was on at the time.

And as you wind your way through the lack of documentation or sanity in how things were done, you inevitably find some sign that the person who created it was...you. <facepalm>

> Then when I arrive, I make everything logical, nice, structured and proper.

Not to mention self-documenting.


Otherwise perfect. :-D

Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact