The SQL Injection Feedback Loop

Content lafur Waage olafurw Off by one Sabrina sabrinaesaquino - Jun 1 Make a programmer cry with 4 words 10:53 PM Jun 1, 2022 TweetDeck

Content JUNIOR FRONTEND DEV USING NODE YARN WEBPACK BABEL TYPESCRIPT REACT REDUK AXIOS IS-EVEN CSS MODULES SASS ALENL SENIOR FULLSTACK DEV STILL USING JQUERY 1.9 AND TABLES S 2024 PARIS 202 2024 PARIS 202 TOiy 00000 imanin.co 00000 3 38

The look of pure existential dread on the senior dev's face says everything. That "hypothetical" question is the database equivalent of asking "how do I put out this fire that I definitely didn't start?" Running an UPDATE without a WHERE clause is like performing surgery with a chainsaw - technically it works, but now everything's broken. The junior just casually dropped a production database nuke while trying to sound innocent. Every DBA just felt a disturbance in the force reading this. Hope they have backups... they DO have backups, right?

Ah, the eternal dev dream: "Can AI just handle all this data conversion crap so I don't have to?" Meanwhile, every developer who's spent weeks building custom parsers for legacy government PDFs is quietly sobbing in the corner. The real treasury isn't money—it's the sanity we lost converting Excel to JSON. Pro tip: if you want to feel true pain, try parsing a PDF that was originally a scanned document from 1997 that someone converted to Word and then back to PDF again.

Content STOP DOING OS • CPUS WERE NOT MEANT TO BE SHARED! • YEARS OF SCHEDULERS yet NO REAL-WORLD USE FOUND for running more than one task at a time! • Wanted to terminate a process? We had a tool for that. It was called manual restart. • "Please give me 30 bytes of virtual memory. Please allocate it on the heap. ' - Statements dreamed up by evil wizards. LOOK at what kernel developers have been demanding your respect for all this time, with all the memory and CPUS we built for them. (This is REAL KERNEL CODE, done by REAL KERNEL DEVS): prev_state = READ_ONCE(prev->__state); if (sched mode == SM IDLE) { * This is how we return from a fork. * SCX must consult the BPF scheduler to if (Irq->nr_running 88 !scx_enabled()) { i SYM_CODE_START(ret_from_fork) next = prev; bl schedule_tail goto picked; cbz x19, 1f MOV x0, x20 } else if (! preempt 8& prev_state) { try_to_block_task(rq, prev, prev_state); switch_count = &prev->nvcsw; blr X19 1: get_current_task tsk MoV X0, sp } bl asm_exit_to_user_mode ret_to_user next = pick_next_task(rq, prev, &rf); rq_set_donor(rq, next); SYM_CODE_END(ret_from_fork) NOKPROBE(ret_from_fork) STOCALE UEFANEX drag pushO: __diag_ignore(GCC, 8, "-Wattribute-alias", dancinkage cong sysomndnes Marta, aC vecc, VA AKUS_/ attribute (altas( stringity( se systanane)))); ONGsystanane, ERRNO); _do_systinare(__MAP(X,__SC_DECL,_VA_ARGS_ _se_sysmenare(__MAP(X,__SC_LONG,__VA_ARGS__)): se sysauname MAP(X, SC LONG,VA ARGS_)) do sussunare MAP(X. SC CAST, VA ARGS. _MAP(X, __SC_TEST,__VA_ARGS_ -PROTECT(x, ret,__MAP(X, __SC_ARGS, _VA_ARGS__)): 10000 94 static inline long SYSCALL DESTEX - do systanare (_MaP(X, _ SC_DECL, _ VA ARGS_ ????? ?????? ??????????? Hello I would like to a process please. They have played us for absolute fools.

When the job description says "R knowledge required, Python mostly used," but then you show up and discover it's 99% R with that one random pandas script someone wrote 3 years ago. The classic bait-and-switch where data scientists get lured by the promise of Python only to find themselves knee-deep in R's cryptic syntax and bizarre indexing. Meanwhile, Python sits there looking all smug because everyone claims to love it, but nobody actually lets you use it for the cool projects.