Yeah This Happened

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

25 million lines of C code held together by duct tape, prayers, and the tears of generations of developers. This Oracle DB saga reads like a horror story that Stephen King would reject for being too disturbing. The lifecycle of fixing a bug is pure corporate torture: two weeks deciphering mysterious flags, adding more flags to fix the first flags, waiting days for tests to fail, rinse and repeat until you accidentally stumble upon the magical combination that works. The real punchline? After surviving this nightmare and swearing "never again," some poor soul is still maintaining this codebase right now, wondering which of their life choices led them to debugging flag #10,372.

Content Finding bugs and giving advice on someone else's code during code reviews Trying to find a bug on my own code ProgrammerHumor.

The classic programmer's escape hatch! Why actually implement that annoying method when you can slap a //TODO on it and kick that problem down the road? Future you will definitely be more motivated and smarter than current you. It's basically time travel for your coding problems - except the time machine only goes in one direction: straight to your technical debt collection.

The top code uses proper control flow with nested if statements and while loops - structured, readable, and maintainable. The bottom code? Pure chaos with line numbers and goto statements jumping around like a caffeinated squirrel. Nothing says "I want my colleagues to suffer" quite like spraying goto statements throughout your code. It's like leaving landmines for the next developer who has to maintain your mess. The best part? Both programs return 69 - because even terrible code can sometimes get the job done. Pro tip: If you want job security, write code only you can understand. If you want respect, never use goto .

Content imogen sailoremo Feb 2 Nature is healing NEW EMPLOYEES 20,000 honey bees took over a tech company's empty office during lockdown 271 17 7.7K 47.6K nombre de usuario democracia 403 Feb 2 Now their products will be full of bugs E 9 17 4 M 89