You could also just show up to a board meeting or similar and keep pushing them to the ground until they stopped trying to stand up, then tell them to give all their money away or you’ll just keep bullying them in increasingly humiliating ways.

i mean it depends what the job is for

“Thanks for your time, but this job isn’t for me. I wish you good luck finding your candidate, though.”

OK we’re definitely talking about different things when we say photorealism. I see stylized and photorealistic almost as on a linear spectrum. I realise there are more dimensionz to it than that, but that’s the usage I think the meme is critiquing. That’s how I took it, anyway.

Oh well then there is no conflict at all, yeah

I think we’re talking about different things, but I see your point.

By stylized “graphics” I took it to mean like the actual resolution, polygons, draw distance, etc, and then aesthetics goes on top of that.

give me back my jpeg artifacting you thief

High-fidelity and artfully stylized aren’t, but photorealism is like… a photo.

Right click > safe to Desktop

You’re going to want to follow the “campsite rule” everywhere you go, and also sneak in positive refactors into your feature changes (if business is not willing to commit time to improving the maintainability of the codebase).

Read up on good software design principles. I don’t know you experience level, but for instance, everyone agrees that appropriate abstraction, and encapsulation make code easier and more enjoyable to work with, and will let you run tests on isolated sections of the code without having to do a full end-to-end testsuite run.

Having tests that you trust, especially if they execute quickly, will increase your “developer velocity” and let you to code fearlessly–knowing that your changes are reasonably safe to deploy. (Bugs and escaped defects will happen, but you just fix them and continue on.)

Good luck!

The fact that documentation and comments can’t “fail” if the underlying code changes is a real problem. I’ve even worked at places which dictated that comments had to go directly above or even beside (inline) with the code they were explaining, so they would show up in any patches changing the code.

What do you think happened? Yup, people would change code and leave the outdated (and wrong) comment untouched, directly to the right of the code they just changed.

Hell, I was one of those people, so I get how it can happen.

omfg that’s over 1 MILLION characters 💀 💀 💀

vomit

Translation: please help us understand our codebase. We’re paralyzed by fear.