Peter Ritchie 💭

56.1K posts

Peter Ritchie 💭 banner
Peter Ritchie 💭

Peter Ritchie 💭

@peterritchie

Technologist, software architect, mentor, author, speaker, cyberneticist. Opinions my own. see also https://t.co/JlW3BZuIuU

North America เข้าร่วม Mart 2008
593 กำลังติดตาม2.8K ผู้ติดตาม
Peter Ritchie 💭 รีทวีตแล้ว
Sarah ✱
Sarah ✱@disaster_sarah·
“This hour has 22 minutes” (a legendary Canadian sketch comedy show) did a Pitt parody on the Canadian healthcare system. “Robby” using hand sanitiser every 10 seconds is taking me out 😂😂😂
English
220
2.5K
25.1K
2.3M
Ilya Ryzhenkov
Ilya Ryzhenkov@orangy·
Is it too early to start thinking about a name for “old-coding”?
English
5
0
3
1.7K
Benjamin Day
Benjamin Day@benday·
Your AI agents are writing code your team can't maintain. Working beautifully... until it doesn't. I call it Comprehension Debt.
English
1
0
3
120
Occular Malice 🏳️‍🌈
Pro Tip: Just because you can connect to your neighbor's bluetooth speaker and play ghost noises doesn't mean you should.
English
1
0
3
65
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
In light of recent news, I've cancelled my Grammarly subscription.
English
0
0
1
180
Peter Ritchie 💭 รีทวีตแล้ว
Cory House
Cory House@housecor·
This. So tired of people discounting expertise. All abstractions leak. Nearly every coding decision has tradeoffs. AI cuts corners on performance, security, validation, and accessibility. Software created without expertise is a ticking time-bomb.
Gergely Orosz@GergelyOrosz

Saying not knowing how to code gives you an advantage in building software (thanks to AI) is like saying not knowing anything about filmmaking gives you an advantage in making films (thanks to having a smartphone + apps to edit stuff) Ignore this stuff and keep learning+building

English
25
47
497
26.4K
Peter Ritchie 💭 รีทวีตแล้ว
Benjamin Day
Benjamin Day@benday·
AI helps you go faster. If your development process has problems it just makes the problems come at you faster.
English
0
1
5
155
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@benday I often respond to questions like that with "when will *what* be done?" and "What can I tell you, so you know it's actually done?"
English
0
0
1
11
Benjamin Day
Benjamin Day@benday·
'When will it be done?' sounds like a simple question. It's not. You're never predicting one item — you're predicting a pile of items landing in sequence. youtube.com/watch?v=wks_Rz…
YouTube video
YouTube
English
1
0
1
128
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@sinclairinat0r It should ask you after an upgrade "Hey, is the upgrade working well enough to clean up the data necessary to roll back to the previous version?". At some point, considering rolling back is not an option realistically.
English
1
0
0
10
Jeremy Sinclair #ฺNET
Jeremy Sinclair #ฺNET@sinclairinat0r·
Huh? That's quite a bit of space used for Previous Windows Installation(s) 🤔
Jeremy Sinclair #ฺNET tweet media
English
1
0
2
299
Debbie O'Brien
Debbie O'Brien@debs_obrien·
And here is why I and many others today were laid off
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
88
20
621
304.2K
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
When given little context, AI will generate code that doesn't match the expectations it wasn't given.
English
0
0
2
58
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@VaughnVernon You were done at "The IBM stock sell-off demonstrates how little investors understand."😉
English
1
0
1
87
Vaughn Vernon
Vaughn Vernon@VaughnVernon·
The IBM stock sell-off demonstrates how little investors understand about AI and LLM-based coding assistants. If anything, the stock should have surged 15% due to Claude Code extending the life of COBOL systems. It *writes* COBOL, which means it can be used by another generation of programmers to *maintain existing* financial systems. No, I don't own IBM stock, and I'd love to see COBOL systems replaced, but I'm not that naive to think that 67 years of gargantuan work and lock-in will go up in smoke even in the next 10 years. If you don't understand, you should work with a single bank with the goal of doing just that. Five years later, they're still scratching their heads, trying to make a single decision on *how* they can possibly succeed. What some company should do is throw a bunch of CPUs and GPUs at emulating z/OS and iSeries in the cloud. Some have tried, but the emulators fall over on load. Huh, I may have just convinced myself to buy IBM on the cheap.
English
8
11
62
7.6K
Jeff Fritz
Jeff Fritz@csharpfritz·
You can build the fastest applications, target windows Mac or Linux, use the same language on the front end, back end and everywhere between to manage your application, you can even reuse code from 25 years ago.. And the problem with .NET is that you have to use someone else’s PDF library?
GIF
English
10
0
53
4.8K
Kristijan Kralj
Kristijan Kralj@kristijan_kralj·
PDF is the main bottleneck of modern .NET development: 1. ASP .NET Core can handle thousands of requests per second, but exporting to PDF still means installing 3 NuGet packages, reading 5 GitHub issues, and hoping fonts don't explode in production. 2. We have async/await, background jobs, cloud autoscaling, and distributed systems, yet the moment the business says "Can we just get a small PDF with a table and a logo?" the whole sprint vanishes. 3. We can model complex domains, enforce invariants, and scale systems to millions of users, but aligning a table header in a PDF still feels like dark magic. .NET devs, know your enemies.
English
38
7
173
41.3K
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@jamesbender Part of it might be that when a generated test fails generated code, it regenerates/changes the code. If it didn't know how to generate passing code out of the gate, how well will it do "fixing it". AI is too human, it won't admit it doesn't know :)
English
0
0
0
17
James Bender
James Bender@jamesbender·
It’s not even about the unit tests, which are shit anyway. The first big problem is that it goes down these rabbit holes where it makes the same mistakes over and over, or it gets fixated on the wrong way to do something and can’t “break out” of that mindset, even when proven it’s wrong. And don’t get me started on its CSS abilities, which are just plain nonexistent, especially if you ask it to do crazy complicated stuff, like centering text in a div. 🙄
English
1
0
1
21
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@techgirl1908 @debs_obrien All of what went away tomorrow? I think there's an assumption you mean AI. E.g., "If AI went away tomorrow do you think you could go back to writing code by hand?" But no one was really writing code by hand before AI.
English
0
0
0
14
Angie Jones
Angie Jones@techgirl1908·
Developers who are full agent mode: If all of this went away tomorrow, do you think you could go back to writing code by hand? Like would you even want to?
English
196
11
274
56.6K
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@MicrosoftLearn Feynman technique: I try to think about how I could try to teach someone else about what I'm learning.
English
0
0
2
21
Microsoft Learn
Microsoft Learn@MicrosoftLearn·
Everyone learns differently. What’s your go‑to move when a concept just isn’t clicking?
English
34
9
80
5.7K
Peter Ritchie 💭
Peter Ritchie 💭@peterritchie·
@debs_obrien @techgirl1908 Exactly, false equivalency. People like to present and unrealistic stance to make a point but they're really just lying to themselves.
English
0
0
0
32
Debbie O'Brien
Debbie O'Brien@debs_obrien·
@techgirl1908 Its kinda like asking if I would go back to the time we wrote code without editors and syntax highlighting and had to remember things like <!DOCTYPE html>. They were fun times and Im glad I lived through the evolution but it took so long to get stuff done compared to now.
English
1
1
18
1.6K