ProgrammerHumor
fromVibeToObliviousCoding
Discussion
def function_doing_y(parameter_a, parameter_b)
I wonder what my code is doing. Might it be doing y and using a and b for that?
Naaah, impossible, but because I haven’t added the comment
computed y(a,b)
I guess I will never know what it does
Eh it happens, it's even funnier when your reviewing some code with a peer and your like "Who did this?!" and git blame points the finger back to you. Very humbling moment.
//Howdy future me
This is present me
Amateurs
Right... I don't understand why you wouldn't want to have all your functions and logic pathways somewhat memorized. Maybe this is some programmer form of self depreciation BDSM kink I don't understand. 🤔
Dude, I’ve got 20k files and hundreds of thousands of lines of code. I’ve touched at least 40% of it. And the moment I finish a dev cycle, the first thing I do is flush it all the fuck out of my head. Because I don’t need that info anymore — and there’s just way too much of it.
The biggest lie ever told is self documenting code.
That's what I said to my team lead today morning when he asked me what I coded 2 weeks ago
And yes he did ask the question again
Later...
Jr. Dev: "Help! I forgot what my code does!"
Sr. Dev: "No comment."
ObliviousCoding is a great name
Thanks
I still remember my code even after leaving my prev company... am i... builtttt differrrent?
Fun thing, event though I write comments a lot, problems usually occur in the places not covered by comments. So they are useless anyway.
Wdym I need to write documentation?
For my serious answer:
- function names
handle_keypress... // like no shit ... - comments ``` // ======= KEYBOARD SHORTCUTS ======= ...
// ======= ACTUAL TEXT INPUT ======= ... ``` 3. cleaning up after yourself and not making a convoluted mess (which often happens right after I solve some problem)
...works well enough for me.
Also, I personally, find that code is more skimmable when aligned vertically (works only sometimes and not that impactful)
I thought most people save their code to disk so they can read it later.
Step 1: “Who wrote this steaming pile of crap!!!?”
Step 2: git blame
Step 3: “Oh, it was me”
This happens.....but having diagrams on the source code documentation will help with recognition of old code...or keep the files and functions neat with good name choosing :)
Hell I'll be in the middle of writing a function and forget what it does
just gotta write better readable code
If it wasn't because of Git I wouldn't even remember that it is my code.
Vibe coders never know what their code does.
Present me, “Behold my perfectly formed, logical, and bulletproof solution to this intractable problem!”
Future me, “WTF was I thinking?”
The trick is not to touch it again until you advanced to be a senior dev. And then it‘s another juniors problem