Now It Makes Sense

Someone wrote a method to count employees, but there's a tiny problem: it deletes ALL the employees from the database first, then counts how many are left. Spoiler alert: zero. Every single time after the first run, you're counting an empty table. The function technically works once—before it nukes your entire workforce into the digital void. The best part? They're using using statements for proper resource disposal, so at least the database connection is being cleaned up responsibly while the employee data gets yeeted into oblivion. Priorities, right? Pro tip: maybe fetch the count BEFORE running DELETE FROM. Or better yet, don't run DELETE FROM at all when you just want to count rows. That's what SELECT COUNT(*) is for. Your HR department will thank you.

Content rwebdev Posted by ufuturewebdev 12h Are front-end devs looked down upon by others? Tech 1 keep getting this vibe online that back-end developers think front-end work is for simpletons (for the lack of a better word). Is this true or am I imagining things? 4 255 354 A Share Award BEST COMMENTS QuestionsHurt 10h 6 2 Awards Yes, yes it is. But then again Web development in general is scoffed at by most other developers. Programmers are scoffed at by "real" Engineers. Engineers are belittled by physicists. Physicists by Mathematicians. Mathematicians by Artists. Artists by designers. Designers by frontend developers. Circle of life. Reply 4 1,0k ProarammerHumor.io

Content Tell me the truth.I'm... 'm ready to hear it. YOU SHOULD HAVE WRITTEN THIS PROJECT IN A DIFFERENT LANGUAGE imaflip.com

Content Roni loves Chachi moonpolysoft Nerds: let's do a hackathon to find ways that programmers can fight covid-19 NJ Gov: unemployment system is falling over and we need COBOL programmers Nerds: not like that,

The media: "HACKERS BREACH TEA DATABASE IN SOPHISTICATED CYBERATTACK!" The actual "hack": requests.get(PUBLIC_URL) Nothing screams "senior developer energy" like seeing Python code that's just fetching publicly available JPG files being labeled a "hack." It's like calling yourself a master chef for successfully boiling water. The real security breach here is whoever decided that putting files in a publicly accessible URL with zero authentication was a good architecture decision. That person probably also uses "password123" and wonders why they keep getting "hacked."

Content My SQL query turns one month old today after running for 720 hours 0111111152.7 3111111152.5 6111111144.0 911111151.3 11111149.3 4C11111154.9 7C11 43.6 10111111152.9 2111111 46.5 5 64.7 8 55.6 11111 18.7 111153.0G62. 7G SwpI 111.151.39T PID USER PRI NI VIRT RES SHR S CPU MEM TIME Command 3921466 postgres, 30 10 1710G 7464M 2316 R 95.0 11.6 681h postgres: F1Help F2Setup F3SearchF4FilterF5Tree F6SortByF7Nice -F8Nice F9Kill F1 NAME TYPE SIZE USED PRIO devsda3 partition 321.4G 321.4G -2 swapfile file 400G 400G -3 swapfile2 file 300G 298.4G -4 swapfile3 file 400G 162.1G -5 I hope I don't have to buy another ssd to add as swap because I don't have any more drive space to save it from the OOM killer if it continues to grow. ProarammerHumor.io