Great systems= great life!
1) If you are a student. Build projects, side gigs, your personal brand.
Use your time to "build", not "consume".
And, consume mostly to build.
2) If you are just starting a job, build a system of efficiency.
Get things work done fast, efficiently.
Become indispensable for your boss.
People who are needed, almost never get fired.
3) If you reach middle management, replace your salary with your income from assets.
This lowers your stress. And, builds optionality.
4) If you become a HNI, build a system of wealth diversification.
Split wealth across 3 countries. And, 3 asset classes.
Pay close to 0% tax.
Let your wealth build more wealth.
Save time. Enjoy your wealth.
5) If you become an UHNI, build a Foundation/Trust. Think legacy wealth. And, succession planning.
Enjoy your wealth.
****
At every stage learn practical things from folks, who have been there done that. And, ignore 99.99% generic advice out there.
Reading a tutorial and terms like exponential backoff, jitter, and idempotency keys makes sense. Then you build the thing, the API returns a 500, and you watch your system crash.
The happy path is the part everyone writes about. The request succeeds, the response looks like the example, and the system behaves. That is maybe 20% of the actual code you end up shipping.
The other 80% is what you only discover by running the thing under real conditions. A queue that is supposed to be FIFO but is not under load, a dependency that is "always available" until it is not, or a database connection pool that gets exhausted when 3 slow queries stack up during a deploy.
Hence, reading 10 blog posts about a system is no substitute for spending a weekend building it. The bugs you hit while building it (or, better yet, while running it in production) are the actual curriculum. The blog post is just the syllabus.
Reading teaches the happy path. Building teaches the failure modes. So keep coding and keep shipping.
Hope this helps.
This takes like 2 min to read and is the simplest explanation of the “loops” everyone is talking about.
Why can’t we all just speak in plain English instead of trying to make every single ai coding concept seem bigger than life?
I think we know why but still
Back to writing 😃
My take on the power of vibe code token-maxxing and why engineering fundamentals matter more than ever now
Do check it out
https://t.co/N500zxk5yz
#VibeCoding#TokenMaxxing
Do not reward your brain for a "jugaad" you came up with.
It is good that you came up with a witty but dirty solution, but do not make it a habit or give it positive reinforcement. What you repeatedly reward becomes your default way of thinking.
Over time, what matters more is that you can reason from first principles, spot nuances, and hold a high bar before reaching for shortcuts. A way I would put it is: a shortcut is useful when it is built on understanding, not when it replaces it.
Hope this helps.
@shyamalanadkat@OpenAI I moved 5 years back , right after postgrad .
Currently working in the AI application layer with a startup .
Unable to DM as its limited verified members . Love to connect via any alternate way .
1) The house I live costs less than 5% of my net-worth.
2) My #1 conviction stock is Meta. I've invested less than 7% of my net-worth on it.
3) South Goa is my #1 Real Estate play, I do not have more than 15% of my net-worth exposure on it.
Concentration is for insiders. If you got no political connects, your only friend is diversification.
We're rolling out Brain: a self-improving context-graph of all your sessions, connectors, and files.
Brain updates itself overnight with fresh context proactively, and feeds itself to every task on Computer, allowing Computer to be stateful and self-improving.
Available to all Perplexity Max subscribers.
This is a super exciting release - Claude Fable 5 is the same underlying model as Mythos but with added safeguards. The benchmarks are great and it's SOTA on everything by a margin but I'll add that *qualitatively* also, this is a major-version-bump-deserving step change forward (imo of the same order as Claude 4.5 was in November), peaking especially for long problem-solving sessions on very difficult problems. You can give it a lot more ambitious tasks than what you're used to, the model "gets it" and it will just go, and it's never felt this tempting to stop looking at the code at all (but don't do this in prod!). The model still has quirks that people will run into and the safeguards are configured to be a little too trigger happy for launch, which can hopefully be tuned over time.
I feel a lot of things changing as working software increasingly comes out on a tap. The Jevon's paradox kicks in and I feel my own demand for software growing substantially. You can ask for anything - explainers, visualizers, dashboards, bespoke single-use apps (e.g. a full wandb that is hyper-specific just for your project), you can 10X your test suite, auto-optimize code, run giant research projects with custom HTML for the results, anything! "Free your mind" (Matrix ref). Really looking forward to all the things people build!
My friend went to an indie hacker meetup this week and said this:
"i went to indie hacker meetup
so what’s really interesting is that almost everyone is super focused on development.
they build these whole spaceships that generate code, review it, make all kinds of reports, analytics, and so on.
one guy built an entire factory: he has a list of ideas, and agents generate the landing page, the saas, the analytics, and pull everything into one dashboard. straight-up sci-fi.
and they focused optimize all of it like crazy.
and you can really see how comfortable that is for them.
but the most interesting part is that almost none of them have money or traffic.
and nobody knows where to get either one.
you often hear something like, yeah, i should probably do on marketing, but first i’ll finish my super system and then i’ll start.
or in best i would need to make agent that will post to instaram automatically
before, the classic programmer would spend a year writing code, tests, preparing for scale in the basement, and not show anything to anyone.
now it’s even worse: the amount of useless aislop nobody needs has grown massively."
Whenever I am having a good year in stock markets, I would take 15-20% profits out.
1) I would go buy something that improves my life.
2) If I am already happy with my current lifestyle. And, don't need to "buy" anything-- I would move it to less riskier assets.
3) This process:
- Keeps the joy of investing alive.
- Gives me opportunity to re-invest at lower rates (if market falls).
- If it does not, cool-- the remainder 80% keeps compounding.
Taking profits out is an important part of investing.
Very few folks, actually talk about it.
Our traditional approach to technical complexity is to "divide and conquer" - break the problem into small, low complex chunks and solve them and then put the pieces together. This works well for many problems.
There exists a class of problems that are "fractal-like" in complexity and you break the problem down, only to expose another hidden layer of complexity. Highly creative domains have this nature. That is why they are unpredictable.
I hope all of us heed the Prime Minister's appeal.
As a company, we adopted
Work From Office fully in recent months, but we will revisit Work From Home now.
We have adopted natural farming in our farm and we are also actively looking for ways to cut diesel use.
Today we’re launching the OpenAI Deployment Company to help businesses build and deploy AI.
It's majority-owned and controlled by OpenAI. It brings together 19 leading investment firms, consultancies, and system integrators to help organizations deploy frontier AI to production for business impact. https://t.co/GnyjGFaLLA
We are investing in foundational technologies across the board: recently in quantum sensing, advanced materials, and soon metallurgy. I am a big proponent of metallurgy R&D in particular. Without it, we cannot build nail cutters or precision machinery or jet engines.
These are not flashy billion dollar investments to make headlines, they are foundational R&D that cost millions a year, stretched out over many years. The key is to SUSTAIN them for a decade or longer. Scientists and engineers need time and rock solid support.
We also don't aim for prestige, we want to first replicate know-how already there.
We have also been looking to partner with small Japanese companies with critical know-how. I have two fluent Japanese speakers with me now!
Weird how some people always target open-source in AI!
First it was:
“Open-source AI will destroy the world” (spoiler: it didn't and it won't)
Now:
“Open-source is a cybersecurity threat because of AI”
Both narratives are far too simplistic.
The truth is that the exact same risks exist in closed-source systems, often even more so. For example, in practice, APIs can create much bigger data and security vulnerabilities than open systems you can inspect, self-host, and secure yourself.
And as with software more broadly, open-source often ends up more secure because it benefits from far more scrutiny than private internal systems.
The reality is not “open vs closed.”
The reality is that AI is raising cybersecurity stakes across the board, and we need to tackle that seriously together.
Hi @onlywhatsneeded@foodpharmer2 - A new product suggestion : Pls consider launching plant protein bars, as the market is right now focussing only on whey, for which the prices are skyrocketting right now.