Syntax Highlighting: Hair Edition

Content 2009 Querv 2019 A node mom B ES6 i webpack V BABEL

Content Pratham Prathkum Created Ferb using CSS. eyetsbefore contents helonts 12pxi eyet 4 5:18 am 15 Jan 2022 Twitter for iPhone

Content Fscript var containers document .getElementsByClassName ("category-container"); for (let i 0; i containers.Length; i) 1 containers i.addEventlistener ('wheel', (evt) evt.preventDefault); containersi.scrottleft evt.deltaY; 1); "deltaY" should probably not be assigned to 'scrollleft script var containers: HTMLCollection0fElement odiv class-"categ app-modulescategoryfilters.html 1 for tag in opportulisttemplate div clas page else '" " s if searchQuery

Content Giulio Carrara 3rd Software Engineer 1d Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - nix system administration - Git and Cl with TDD - Docker, Kubernetes That's not a Full Stack Developer. That's an entire IT department. Yours truly 8,801 391 comments

Oh. My. God. The AUDACITY of our New Year's programming ambitions! 🤡 Every January, we transform from basic developers into full-blown circus performers with our GRANDIOSE declarations! "I'll master Python!" (applies first layer of clown makeup) "I'll become a backend wizard!" (adds tearful blue eyeshadow) "I'll create CSS ART, for heaven's sake!" (dons rainbow wig) And by December? We're the COMPLETE CLOWN, honking our red noses at the ONE tutorial we barely finished. The transformation is INEVITABLE, darling! Our ambitions are writing checks our commitment simply cannot cash!

Someone asked an LLM to fix a simple UI bug and watched in horror as it burned through 177,000 tokens ($$$) to essentially do what a human could've done in 5 minutes. The AI went full detective mode, investigating websocket reconnect logic, spawning THREE sub-agents to explore server architecture, adding debugging lines, and writing a whole Playwright test suite. All to fix a timing issue that probably needed a setTimeout() and a coffee break. The best part? It actually solved the problem correctly. But at what cost? Your AWS bill is crying. Your product manager is asking why the API costs tripled. And somewhere, a junior dev who could've fixed this for the price of their salary is updating their resume because they've been replaced by a $200 bug fix. Fun fact: 177k tokens is roughly the length of "The Great Gatsby." So basically, the LLM wrote a novel about your websocket connection instead of just... fixing it. Efficiency at its finest.