Be Gentle Please

The holy war of software development methodologies in one perfect image. TDD disciples preach the gospel of "write tests first, code later" with religious fervor, silently judging from their moral high ground. Meanwhile, error-driven developers (aka the rest of us mortals) are out here building features and fixing bugs in real-time like digital firefighters. "My code works? I have no idea why, but I'm not touching it again." The irony? Both approaches eventually lead to the same stack overflow questions at 2 AM.

Content 13:51 MyWellness teatw teatw teatw teatw teatw teatw pushnotificaiton pushnotificaiton ProdrammerHumor.io .oll 84 Weniger Jetzt Vor 9 Min. Vor 17 Min. Vor 44 Min.

Content Marc Gravell marcgravell 1h I don't know how to get this to the ears that need to hear it, but if you end any programming question - whether in Stack Overflow, or GitHub, or anywhere else - with "but it gives an error", without telling me what it said: I want to reach through the screen and slap you. 4 17 6 48 8 V

Ah, the sacred text of professional groveling. This is the comprehensive collection of phrases every developer keeps in a text file for when they realize they've been arguing about a bug for 45 minutes only to discover they forgot a semicolon. These aren't just apologies—they're survival tools. Copy-paste these into Slack after your senior dev points out you've been using the wrong API endpoint for three weeks and watch as your performance review magically improves from "concerning" to "shows potential." The best part? After 10 years in the industry, you'll develop the ability to sound genuinely contrite while simultaneously rolling your eyes so hard you can see your own brain.

Expectation: A smiling, confident Mr. Incredible ready to create the next Fortnite. Reality: A hollow-eyed, traumatized soul who just learned that their game engine doesn't support the feature they designed their entire concept around. Nothing transforms a bright-eyed dreamer into a sleep-deprived ghoul faster than discovering your physics engine has a memory leak and your deadline is tomorrow. The duality of gamedev: fantasizing about creative freedom while actually drowning in shader compilation errors.

Content I use windows 11, my game crashed after few hours, plz fix KAPWING I use Ubuntu 20.04.3 LTS with mesa 21.1.5. Mv hardware is - CPU: AMD Rzen 5 5600x. GPU: RX 6800 XT, 32 GB of DDR4 RAM. Steam version of the game crashes at king's palace, when standing around 1-2 meters from kings throne and looking towards the wall. It only happens when motion blur is toggled on in options. I suspect it may be race condition ir postprocessing related to animated elements on the wall. Hi, I use arch linux with latest kernel and MESA. Intel i7 10700K and AMD RX 6900 XT 16 GB of RAM. I noticed a bug in your game - I see the acceleration of character probably does not work properly when stopping movement. Speed "winds up" when character starts moving, but when releasing movement button then character runs at full speed for like 1 more second. It appears that your game uses Unity Engine. Maybe you normalize movement vector when stopping movement after multiplying it by GetAxis instead of doing it after? BTW I run game nativelv via steam I ran your game on Linux (Kubuntu 20.04 LTS with MESA from kisak PPA) via Proton 6.13. I found item duplication bug in multiplayer mode, as I lost connection during storm while using crafting device. I received result item, but didn't lose ingredients. Did try to reproduce bug 1 more time with wireshark active and I found that no web requests were needed to create crafting resultitem. This should be removed from client side evaluation. Posted in rlinuxmasterrace by udydzio reddit