Hacker News Reader

Comment by hellofunk | Hacker News Reader

I made the terrible mistake this week of using the strategies in this article as a way to provide to my employer my resignation, and unfortunately it didn't work as I'd expected.

View on HN

That's because the premise of the article is completely wrong. There's a venerable tradition on Wall Street of generating unmaintainable code and not sharing your knowledge with anyone else. If you're lucky enough for the code you're writing to be mission-critical, you can write your own check and never get fired.

I won't say which, but one of my previous employers had a policy of only using frameworks and libraries that were invented at the org to reduce the likelihood of employees developing transferable skills. I learned about the policy after I wrote a detailed write-up of a specific bug class that was affecting all of our apps, and recommending switching libraries, and sent it to the leads of all of the development teams across the org. Learning this was a contributing factor in my leaving the place :/

Two question from the "hacker" variant[1] of the old usenet/gopher-era "purity test":

    00F0 Is your job secure?
    00F1 ... Do you have code to prove it?

[1] http://www.mit.edu/people/mjbauer/Purity/hackpure.html

Ah, the classic "try to get fired" move and they promote you instead!

Boy, that's just a straight shooter with upper management written all over him.

Our entire society seems to be based on Office Space and Idiocracy

Reply on news.ycombinator.com