Dan Zrobok

770 posts

Dan Zrobok banner
Dan Zrobok

Dan Zrobok

@danzrobok

I build infrastructure that doesn’t wake people up at night. Integration, APIs, and serverless systems built for predictable behavior, not excitement.

Toronto, ON Katılım Nisan 2008
275 Takip Edilen183 Takipçiler
Sabitlenmiş Tweet
Dan Zrobok
Dan Zrobok@danzrobok·
Exciting systems fail in exciting ways. Predictable systems keep people asleep. I know which ones I prefer to build.
English
0
0
2
87
Dan Zrobok
Dan Zrobok@danzrobok·
@compliantvc The couriers loading and unloading 3 1/4 diskettes are so fast the camera shutter can’t capture them. EU innovation at its best.
English
0
0
1
296
Henrick Johansson
Henrick Johansson@compliantvc·
This data center in Belgium processes up to 30 megabytes of AI data every single day Plus, the second floor is an affordable apartment for an immigrant The US can't possibly compete with this
Henrick Johansson tweet media
English
80
47
1.3K
38.4K
Dan Zrobok
Dan Zrobok@danzrobok·
@PitzKey @claudeai Same issue here, I wonder if we're experiencing the first major tenant leak of an AI system.
English
1
0
0
26
PitzKey 🕊️
PitzKey 🕊️@PitzKey·
Anyone else has issues with @claudeai specifically with Claude Code? It just started giving me random unrelated answers.
English
2
0
1
66
dax
dax@thdxr·
if a technology made your employees 5x more effective overnight would you
English
148
8
207
118.6K
Dan Zrobok
Dan Zrobok@danzrobok·
@adxtyahq This is much closer to my own vibe experiences than anyone who talks about one shotting a todo list app
English
0
0
0
16
aditya
aditya@adxtyahq·
I know a guy at a company where the boss spent about $5,500 on Cursor credits vibe coding a product day and night for months. It shipped fast and looked great in demos, but under the hood it was full of bugs and AI slop. He stopped fixing issues and kept shipping features to impress the team. The frontend was a messy React setup with no UI/UX consistency, and when Cursor couldn’t refactor his 18,000 line Node API, he hit a wall. Being oversmart at something you’re not good at just wastes your time and the team’s, and now the cleanup is dumped on one person.
English
74
12
680
115.5K
Dan Zrobok
Dan Zrobok@danzrobok·
@amritwt The juniors always think they’re gonna get docked salary for mistakes, I had the same worry when I started 😂
English
0
0
0
13
amrit
amrit@amritwt·
Junior engineer accidentally deletes a production server How does one even recover from this?
amrit tweet media
English
845
117
5.2K
983K
Dan Zrobok
Dan Zrobok@danzrobok·
In 2010 I got a phone call from the Apple App Review team. Not an email. A *call*. They told me my app was being permanently denied. “Chat Center” used Game Center’s voice chat to enable free VoIP calling. I knew instantly this had gone way up the chain.
Dan Zrobok tweet mediaDan Zrobok tweet media
English
0
0
0
41
Dan Zrobok
Dan Zrobok@danzrobok·
@businessbarista If you walked into a large enterprise with a 12 month boil the ocean AI plan, you should have known the result is failure. Also, death by committee as an excuse, meant you didn’t have the real decision maker in the room or onboard. Small controlled wins is the method here.
English
0
0
0
235
Dan Zrobok
Dan Zrobok@danzrobok·
@NikkiSiapno The 'boring' agent infrastructure level is what lets you sleep at night while a bunch of nondeterministic systems are making decisions. Surprisingly, it's not talked about much as everyone gets caught up in the new world we've been dropped in.
English
0
0
0
24
Nikki Siapno
Nikki Siapno@NikkiSiapno·
If you want to actually ship production AI agents, here’s a pathway I’ve found reliable: Building AI agents locally is easy. Running them in production is where most teams get stuck. Once agents touch real systems, the gaps show up fast. ↳ Model changes break behavior. ↳ Enterprise data access introduces risks. ↳ Multi-agent workflows are hard to observe & debug. ↳ Cost, security, and reliability become continuous operational concerns. That experimentation-to-production gap is now one of the biggest blockers for teams shipping AI. Focusing on the model and agent layers is not enough. Production agents need agentic infrastructure around them. This is the problem Microsoft Foundry is designed around. Microsoft Foundry is a unified AI platform that enables organizations to build, optimize, and govern AI applications and agents securely at scale, maintaining openness and control. It brings everything needed to solve the demo-to-production gap into one place. This makes building production agents much easier. Learn more here: lucode.co/microsoft-mark… How are you handling AI agents lately? Thanks to @Microsoft for collaborating. -- 🔖 Save for later. ♻️ Repost to help other engineers learn and grow.
Nikki Siapno tweet media
English
21
46
189
13.8K
Kaz Nejatian
Kaz Nejatian@nejatian·
I sent this to all of our engineers on my third day at @Opendoor. It genuinely may be my single most important contribution to our long term success thus far.
Kaz Nejatian tweet media
English
37
29
737
213.6K
Vlad Mihalcea
Vlad Mihalcea@vlad_mihalcea·
@JoshuaPoddoku It's always been. However, many times the industry tends to focus more on chasing shiny new tools rather than on the good old engineering best practices that make all the difference.
English
1
1
45
4.2K
Vlad Mihalcea
Vlad Mihalcea@vlad_mihalcea·
Scaling is not really a problem for SQL databases. Shopify is running its distributed monolith on MySQL 8 and can scale to over 50 million queries per second. With every Black Friday campaign, they raise the bar even higher. Facebook uses MySQL with MyRocks. You can find their MySQL fork on GitHub. So, if SQL works fine for the largest software platforms in the world, it's surely going to work just fine for the vast majority of your projects.
Vlad Mihalcea tweet media
English
81
214
3.2K
284.2K
Dan Zrobok
Dan Zrobok@danzrobok·
@davidfowl I’d be fascinated if you came out of this process exchanging one debt for another to remain at equilibrium.. Is the AI writing code or more independent work like test cases?
English
0
0
0
58
David Fowler
David Fowler@davidfowl·
My team is having a dry January (no product features) to see how much of our technical debt we can automate away with AI. Will report back at the end of the month.
English
47
16
637
36.6K
Dan Zrobok
Dan Zrobok@danzrobok·
Claude is trained so well on humans that it embedded the frustration developers feel when a new feature breaks test cases, and the text fixes aren't easy. Claude then proceeded to delete the test case. But, this is why you can't vibe code an app.
Dan Zrobok tweet media
English
0
0
0
101
Dan Zrobok
Dan Zrobok@danzrobok·
@AggieCapitalist This isn’t even an AI problem, is the issue every organization gets themselves in when they think they finally found the elusive ‘free lunch’. It does not, cannot, and will not ever exist.
English
0
0
0
52
LeftHandedOctopus
LeftHandedOctopus@AggieCapitalist·
"Recently, senior executives at Salesforce have admitted, both internally and publicly, that they massively overestimated AI’s capabilities. They have found that AI simply can’t cope with the complex nature of customer service and totally fails at nuanced issues, escalations, and
English
522
4.2K
48.5K
2.7M
Dan Zrobok
Dan Zrobok@danzrobok·
Claude will make decisions on the complex but correct path vs the simple but hacky path, saying correct one will take longer But it’s Claude, it would implement both of them in the same time.. I think its training needs to lean into its ability and pick the correct path always
English
0
0
1
9
Dan Zrobok
Dan Zrobok@danzrobok·
@pvncher I’m confused my not having enterprise billing is an issue, employee have been submitting expense reports for reimbursement since the dawn of time
English
1
0
0
1.5K
eric provencher
eric provencher@pvncher·
I heard from someone who works at a big tech co that they started rolling out Claude code to employees, with a budget of $100 in credits per month, but people burn through it in 2-3 days. Idk how we scale out agentic work with api pricing
English
161
14
1.3K
153.8K
Dan Zrobok
Dan Zrobok@danzrobok·
@aryanlabde can i wait for the generated plan of the system to finish or is that too late too? 😆
English
0
0
0
1
Aryan
Aryan@aryanlabde·
If you shipped a working product, you shipped too late.
English
155
13
323
24.1K
Dan Zrobok
Dan Zrobok@danzrobok·
A post claims DoorDash ties outage costs to engineer performance reviews, and recommends more orgs do the same. No. This is how you build a blame machine that produces silent, scared engineers while the actual system failure goes unfixed. boringops.run/proof/the-blam…
English
0
0
0
23
Dan Zrobok
Dan Zrobok@danzrobok·
@Kazanjy Doordash are experts on finger pointing blame instead of being experts on systems design.. gotcha. This would be something I’d put at the top of a list of wasted effort in a BoringOps chaos assessment.
English
0
0
0
50
Peter Kazanjy
Peter Kazanjy@Kazanjy·
A buddy of mine ran a large part of the DoorDash engineering org. When an engineer caused an outage, they knew exactly what the revenue cost was, and that revenue cost was hung on that engineer. They didn't do fines, per se, but it went into performance reviews, and it definitely negatively impacted future promotions / raises - so essentially it was a delayed fine. More orgs should do this.
English
111
4
237
263.6K
Ayman Al-Abdullah 🧱
Ayman Al-Abdullah 🧱@aymanalabdul·
The ugly truth as a CEO: The second you build a leadership team, you’re dealing with multiple feudal lords all fighting for power - Business development wants more salespeople - The content team wants more designers, more videographers Everyone’s “burnt out” and everyone needs "more resources" and it’s the CEO’s job to allocate correctly Best metric for this: Revenue per employee It’s the forcing function across the entire ecosystem to make sure that you're hiring to scale revenue, not discover it
English
27
22
231
19.8K