the world needs more recreational programming.
like, was this the most optimal or elegant way to code this?
no, but it was the most fun to write.
cause like, yeah, it's good to know how to write optimal code and how to make it elegant and easy to maintain, sure!
but one thing you have to maintain is your brain. If you're constantly driving your programming brain at maximum speed, maximum awareness of all possible caveats and vulnerabilities, always considering "how will I maintain this code in ten years time?" you're going to burn yourself out.
@foone
* If you have the time, defer things with TODOs. Yes, that's the path to tech debt, that's why I started with "if...".
* Write tests, positive and negative, before (TDD), meanwhile and after. As many as you can think of without straining. Real life will provide you with more. Integration tests, for each layers if possible.
* Start writing with comments and or pseudocode. If the latter and your programming language is #Python, you're halfway there.
I wish it was that easy on the Ops side.