When you no longer read the code, you want to pick the language that runs everywhere.
Unless you’re doing something super niche, Typescript is the answer.

Browse by month
When you no longer read the code, you want to pick the language that runs everywhere.
Unless you’re doing something super niche, Typescript is the answer.
People will start to wake up to the fact that a monorepo is an anti-pattern for large projects.
We've had such great freedom and life improvements since switching from a giant monorepo to many pico repos 6 months ago. It's like we got rid of the chains holding us back.
General intelligence is getting cheap, but specific knowledge is only going to get more expensive.
Domain experts see things others can't, and things no model was trained on.
It's very easy for AI to lead people down a wrong path and the cost of getting it wrong is higher now.
Every second spent building somebody else's company is a second not spent building your own.
Every second spent on marketing is a second not spent building something worth talking about.
Every second spent polishing the pitch deck is a second not spent building your product.
Every second spent chasing funding is a second not spent on making revenue.
I think most people will own a business in the future.
They kinda already do. When you work for somebody else, it's like your employer is your only customer.
If you want to make more money, you need more customers or the few customers to pay you more.
When you have few customers that spend a lot, they demand more from you and their managerial role over you is stronger, so it feels like being an employee.
If you want to be sovereign, you need to have a lot of customers.
But when you have a lot of customers, it’s infeasible to provide custom products and services to each of them. So your business becomes product-based, or an automated service.
When you have lots of customers, losing each individual customer costs you less.
The biggest risk will be working for somebody else and losing the only customer (employer) that you have.
Why take that risk if you can run your own business with a team of AI agents working for you?
I’ve seen this exact failure mode kill the 3D printing industry.
I’ve worked in photolithography (semiconductor additive process), CMP (semiconductor subtractive process), and metrology (semicondutor measurement process), also at a 3D printing unicorn, and also ran my own 3D printing business.
3D printing was supposed to disrupt traditional manufacturing, but never got past prototyping, never achieved high volume, and yield is still pretty low even with the most advanced machines.
Semiconductor chips are as complex as an airplane, made at higher yield and volume than almost anything else humans build. The reason is that every additive step is followed by a subtractive one and a measurement. Errors get corrected layer by layer instead of compounding.
3D printing is purely additive. A defect on layer 10 propagates to layer 100. The best a very advanced system can do is add less material in later layers to compensate. I’ve never seen that work well, even with fancy AI predicting material behavior.
Current coding agents are purely additive and I believe that’s of the cause of over 60% of slop.
Code should be just an output of a higher level process.
That way, you can improve the process, and all the code improves as a function of it.
Instead of fixing bugs, you eliminate failure modes.
Our vision for the future is much bigger than what one git monorepo could support.
3 contrarian takes that we’re betting on for the future of AI software production:
1. A monorepo is a structural anti-pattern
Monorepos exist because coordinating across many repos was expensive when that cost was priced for human coordination. But now you can automate coordination with agents handling the cross-repo changes and pull-based flows replacing manual syncing.
We're betting on having thousands of pico repos. The benefits: a clear authorization boundary for what agents can autonomously act on (agents don't have write access to critical infrastructure repos, for example), reduced token cost, and independent evolution, where each repo improves on its own while the whole ecosystem can benefit from it.
--
2. PRs are a waste
Human review is the new bottleneck, and one person can't manage thousands of agents through a review queue, so in the age of AI software production, a PR is pure friction.
Now that software can be just an output of a spec, if you have a problem, find the root cause and fix the spec so it never happens again. The human stops reviewing code and starts continuously improving the process to catch and prevent defects.
--
3. No need to look at the code
No one will read code, the way no one reads assembly anymore. We stopped reading compiler output the moment we started trusting the compiler; we will stop reading generated code the moment we start trusting our means of software production.
Humans write the spec and define what "good" means, and code becomes just an output of that spec, written by agents. The spec, the single source of truth, leads everything downstream.
I’m building the product that most teams will eventually use to exponentially improve while producing software at high scale and high yield.
Once people start noticing it is orders of magnitude better than anything else that has ever existed, we will be ready for takeoff.
3D printing never took off because it failed to solve scale and yield.
I think I know the reason why:
Semiconductor manufacturing is the most sophisticated, highest volume, and highest precision production process in the world.
My career after college started as a photolithography engineer at TI.
There, I learned how to build and monitor processes that scale, how to lead teams, and how to drive continuous improvement across cost, scrap, and yield.
Now I’m seeing the same revolution happen in software. Building, testing, and deploying software end-to-end at high scale and high precision requires the same rigor.
Supply chain optimization, inventory control, yield management, continuous improvement. These lessons from semiconductor fabs apply directly.
I’m grateful for my time at TI. That experience shaped how I think about scale, precision, and process control. And it’s exactly what I’m applying now: creating and optimizing the processes my AI workers follow to build better than I could myself.
I don’t vibe code anymore.
I build and optimize processes that my AI workers follow to vibe code better than I would myself.
Everything is spec’ed, from how the code has to be written to every pixel you see in the UI.
Test-driven-development, RCA, validation, rollout, process control, all done by AI.
My work has shifted to finding ways of optimizing the processes, choosing trade-offs, and defining the vision.
So far, I feel like I’ve reached an exponential improvement curve.
Keep Calm. Problems are Solvable.
My first internship was very interesting.
I was a sophomore in college and worked in the Quality department at Siemens.
My main activity was helping an instructor teaching engineers Root Cause Analysis (from 5-Why to KT), risk assessment, corrective/preventive actions, etc.
I did the same training multiple times and it was very in-depth. For example, we spent a lot of time learning how to define a problem statement because everything else depends on it.
After that role, I worked in R&D, my own business, semiconductor manufacturing, startups, etc. Everywhere I worked, I was able to apply that training. I believe it's a big contributor to the success of big companies that have this knowledge: solving problems and eliminating root causes.
In the age of AI, you shouldn’t be trying to grow your thing.
You should be trying to build something that can grow on its own.
Build something only you could.
I love the work I get to do every day. It's fun!
I go to bed excited about what I'll do in the morning.
I wake up and don't want to waste any time, so I jump straight to it!
My dream is to do this for the rest of my life.
Here's my general advice for building a successful startup:
1. Don’t blindly follow anyone's advice, including this one.
2. Build a great foundation; don't build a temporary shelter, build a skyscraper.
3. Build before you sell; sales are much easier when you have a great product.
4. Build a great product; the market rewards those who create genuine value.
5. Adjust and adapt daily; this is your biggest advantage over big companies.
6. Master prioritization; your most important role should be prioritization.
7. Do things that scale; prioritize efforts that can compound and multiply impact over time.
I was born in one of the poorest areas in Brazil. My mother was pregnant with me at 14, and I was raised by my grandparents until I was seven. My mother was a housemaid.
Something that always stood out about me was a strong desire for continuous improvement and building a better life. I always strived for excellence in everything I committed to doing.
I immigrated to the USA and lived in this country alone without my family. I also became an engineer and worked to support myself while pursuing my degree. After college, I started my own company, worked for a large corporation, and also for a unicorn startup.
But self-improvement isn't just about moving up in your career. For the past three years, my top priority in life has been my health. I've learned that if you want to play the long-term game, you must be in good shape.
The thing is, many times, I went down the wrong route. This is especially true for my fitness journey. I actually started it back in high school, always going on and off with the gym. It took me years to commit, learn proper form, and enjoy working out. That's only when I finally started seeing results.
Another challenge was wasting a lot of time and effort duplicating work and solving problems that had already been solved because I had no idea these solutions already existed.
Many times, I had no idea what to do and had to read hundreds of search results on Google just to find something that would finally be a partial fit for me and my circumstances. Don't even mention having to scroll through all the ads on those pages.
I have had countless achievements, but also countless failures. Most of my failures were due to getting sidetracked, derailed, and losing track of what I truly wanted to achieve in life.
The idea for socra started with a simple yet profound question: “What do I need to do today to achieve my long-term goals in the future?" Well, a supercomputer knows the answer to that question better than we do.
Imagine how much time and effort it would have saved me if I had a system that would help me plan, track, and navigate my goals from start to finish.
So I quit my job to start socra - a platform to help people crush their goals. There's a reason the tagline says "crush" and not "achieve". socra is not a habit-tracker, not a to-do list, not a note-taking app, but your second brain on your journey to success.
I don't care about product-market fit, niche, networking events, or fundraising. I unplugged from the matrix. The only thing that truly matters is to continue to improve the platform that helps you make progress towards your goals and in the right direction.
socra is built by people who understand the challenges of achieving goals for people who want to make meaningful progress in their lives.