If it works, it works

Content "Just keep coding. We can always fix it later."

Content When the code you copied from a tutorial gives an error

Content How to get GenZ developers to stop using emojis in commit messages and PR titles? I am a senior developer and tech lead at a software company. Recently, we hired some fresh graduates who are very talented and enthusiastic, but they have a habit of using emojis in their commit messages. For example, they would write something like: "Fixed bug in login function Or "Optimized sqc algorithm I" or "fix lint Go" and " : handle null pointer exception y" I find this very unprofessional and annoying, as it makes the commit history hard to read and understand. I have tried to talk to them and explain the importance of clear and concise commit messages, but they don't seem to care. They even put emojis as variable names in Kotlin, apparently you can do it using back ticks, I didn't even know this. (edit: this seemed to be just a one time joke and they took out during code revIew. They just laugh to my teams message with a clown emoji, and a tomato? What's that even mean? How can I get them to stop using emojis in their commit messages? Is this a common problem in the industry? How do you handle it in your team? Any advice or suggestions would be appreciated. Thanks. 550 Comments Share g Unsave 162 people here (

The classic tech hype cycle in its natural habitat. First, AI writes 90% of code. Then AI writes 100% of code. Then reality hits and humans get paid premium wages to fix the AI's spaghetti code. Reminds me of that time we deployed an "automated" monitoring system that generated so many false alerts we had to hire three people just to monitor the monitoring system. Progress!

Content COMPILE TIME ERROR US RUNTIME ERROR YOU ARE TOO DRUNK TO DRIVE o 2 0 1 EXEC

This meme perfectly captures the existential crisis of C++ developers. The code creates a class called "StaticNotInventedYet" with a method that checks if "this" exists. When run with a null pointer (0x0), it somehow prints "static" instead of crashing spectacularly. But when compiled with a different flag (-O1 vs -O0), it prints "member" instead! The monkey's confused face is every programmer realizing that compiler optimizations are basically black magic and C++ just does whatever it wants. When undefined behavior meets compiler optimizations, even the language itself doesn't know what's real anymore.