Joined April 2013
75 Photos and videos
Pinned Tweet
21 Nov 2020
Replying to @ollermi
It’s fully programmable now 🤩 Here it is adding 18 24. Only thing left is to make it Turing complete so it can be a “real” computer. All we need to do that is a conditional jump instruction 🏃🏻‍♂️
6
Miguel Oller retweeted
The fallacy of this is that more creates more. More hours, more hiring, more something. And it is true in a sense. If you put in more work, more work will happen. But I think for most startups, the leverage is really in how differently you approach the problem, how well you cultivate your team, and the strategy. Any large company can outspend you on hours. They have thousands or tens of thousands more people, spending more hours. If hours worked were the metric, every large company and government organization would always win and do the best work. More hours, better output. This thinking is often representative of younger founders, where the startup becomes their identity and life. They have a hard time doing anything else, and cannot understand that your work is not the person that is you. But activities outside of work can grow you as a person too and make you do better work. I’ve never worked this way. As a designer, I always saw the need to take a step back, to take a break. At times, I might work 12 hours or 16 hours, or whatever amount was needed, but it wasn’t the norm. You just can't grind design, you need inspiration. But taking that step away from the work, would give me more perspective, inspiration and I could approach the problem differently or I could just see the solution. Grinding is never good for any creative problem, and startups or creating new products are often mostly about creative problem solving. Grinding works ok for email jobs, or where you just executing on very clear playbook. With Linear, we’ve never worked this way. We work reasonable hours, 5 days a week. All of us founders have families. Many of our employees have families. I personally stop every evening, spend time with the family, cook dinner for the family, eat dinner together, and focus on things outside of work. Sometimes I work in the late evenings or weekends, but to me the pride is that I don’t need to. Company should be succesful without it. My goal is to build a company that is sustainable in the long term, and doesn’t require heroics or personal sacrifices every single day. There are times when our team is heroic. Launches, incidents, some other work that just needs to be done. They will work late into the night because they know it is the right thing. But we don’t require that every day or every week, and the more this happens, the more I think it is a failure of our company and leadership. The team and the leaders should always keep a reserve to use when something is needed. Our thinking was also that quality, which we value, doesn’t emerge from working more or stressing people more. It emerges when you create the conditions for it to emerge. Often it is the appreciation, space, time, and how the person feels. A person who is rested will do better work. I wouldn’t attribute much of our success to working a lot. The success came from having clear thinking, ideas, and focus to do the right things. I sometimes wish we could move the culture more toward a Zen master. Real mastery is not exerting the most effort. It is achieving the outcome with the least necessary effort.
"If you are not working 7 days per week, you are going to lose". Corgi Insurance is the most intense workplace culture in startups. - The company works 7 days per week. - Founder (@nico_laqua) lives and sleeps in the office. - He built a cafe in the office because there was no local cafe that was open 24/7. - 2/3 of the first 30 team members have the Corgi logo as a tattoo. Today I went behind the scenes with Nico, who has used this culture to scale the company to a $2.6BN valuation in just two years. My condensed notes below: 1. If You Are Not Working 7 Days Per Week, You Are Going to Lose: Whatever you can get done in 5 days, you'll get more done in 6 and 7. If you are trying to solve the world’s hardest problems, a standard 5-day workweek will not cut it. 2. Work Trials Repel the Mediocre: Corgi forces candidates into mock work trials over the weekend. If seeing a full office on a Saturday scares them, they don't belong. True intensity acts as a natural filter to attract killers and repel clock-watchers. 3. Lead from the Front Lines You can’t demand 7-day weeks while sitting on a yacht. Nico sleeps 3–4 hours a night on a mattress inside the office. If you want your troops to bleed, you have to be in the trenches with them. 4. Culture Only Means One Thing: Winning Forget superficial jargon like "hackers" or "ex-founders." Strip away the corporate fluff. A great startup culture is aggressively optimized around one single word: Winning. 5. Lifespan vs. Victories Building something world-historic requires radical sacrifice. When asked if he'd rather build a trillion-dollar company and die at 50, or fail and live to 80, the answer was easy. "I would rather measure my lifespan in victories." 6. Reject the Comfort of "Quiet Quitting." If you are operating in a hyper-growth environment and your days off happen to be Saturday and Sunday every single week, you are quiet quitting. To win, you must deliberately bypass the off-ramps of personal comfort and low volatility. Corgi isn't for everyone—and that’s exactly the point.
157
444
5,104
1,345,576
Miguel Oller retweeted
Excited to share our progress on @GitHub Stacked PRs 🥞
46
31
790
106,307
Miguel Oller retweeted
Mar 23
You can now enable Claude to use your computer to complete tasks. It opens your apps, navigates your browser, fills in spreadsheets—anything you'd do sitting at your desk. Research preview in Claude Cowork and Claude Code, macOS only.
4,920
14,292
138,613
78,058,016
Miguel Oller retweeted
and so it begins
Feb 26
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
15
2
184
29,186
Miguel Oller retweeted
21 Nov 2025
if you can read the first one, you can read the second one
38
12
309
61,181
Miguel Oller retweeted
11 Oct 2025
Bun v1.3 is our biggest release yet
41
78
1,088
122,581
Miguel Oller retweeted
Introducing Zod 4.1 and its flagship feature: CODECS z.codec() is a new API for defining *bi-directional transformations* in Zod
92
214
3,160
308,049
Miguel Oller retweeted
14 Feb 2019
Replying to @OpenAI
Society needs to adapt, fast. We risk having a large group of people fooled by a few wielding these superpowers. Indeed having widespread AI looks more and more as the right solution—knowing what’s possible protects you from being a victim.
3
14
Miguel Oller retweeted
11 Aug 2025
Last month, I stepped away from my role working on Next.js. I've been reflecting on that journey and wanted to write down some thoughts on the state of the React community. leerob.com/reflections
42
56
929
71,885
Miguel Oller retweeted
The video you've all been asking for youtube.com/watch?v=S2GChOwi…

28
48
522
136,592
Miguel Oller retweeted
1 for "context engineering" over "prompt engineering". People associate prompts with short task descriptions you'd give an LLM in your day-to-day use. When in every industrial-strength LLM app, context engineering is the delicate art and science of filling the context window with just the right information for the next step. Science because doing this right involves task descriptions and explanations, few shot examples, RAG, related (possibly multimodal) data, tools, state and history, compacting... Too little or of the wrong form and the LLM doesn't have the right context for optimal performance. Too much or too irrelevant and the LLM costs might go up and performance might come down. Doing this well is highly non-trivial. And art because of the guiding intuition around LLM psychology of people spirits. On top of context engineering itself, an LLM app has to: - break up problems just right into control flows - pack the context windows just right - dispatch calls to LLMs of the right kind and capability - handle generation-verification UIUX flows - a lot more - guardrails, security, evals, parallelism, prefetching, ... So context engineering is just one small piece of an emerging thick layer of non-trivial software that coordinates individual LLM calls (and a lot more) into full LLM apps. The term "ChatGPT wrapper" is tired and really, really wrong.
19 Jun 2025
I really like the term “context engineering” over prompt engineering. It describes the core skill better: the art of providing all the context for the task to be plausibly solvable by the LLM.
530
2,051
14,341
2,380,484
Miguel Oller retweeted
29 Jun 2025
As promised, how to generate both client AND server from Effect Schemas. This one's a bit longer today, thank you for your patience, and as always.. Use @EffectTS_ !
3
9
243
35,933
Miguel Oller retweeted
9 Jun 2025
Having no experience did not stop me from making a VTOL with world-class range and flight time, all in 90 days. This is the thing I'm most proud of building to date!
84
197
2,162
414,896
Miguel Oller retweeted
296
1,285
8,672
1,163,713
24 Dec 2024
Nice Christmas present 🎁☺️
100%. Ready to go. The release will probably be on the 26th though so I can take time to enjoy the holidays with my family without stressing about inevitable launch day issues. For those interested: thanks for hanging in there, not long now. Happy holidays y'all. ❤️
71
Miguel Oller retweeted
Web development has evolved through major shifts—from the early days of server-rendered pages to the explosion of single-page applications, and more recently, the rise of static site generation. Hearing @jamesqquick explain how @MakeswiftHQ and @nextjs are pushing this evolution further was fascinating. They’re blending static-first principles with dynamic capabilities like incremental static regeneration and partial pre-rendering. The future of web development is all about smarter, more adaptive frameworks—and it’s exciting to see where we’re headed! Check out the full episode—link in the comments. 🚀
1
2
12
1,144
Miguel Oller retweeted
. @ollermi is the co-founder/CTO of @MakeswiftHQ and has a great startup career story. After graduating from Georgia Institute of Technology, he founded several companies, including Shortweb and BloveIt, before becoming co-founder & CTO at Makeswift, which was recently acquired by @BigCommerce. Last week, we sat down for an episode of Monetizing SaaS and talked about ten years of building on React, lessons learned about commercializing & building products, establishing trust with co-founders, and hyperbolic learning chambers :-) In this clip, he talks about what Makeswift has taught him about pricing & packaging in SaaS. "The one constant in startups is that pricing will change. We've continuously experimented with different models—per page, per user, per site. Aligning price with the actual value the customer receives has been the key learning… From a technical perspective you want to be able to support the change without distracting from core product development." Listen or watch now👇 🎥 Youtube: tinyurl.com/3wfwja3e 🎧 Spotify: tinyurl.com/mrycsv27 🍏 Apple: tinyurl.com/yh3mcxs4 Key Takeaways: 1. Experimentation and change: A flexible architecture for managing pricing, packaging, and subscriptions is essential to handle ongoing change without starting over. 2. Pricing complexity: Finding the right price metric for Makeswift has been an ongoing pursuit. From per-page to per-user to per-site pricing, each method had trade-offs, but the goal is to align pricing with value. Makeswift is now experimenting with pricing based on "change frequency," reflecting how often customers modify their sites—an approach that ties value directly to product usage. 3. Career North Stars & Dragon Ball Z —  For Miguel, startups are hyperbolic time chambers — environments where time is condensed & people grow much faster than they would in the outside world. "Your rate of learning is a perfectly acceptable career north star." For startup founders, Miguel’s story is instructive & resonant. If you're building a startup, highly recommend this episode!
2
6
165
Miguel Oller retweeted
Going to conferences WILL CHANGE YOUR LIFE! At @RenderATL this past summer I met the amazing team at @MakeswiftHQ and last week I started working with them full-time 🔥 🔥
6
5
66
6,170
Miguel Oller retweeted
8 Oct 2024
👀 Great news! Vercel is adding route-level middlewares (Request Interceptors) in @nextjs (link in replies)
15
25
457
98,646
Miguel Oller retweeted
8 Oct 2024
📹 Self-Hosting Next.js Learn how to deploy Next.js, Postgres, and Nginx to a $4 VPS with Docker. I'll explain how to use and configure Next.js features like image optimization, caching & ISR, streaming, middleware, server components, and more. Demo app is open source!
141
431
4,220
568,153