Frontend vs Backend: The Sock Edition

You know that code that's been running flawlessly for 5 years? The one written by that dev who left the company and didn't document anything? Yeah, some hotshot just decided it needed "optimization" and "clean architecture." Now your Slack is blowing up, the CEO is calling, and somewhere a database is crying. This is why we have the sacred developer commandment: "If it ain't throwing errors, don't fix it." Nuclear meltdown is just nature's way of saying you should've left that legacy spaghetti code alone.

Content When you copy a snippet from StackOverflow and it doesn't work Those bastards lied to me

Content Yep Youre checking my password is hard to guess, right? So that means high entropy Yep And any further restrictions would reduce the entropy That makes sense to me Password: correcthorsebatterystaple Error: password must contain uppercase, lowercase, numbers, and especial charso

Content Matt Watson 2nd 4x Founder, CTOCEO, Podcaster, .. Follow View my blog 3d "Technical debt": Move fast and don't fix things "Agile development": Admitting you have no plan "TDD": Guessing the future, one test at a time "Open source": Asking someone else to fix it "CICD: Automating your mistakes into production "API": Asking someone else to do it "DevOps": The belief that more tools fix any problem "Microservices: Creating enough small problems to avoid one big one "Cybersecurity": Playing hide and seek with hackers "Serverless": Pretending servers don't exist until the bill comes "Scrum": Group therapy for being behind schedule

Content isfp isfp my talent is identifying birds 12:37 PM 30082021 17 intj intj okay. what's this one? 2 m v isfp isfp yep it's definitely a bird 17

Content CERE PERE CCCC