3 ms·
A lot of the complexity you see in code, tool or project are Job-Security sub projects. At first you have a bright eyes junior dev who wants to do the right th
by kbrannigan 4y ago
A lot of the complexity you see in code, tool or project are
Job-Security sub projects. At first you have a bright eyes junior dev who wants to do the right thing, change the world they said.
Little by little he realizes that documenting everything, writing easy to follow and bug free code is a great way to be out of a job.
Complex code is what gets you promoted because you have fire to put out, bugs to fix, getting pulled in meetings where you have to explain the intricate architecture.
- actinium226 4y agoI imagine there are people who face a decision like this at some point in their career, and maybe it seems like the right one at the time, but it feels like optimizing for a local maximum as opposed to a global one. This may work to keep your current job, but should you need to find another job for any reason, how will you sell yourself to the next company, other than trying to bullshit your way in?
- JonChesterfield 4y agoWell, we mostly interview by grilling people about obscure parts of computer science. One of the obvious ways to obfuscate your current code base is to rewrite it with obscure parts of computer science. So with a little ahead of time planning you should be able to practice leetcode and the like on your production codebase.
- great_psy 4y agoWhat is the alternative to bullshitting your way in ? “I worked on this project, I did the right things, wrote all the documentation, there were no bugs, etc” Everyone will say that, how is an interviewer going to tell who’s honest and who isn’t ? The things that make the difference between an ok and great engineer are things that never get published along with the product.