zhandos mukatayev

[zhandos mukatayev @zhanddos]

Organizations will never claim to use your data to increase profits. It’s always for safety, research, quality assurance, etc. The ultimate incentive remains to kill competition and maximize profits.

[zhandos mukatayev @zhanddos]

With only 2 key differences: 2x the cost and no more zero data retention options available with fable 5

[Theo - t3.gg @theo]

Mythos is the new Sonnet
Opus is the new Haiku

[zhandos mukatayev @zhanddos]

Ever had to prompt a human?😂

[zhandos mukatayev @zhanddos]

@mohamed__315 LOL

[zhandos mukatayev @zhanddos]

Always seek more and ask

[zhandos mukatayev @zhanddos]

Knowing what you don’t know is as powerful as true expertise.
The unknown unknowns? That’s the danger zone.

[zhandos mukatayev @zhanddos]

Serverless inference is one of the two:
1. a weekend prototype
2. an overpriced ripoff.

There is no third option.

[zhandos mukatayev @zhanddos]

Preserve and enrich your physical and mental energy. It takes discipline, clear direction, and health to push through anything.

[Path of Men @PathOfMen_]

During a very dark period, what was the best thing you ever did for your mental health?

[zhandos mukatayev @zhanddos]

@TTrimoreau Best cost to value ratio, speed - composer 2.5
Best at handling complex tasks with heavy cognitive load - opus 4.7
Best at getting things “right” without much explanation - gpt 5.5

[Mitchell Hashimoto @mitchellh]

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).

If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!

I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.

Feeling pretty swell about this mentality with all the supply chain attacks happening.

[zhandos mukatayev @zhanddos]

- Your device has a backdoor. Don't leave secrets in text files

- Your app will get hacked one day. NEVER leave secrets in the source code hard coding NOR baking during build time
Env variables are slept on. Pulling them from a running process is way harder than people think.

- Cloud creds will leak. Forget these: long-lived tokens, permanent admin, or delete permissions.

- API keys are basically public: hard spending caps + instant alerts. Treat every key like it’s half-leaked already.

[zhandos mukatayev @zhanddos]

These simple rules will save a lot of headache

1. Catch crap before it ships: scan your apps for vulnerabilities with Trivy or similar tools
2. NEVER update to the latest version Day 1: (unless it's a security patch): let enthusiasts beta test for you. Wait 2-4 weeks. The real bugs always surface early
3. Golden Rule: Assume everything is already compromised you just don't know it yet

[Theo - t3.gg @theo]

The GitHub hack is really, really bad.

[zhandos mukatayev @zhanddos]

Rubber handles on pull up bars should be banned

[zhandos mukatayev @zhanddos]

Hacks like this are the new norm. Assume the worst. Make it easy to swap secrets. If possible, limit each secret’s privileges to be as narrow as possible and break it down into many. Set caps on spendings. Can’t trust with your sensitive and proprietary stuff to be out there

[GitHub @github]

We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.

[zhandos mukatayev @zhanddos]

Funniest hallucination yet💀🤣 We’re far from getting replaced by AI

Replaces .pop() with popcorn(). Fixes back to .pop()

[Ryo Lu @ryolu_]

overcooking

you've seen this: someone ships a dashboard that shows every number with a sparkline, every action has a confirmation modal, every empty state has an animated illustration and a tagline. individually each decision made sense to someone. together it feels like chaos. nothing is in focus.

that's overcooking. not one bad decision in isolation, but the accumulation of reasonable ones that no one said no to.

AI makes this worse as the cost of adding dropped to near zero. it can build a feature, even a whole new concept in minutes. so people do. and then they do it again. the thing that started with a clear purpose slowly becomes a collection of additions that are each justifiable but collectively incoherent.

the root problem is that most "new ideas" aren't new. they're repackaging of something that already exists at a more fundamental level. a new sticker on an old concept. it feels like progress because something changed, with a new word and skin – but the thinking didn't go deeper, it just duplicated itself into confusion.

the whole has a core. you feel it once you understand the whole system. everything in it are related and balanced. when you overload it, that gravity weakens. not because any one thing is wrong – but because attention is finite and you force it everywhere.

what we need aren't more tools that make more slop. it's seeing through the chaos, and returning to what the thing actually is, and cutting everything that doesn't serve that. that's harder now, not easier. because there's always something else you could add with one more prompt.

[zhandos mukatayev @zhanddos]

Start early

[Sahil Bloom @SahilBloom]

What is the single best health investment you’ve ever made?