Author of š„Kill It with Fireš„Maintainer of safety critical systems, pondering anti-fragile AI, gleefully mediocre Formal Methods practitioner.
Joined January 2009
- Tweets 3,397
- Following 308
- Followers 3,655
- Likes 2,092
183 Photos and videos
I'm going to be talking about Fault at @strangeloop_stl this year! š I'm going to struggle to live up to all the great languages that have debuted there ššš
2
1
15
2,502
Marianne retweeted
17 Nov 2024
Recommended reading (and maybe advisor): "Kill it with fire", by Marianne Bellotti @bellmar
1
1
2
377
So much fun hanging out with rural broadband providers. They do such important work so it was an honor to be asked.
28 Oct 2024
The 2024 #CyberShare Summit is underway in Louisville, Ky. Yesterday kicked off with workshops & a visit to @SluggerMuseum. This morning, participants heard from @bellmar, software engineering expert & author, & participated in a friendly maker space competition.
1
4
628
Marianne retweeted
31 May 2024
šļø Marianne Bellotti talks about āMurder Boardsā, which started at NASA as part of the engineering process. āSometimes murder really is the best way to get through a hard problem.ā šµļø #craftconf @bellmar
1
2
5
730
Marianne retweeted
31 May 2024
'It's not about attacking people it's about attacking plans" -@bellmar @CraftConf
#CraftConf #Craft2025ready
1
4
424
Iāll worry about AI when AI can pick up a shift on an on call rotation.
Well actually ā¦ I wonāt worry, Iāll be on a šļø somewhere š But point is tech decisions only matter in the context of operations. If it canāt be maintained, it doesnāt matter how fast/cheap it was to build
2
17
2,687
Marianne retweeted
9 May 2024
I can typically sort meeting information into three buckets: things that are true, things that are false, and things that are true but irrelevant
ā @bellmar, Kill it with Fire
1
1
6
1,465
Itās amazing how often the answer to the question āwhy didnāt you do it this wayā is ābecause that technology did not exist at the timeā ššš
20 Apr 2024
At big companies you often run into old terrible code thatās still not been fixed and curse the person that wrote them years ago. Iāve done it plenty, I canāt help it.
I was once the first engineer at a startup and was there for 14 years. So Iāve been in meetings where a developer was cursing whoever wrote some piece of crap 10yr old code, and it was oftenā¦me. Why didnāt you use the factory pattern, why didnāt you document store this instead of using mysql, etc.
So sometimes I try extra hard to remember that smart well-intentioned people made the best decisions they could using the information they had at the time. The tradeoffs they made aren't always immediately obvious a decade later. But the fact that the project is still running 10 years later is a testament toā¦something.
Also- this is why you/we were hired; to fix the shit code instead of just complaining about it.
7
917
Marianne retweeted
20 Apr 2024
At big companies you often run into old terrible code thatās still not been fixed and curse the person that wrote them years ago. Iāve done it plenty, I canāt help it.
I was once the first engineer at a startup and was there for 14 years. So Iāve been in meetings where a developer was cursing whoever wrote some piece of crap 10yr old code, and it was oftenā¦me. Why didnāt you use the factory pattern, why didnāt you document store this instead of using mysql, etc.
So sometimes I try extra hard to remember that smart well-intentioned people made the best decisions they could using the information they had at the time. The tradeoffs they made aren't always immediately obvious a decade later. But the fact that the project is still running 10 years later is a testament toā¦something.
Also- this is why you/we were hired; to fix the shit code instead of just complaining about it.
68
69
1,005
130,353
My advice: take a job at any company thatās 11 years old ššš
6
620