this post was submitted on 20 Aug 2025
689 points (97.9% liked)

Programmer Humor

26071 readers
1022 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] dotslashme@infosec.pub 37 points 1 week ago (11 children)

At work we have the following quote on the fridge

"A ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot — albeit a perfect one — to get an “A”. Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes — the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay."

We are a software development company and my reply to this was basically that pot making hasn't changed in a long time, it's basically shaping and firing clay. Software development is comparatively new and has a vastly more dynamic landscape.

Also, the comparison is stupid because we don't write code, realize it was shit and write a new one. If we did business like that, we wouldn't be in business.

[–] yogsototh@programming.dev 4 points 1 week ago* (last edited 1 week ago)

From my experience of boss looking at people working. Working hard is by a huge margin a lot better than working smart. Trust me I know my shit. Once I even wrote a formula in Excel! /s

That being said with experience you stop using anecdotes, easy pre-made sentences like "premature abstraction/optimisation is the root of all evil!" and you understand that there are no generic solutions and you need, every time, to think hard about the best way to produce something relatively to the context and constraints which, most of them, aren’t technical but organizational and human related.

And also, if you intend to work on a project more than 6 months. Quality is really worth it. The lack of quality works like accumulating mud. After a while, you are stuck, and the next step will require a huge amount of energy.

load more comments (10 replies)