I really dislike it when non-devs ask devs: "I don't understand. What could be so hard about coding?".

Grumble. FredFlintStoneGrumble.

"What could be so hard about coding?"

Pretend you have a bag. The bag has a limit on volume. There is also a weight limit of how heavy the bag can be. Now pretend you have an assortment of objects that have different weights and volumes. The total weight exceeds the weight limit of the bag. The total volume also exceeds the volume of the bag.

Describe a method for optimal choice of items to maximize the number of items.

Now assign a value to the items. Describe a method for optimal choice of item value in the bag.

At some point they will realize they don't know what the fuck they are talking about. You won't even have to say it.

I just keep silent.... I'd rather not waste my time & energy explaining

@Demolishun I'm dealing with code that 15 devs before me wrote horribly, lazily and spaghettily. Then my product owner thinks it's ok to put a 2-day time limit on it and call me fucked up when I'm not fast enough in solving it. What the fuck am I, a machine?

@CaptainRant 🫡 sorry bro

"you've activated my trap card!" proceed to bore them to sleep with the details

@CaptainRant I'd just get the specs and rewrite it

that's actually how I rewrite bad stuff. I read the codebase, extract the specs, then write my own version and use the old codebase as reference if I don't know how to do something

it's faster than refactoring

also tho not professional advice. you do you

@jestdotty It's a good idea to rewrite but they put serious time constraints on me.