Mark Imbriaco

29.6K posts

Mark Imbriaco

Mark Imbriaco

@markimbriaco

Head of Engineering @ Railway. Prev. Epic Games, GitHub, Heroku, 37signals. Father of 4.

Apex, NC Katılım Kasım 2007
1.8K Takip Edilen9.7K Takipçiler
Sabitlenmiş Tweet
Mark Imbriaco
Mark Imbriaco@markimbriaco·
There's technical debt, then there's technical subprime mortgages with exploding balloon payments.
English
40
1K
1.2K
0
Mark Imbriaco
Mark Imbriaco@markimbriaco·
Credit where it's due, the initial corner logic came from @tobi and github.com/tobi/ac-tracer that he showed me. I took his advice, pointed my Claude at it, had it port it to typescript, and then iterated from there.
English
0
0
0
123
Mark Imbriaco
Mark Imbriaco@markimbriaco·
The age of personal software is pretty rad. I added this feature to my PDR review software to visualize how I attack a corner vs. my instructor from the lounge at the airport waiting to fly home last night in about 10 minutes.
Mark Imbriaco tweet mediaMark Imbriaco tweet media
English
2
0
2
432
Mark Imbriaco
Mark Imbriaco@markimbriaco·
@mscccc And lots of SSDs for the databases and file servers, before it was cool.
English
0
0
1
135
Mark Imbriaco retweetledi
Jake
Jake@JustJake·
10k new users per day Up from 3k/day at the start of the year
English
57
5
496
62.7K
tobi lutke
tobi lutke@tobi·
Turns out, you can vibecode your own motorsport telemetry tools instead of waiting for mac ports
tobi lutke tweet media
English
69
35
1.4K
135.5K
Mark Imbriaco
Mark Imbriaco@markimbriaco·
Hellebuyck should get an extra gold medal for that performance.
English
1
0
8
327
Mark Imbriaco
Mark Imbriaco@markimbriaco·
Trying to get back into working out regularly. Does the zone 2 heart rate from watching the hockey game count?
English
1
0
4
831
Jake
Jake@JustJake·
On track to spend my first new grad SWE salary on Opus 4.6
Jake tweet media
English
10
1
204
14.1K
Mark Imbriaco
Mark Imbriaco@markimbriaco·
@eligaultney @robertgraham Let’s say there are 1,000,000 people and 3% of them get the flu. That’s 30,000. If only 2% get the flu instead, that’s 20,000 people. 20,000 is 33% lower than 30,000.
English
1
0
2
30
Eli Gaultney
Eli Gaultney@eligaultney·
@robertgraham I'm maybe just doing bad stats, but the chart looks like it's 3% versus 2% between the two vaccines that were offered, roughly. So it's one extra person per 100, 1%. Very open to being schooled if I'm reading this incorrectly!
English
1
0
0
61
Jared Palmer
Jared Palmer@jaredpalmer·
Pull Requests on @GitHub can now be limited to repo collaborators or disabled entirely. This should help cut down on unwanted noise and give maintainers more control over their experience
English
85
99
1.8K
152.8K
Craig Kerstiens
Craig Kerstiens@craigkerstiens·
Random highlight from time at @heroku was working on the Python launch with @_adamwiggins_. I remember the wrestling back and forth on the blog post and how to do it. The conversation with Adam was invigorating, while a Rubyist he really appreciated certain things about the community and Python. But we were a Ruby product and came out of the Ruby community. Does supporting Python look like we're selling out, and yet of course we were doing this, but how do we do it well for everyone. And we wanted to truly welcome the Python community in. At the time there were about 5 other "Heroku for Python" newer entrants in the market. It was great to see other Heroku for X, but also they probably didn't expect us to make the leap we did as fast as we did. I personally reached out to each of them ahead of time to let them know what we were launching. We considered even hiring a few of them to help lead/drive Python on Heroku. It was older Microsoft playbook, if you're going into a space tell partners and other in the space to give a warning. RDS even did it the other direction to us about Postgres. A small detour, a thing I loved that we did, we "leaked" the Python support on HN. Our original plan was Python was going to be around the 3rd new language, it was ready to go. But because of some conference and other things the schedule for launching it slipped about 4 months. But the buildpack was live, if you shipped a requirements.txt file you got: ... Python app detected ... Yet the HN comments every month were "I hacked Heroku and got a Python app running". I smiled every time I saw it. Back on course. In the end we wrote a mini love letter to Python. These words took hours upon hours, but every minute was worth it. Being one of the few Python folks in Heroku, can't speak highly enough of how when @_adamwiggins_ pours himself into something. From the post: It emphasizes readability, minimizes “magic,” treats documentation as a first-class concern, and has a tradition of well-tested, backward-compatible releases in both the core language and its ecosystem of libraries. It blends approachability for beginners with maintainability for large projects, which has enabled its presence in fields as diverse as scientific computing, video games, systems automation, and the web.
Craig Kerstiens tweet media
English
1
2
26
2.8K
Mark Imbriaco
Mark Imbriaco@markimbriaco·
Waiting for my flight home after 2 days at racing school, so naturally I'm having Claude Code use my data recorder software to analyze my performance for me. As one does.
English
0
0
4
414
Mark Imbriaco
Mark Imbriaco@markimbriaco·
@craigkerstiens @Railway Yeah, even though it's not the Heroku of old I still hate to see them go out with a whimper like this. Feels bad.
English
0
0
1
124
Craig Kerstiens
Craig Kerstiens@craigkerstiens·
@markimbriaco @Railway Someone called out to me for that the worst part is this is from the heroku handle. It’s not the tone that would have ever been the case, if from Salesforce sure I get it. Says a lot in how things are not like they were
English
2
0
6
527
Mark Imbriaco
Mark Imbriaco@markimbriaco·
This makes me super sad. Heroku proved that developer experience shouldn't be an afterthought in infrastructure and spawned an entire category. We carry that torch forward at @Railway, but it's a bummer to see an OG go out like this.
Heroku@heroku

Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means for customers. There is no change for customers using Heroku today. Customers who pay via credit card in the Heroku dashboard—both existing and new—can continue to use Heroku with no changes to pricing, billing, service, or day-to-day usage. Core platform functionality, including applications, pipelines, teams, and add-ons, is unaffected, and customers can continue to rely on Heroku for their production, business-critical workloads. Enterprise Account contracts will no longer be offered to new customers. Existing Enterprise subscriptions and support contracts will continue to be fully honored and may renew as usual. Why this change We’re focusing our product and engineering investments on areas where we can deliver the greatest long-term customer value, including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.

English
2
0
18
3.5K