The f*ck off code

Most of the code other people write is a fuck off code - once it is pushed away it becomes someone else’s problem.

The main assumption is that one will never see the code again, and other people (in an organization or whoever it may be) would have to deal with it.

Now suppose that you are writing a small system with would trade your own money on a crypto exchange (using an API). Suddenly you want it to be absolutely correct, error free, and to document every single step you have taken.

Not just that - when you will look at the code a half-of-a-year later you want to remember justification of every design and data-structure decision which you have made, to be sure that every algorithm on that kind of data has been done right, and how you can be sure of it.

Now every “safe” functional programming technique is making a lot of sense to you and you probably want all your code to be pure, without imperative loops, without destructive updates (immutable data). You want it to be as pure, correct and eternal as math itself.

You probably want everything to be formally verified, but that’s a dream.

If you program as if you are writing your own money managing system, then and only then you really do. Everything else is just a crappy, low-effort “fuck off” code.

Most of corporate code is a “fuck off” code for obvious psychological and organization-structural reasons. Once you build an army of easily replaceable coding “drones” you will get a steady smelling stream of the “fuck off” code.