Diego (@DiegoCode_) profile picture

software dev

Minneapolis, MN
Joined December 2015
Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)Photo by Diego (@DiegoCode_)
Replying to @AdamRackis
Let’s go I’ll try to make it to this one 😎
1
12
My supervisor is hard at work. Making sure I am using AI at the fullest.
1
23
Replying to @marktechson
😎 yt music W
1
4
Replying to @marktechson
Should’ve gone to Uniqlo that place hasn’t missed for me yet 🤣
1
1
11
Replying to @marktechson
Been there lol
1
15
Replying to @maxifirtman
Bienvenidos!
2
Replying to @nicknisi
Cool! 😎
13
Diego retweeted
you dont really need a mop if you just get a dog
6
1
31
3,896
Replying to @nicknisi
`extraordinary circumstances` is not something you want to hear while on a flight lol
43
Replying to @AdamRackis
Sheesh
1
23
That thing looks like fun!
25
Replying to @orcdev
My agent is
22
😢🫡
Portugal estará sempre em mim
46
I just completed "Inverse Captcha" - Day 1 - Advent of Code 2017 adventofcode.com/2017/day/1 doing #AdventOfCode with @andrewhoyer group doing warm up for 2026s adventofcode. lets see how far i make it this year
1
1
1
126
Diego retweeted
Guys literally only want one thing and it's ground beef and rice
when my wife is out, I fallback to my factory settings
145
14
6
1,516
98,000
The more pain you can eat on behalf of your customers, the bigger your moat
Your job is to eat the pain. @aarondfrancis taught us all that pain doesn't disappear. Someone eats the pain. The questions is "Who will eat it? You or your customer?" Or as Aaron put it, "Be the sin eater."
20
18
9
358
16,630
one of the best talks i’ve watched in past few years
Your job is to eat the pain. @aarondfrancis taught us all that pain doesn't disappear. Someone eats the pain. The questions is "Who will eat it? You or your customer?" Or as Aaron put it, "Be the sin eater."
9
20
1
505
35,209
“Patch the planet, we can fix everything” is one of the most misleading, and harmful security initiatives I’ve seen. As if spending billions of dollars cooking the oceans to run swarms of agents spinning their wheels applying hourly? minutely? patches on every abandoned instance across the planet, racing against every incompetent sysadmin - no you will never catch up with human stupidity. And it’s completely the wrong direction. It’s this old school mentality that “I’ll stay in my IT lane, and just update every package and infra” as if this will ever amount to anything. As if this hasn’t been the strategy for half a century. Obviously you’re supposed to patch. But why be a hamster in a wheel spinning idly, while incompetent devs slop-cannon millions of lines of some of humanity’s most atrocious code ever conceived, bypassing every security recommendation, every known best-practice, to meet an arbitrary deadline set by their private equity overlords to ship some inane b2b saas that nobody is going to use, but will get everyone’s data leaked. You won’t patch everything. You won’t catch every bug. You know it’s stupid, it’s a helpless strategy because you don’t want to address the real root cause: making software that doesn’t suck ass. Engineering principles that aren’t guided by psychotic greedy men in suits that just want a return on their investment at the cost of everyone’s data. The problem is nobody gives a shit about breaches. “Cyber insurance covers this”, you send the breach notification, everyone shrugs as if it’s the accepted cost of living in society. So companies have no incentive to care. Some of the most incompetent passionless people become “engineering leaders” that “understand the business” of shipping atrocities, without an ounce of consideration or thought, pure monkey level poop-slinging. The worst code you’ve ever seen is production code, self-merged by the guy thinking increasing shareholder value is how you barely make it across the retirement line. “Move fast and break things” has been one of the most dangerous principles, and an embarrassing one to hold today. We have solutions. The dumbest dev can still ask a coding agent to find, explain, and address security issues in software architecture, and in implementation. And it does a better job than the majority of security engineers I’ve worked with. But they do the opposite. They go AROUND and bypass every security recommendation anyone or anything makes. I’ve seen Claude-generated comments in code saying “this is highly insecure but we have decided to accept the risk” for things with trivial fixes. God forbid, you’re going to have to work with devs. Teach them software design, architecture, planning how components and microservices interact, how to make safe code, how to keep it safe, ultimately just to be considerate. To care a little bit about your craft. “Patch the planet” is a waste of time. Invest in what we ship instead. It’s the ONLY way to make software resilient.
27
46
8
299
12,336