A tip for getting buy-in on frontend work: instead of “UI inconsistency,” try “inconsistent UI patterns increase support tickets by 15%.” Framing it in business metrics helps.
maecapozzi.com/blog/fronten...
The Mist played great and deserved the win. They were robbed too.
Do they know we are also watching the replay? And the announcers are constantly not agreeing with the refs?
Who the FUCK are these refs??? #unrivaled
“Is there a technology the left is excited about?”
High-speed rail! MRNA vaccines! New cancer treatments! Solar and wind energy collection! Better and longer-range EVs! That wood that's harder than steel! New apples! Fibermaxxing! Buldak Swicy ramen! Muppets! Muppets are too a technology, shut up!
Claude has made prototyping code fun enough that I want to do work coding on my days off and I have to (slightly) hold myself back from doing that extra work, or at least make sure that I take time off to make up for the time when inspiration strikes...
Conductor is changing the game for me in terms of running multiple agents simultaneously.
www.conductor.build
I might need to spend an hour per week actually writing code by hand just to make sure I remember how to do it.
What model are you using?
I think for some people there’s a feeling they’re gonna lose their jobs. which like is happening
can you believe it's been _ten years_ since @cyen.bsky.social and i started honeycomb?? jfc.
@honeycomb.io was founded to solve the hardest problems in software. in 2016, that was cloud; in 2026, that's AI. the problems have gotten worse; the stakes got higher.
www.honeycomb.io/blog/honeyco...
Sharing some vacation updates...
1. Got engaged to the loml in Mexico City
2. Wrote two blog posts that I'm extremely pleased with
3. Almost completed the MVP of the app that my fiancée and I have been working on
4. My brother got engaged to his fiancée
It's been a wonderful and not relaxing time.
I wrote about why I believe that companies that will actually have a competitive advantage in the "age of AI" are those that invest in platform work and teams.
maecapozzi.com/blog/working...
Everyone else's workflow and velocity has changed too. But, if everyone's shipping faster with AI, nobody has an advantage.
I've seen a tremendous amount of hype, and valid concern, around software engineers being replaced by AI. Anecdotally, my role has shifted significantly as AI agents and LLMs have improved.
I've been using AI agents to facilitate my work for a year. As a staff engineer, my work mostly revolves around coding, writing proposals, and driving technical strategy.
#platform #infrastructure #ai
‘The deployment of Claude occurred through Anthropic’s partnership with data company Palantir’
(gift)
www.wsj.com/politics/nat...
please give us more personal data please please please please c’mon you’re being so mean dude. we only got breached like three times. we’re NOT going to sell it man please please please plus its for like safety? so you’re the one who looks stupid right now come on pleaaaaaase just one data point bro
I’m on vacation for one week. during that week two new models drop that apparently are changing the game…trying to wait until I’m home to try it!
haha technically I helped remove it, I didn't implement it! But in general, I've enjoyed using a merge queue and see the benefits!
Really? I’ve been an engineer building design systems for 7 years now :)
I don't think these will be production-grade but I think they are very useful for hashing out requirements better before we spend many cycles turning it into production-grade code.
4. I think that we won't really need prototyping tools as much and designers can create proof-of-concepts of entire flows that we can user test.
3. I think that it may become easier for designers to "vibe code" their own designs. They can create their own feedback loops to see how what they build works & what they may need to improve before they hand it off.
2. On our team, we're already changing how designers structure Figma files. I'm working with a designer right now to change how she sets up the file so that the LLM (and honestly humans) can read it more easily and can get to the right answers sooner
It's often the last thing they work on, and so it's the worst part. This negatively impacts our customers. I'm hopeful that we can use AI to do the easier parts, and then engineers will have time to make things look and work significantly better
1. I'm hopeful that it'll help improve the general quality of UIs. Right now I see a lot of "full-stack" engineers not understand how to build high quality UI.
Today's Frontend Infrastructure newsletter issue was about driving impact as a designer or an engineer, code-splitting your webpack bundle for performance gains, and height in CSS.
Give it a read and let me know what you think :)
maecapozzi.com/newsletter/86
#frontend #engineering #webpack
Ever since Twitter was sold, it's been really hard for me to grow my newsletter. I can't seem to reach the same people with the same level of interest. Is Bluesky the place?