truely

Developer(Solidity/JS/Python)

[truely @truelyeth]

@ShtenzY @Tomeratt

[Elon Musk @elonmusk]

We will make the new 𝕏 algorithm, including all code used to determine what organic and advertising posts are recommended to users, open source in 7 days.

This will be repeated every 4 weeks, with comprehensive developer notes, to help you understand what changed.

[truely @truelyeth]

@PapiTrumpo @Tomeratt

[Nick Khami @skeptrune]

software developers merging code written by Opus 4.5

[truely @truelyeth]

@BLUECOW009 I am

[Andrej Karpathy @karpathy]

I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.

[Yam Peleg @Yampeleg]

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it.

I mean, opus built it.
No clue how the code even looks.

The entire thing was vibe coded using my phone.

I wanted to see how far I could push it without touching the computer.

Everything via WhatsApp.
Build what I need on the fly.

So the resulting infrastructure will already be battle tested for software development.

The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection.

If the script is down, I need to get home to start it again to resume the development.

Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me.

I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies.

I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system.

The way this whole thing works:

Claude has its own dedicated phone number that I am paying for.

A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk.

All is registered under my name, this is legit setup with no hacks and tricks.

I’ve set up a WhatsApp “Community” and multiple different groups under it.

Both me and Claude are the admins, so Claude could edit it on my behalf.

Each group is a project I am working on and has its own isolated context.

The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general.

When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal.

Voice notes are seamlessly transcribed with a local Whisper model.

Images are used with multimodal reading in an isolated parallel session.

Multiple groups running in parallel so I can work on all projects at the same time.

No cross-talking, everything has an isolated context and history.

And because it’s local on my own machine:
Everything is REAL.

The browser is REAL.

I am connected as myself on it to all services because I actually use it in real life.

Claude has unlimited internet access, just like humans who use actual browsers.

It utilizes custom-made browser tools that I made to control any browser session it wants.

Depending on the situation, it can either connect to my existing session or create one for its own.

(You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool)

My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable.

This gives Claude full access to my real creds and all the services I actually use.

I’m productive AS HELL with this.
It really feels like a personal assistant.

I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things.

[I try not to do this one a lot lol so far no disasters].

All from my phone.
Super convenient.

This is not a product or an open source project (maybe soon of it will make sense).

This is just an ugly script I hacked the entire thing is ~600 lines.

(ok maybe i did look at the code, but i swear i didn’t edit!)

You can also vibe code this from scratch pretty fast and it will probably even end up better.

This is just a cool thing so I’m sharing.

It is a real speed booster for many things I do on daily basis, mostly boring things.

Forcing my routine into some new “agent platform” just didn’t feel right for me.

WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too.

AGI in my pocket 24/7.

[Tomer Attias تامر عطيه @Tomeratt]

🇪🇺 Europe bleeding talent
🇦🇪🇸🇦🇧🇭GCC is attracting it like a magnet

Why? Simple:

50-60% tax robbery
Woke brainwashing 24/7
Green cults making electricity a luxury
Daily stabbings = "vibrant diversity”

[Noctara @rumilyrics]

I fall in love with souls, not faces.

[Noctara @rumilyrics]

You may not see it yet, but everything is quietly aligning in your favor.

[Noctara @rumilyrics]

We may not understand the wisdom in delays, but God’s timing is always perfect.

[Noctara @rumilyrics]

Your soul already knows that it will all work out.

[Jeson Lee @thejesonlee]

the hardest part about being a male founder..

in my experience is finding a girlfriend / partner that understands the short term gains that we are forgoing and the long-term optimization game that we are playing.

most women expect to have most dates paid for, their vacations covered and their partner to have the time and emotional bandwidth to support them. somebody they see as a reliable provider. this is completely understandable.

but as founders, every dollar saved is additional runway for the company. we budget down to the cent because our life’s work depends on it. every 100-hour work week slightly increases the odds of success. at this stage of life, we’re both cash-poor and time-poor — betting everything on the hope that one day, it all works out. that one day, we’ll be sitting on generational wealth — the kind most men only dream about.

even for women who understand that they might be investing in their man long-term , it’s hard not to compare. their friends are dating guys with high-paying tech jobs, who work from 10 to 3 and can afford to give them a luxury experience now, not later. optimizing for the short term is human nature — it’s hard to fight against.

to all the girlfriends out there dating early-stage founders — you’re the real ones.

and to all my fellow founders: may you find your person while you still have nothing. Because that’s the only time you’ll know she’s with you for who you are, not what you have.

[Linda Chen @linderps]

dating founders is hard. really fking hard.

you come home to a messy apartment, to someone who’s still glued to their laptop. you’re exhausted from your own job, but you pour what’s left of you into his dream. you hold space for their stress, and stay calm when it all feels too heavy. you rejoice in their success, and you support them in their lows. and you hold optimism for them when no one else can.

this is the quiet resilience of a partner.

but for all the sleepless nights, the tears, the chaos, you get a man who is ambitious, magnetic, and genuinely believes he can change the world. and somehow, that makes you believe it too.

and if that's not the sexiest thing in the whole damn world, i don't know what is.

[Garry Tan @garrytan]

You can just do things

[Martian Potato @rad_hardened]

Serious question- What does a software startup spend $300M on?

You aren't building a rocket factory. It can't be that expensive to host a website and employ a dozen engineers and a singular designer.

[tobi lutke @tobi]

This is clearly correct

[Gustavo Aroso @officialneeve]

WOW.
@const_reborn has just sent 2200 $TAO to @Raleigh_CA, one of the OG content producers and believers of #Bittensor, who has never wanted anything in return for his content, after he was scammed yesterday for almost ~300 TAO.

That is FUCKING amazing, well done Jake and OTF.

[Andrew Ng @AndrewYNg]

In the age of AI, large corporations — not just startups — can move fast. I often speak with large companies’ C-suite and Boards about AI strategy and implementation, and would like to share some ideas that are applicable to big companies. One key is to create an environment where small, scrappy teams don’t need permission to innovate. Let me explain.

Large companies are slower than startups for many reasons. But why are even 3-person, scrappy teams within large companies slower than startups of a similar size? One major reason is that large companies have more to lose, and cannot afford for a small team to build and ship a feature that leaks sensitive information, damages the company brand, hurts revenue, invites regulatory scrutiny, or otherwise damages an important part of the business. To prevent these outcomes, I have seen companies require privacy review, marketing review, financial review, legal review, and so on before a team can ship anything. But if engineers need sign-off from 5 vice presidents before they’re even allowed to launch an MVP (minimum viable product) to run an experiment, how can they ever discover what customers want, iterate quickly, or invent any meaningful new product?

Thanks to AI-assisted coding, the world now has a capability to build software prototypes really fast. But many large companies’ processes – designed to protect against legitimate downside risks – make them unable to take advantage of this capability. In contrast, in small startups with no revenue, no customers, and no brand reputation the downside is limited. In fact, going out of business is a very real possibility anyway, so moving fast makes a superior tradeoff to moving slowly to protect against downside risk. In the worst case, it might invent a new way to go out of business, but in a good case, it might become very valuable.

Fortunately, large companies have a way out of this conundrum. They can create a sandbox environment for teams to experiment in a way that strictly limits the downside risk. Then those teams can go much faster and not have to slow down to get anyone’s permission.

The sandbox environment can be a set of written policies, not necessarily a software implementation of a sandbox. For example, it may permit a team to test the nascent product only on employees of the company and perhaps alpha testers who have signed an NDA, and give no access to sensitive information. It may be allowed to launch product experiments only under newly created brands not tied directly to the company. Perhaps it must operate within a pre-allocated budget for compute.

Within this sandbox, there can be broad scope for experimentation, and — importantly — a team is free to experiment without frequently needing to ask for permission, because the downside they can create is limited. Further, when a prototype shows sufficient promise to bring it to scale, the company can then invest in making sure the software is reliable, secure, treats sensitive information appropriately, is consistent with the company’s brand, and so on.

Under this framework, it is easier to build a company culture that encourages learning, building, and experimentation and celebrates even the inevitable failures that now come with modest cost. Dozens or hundreds of prototypes can be built and quickly discarded as part of the price of finding one or two ideas that turn out to be home runs. This also lets teams move quickly as they churn through those dozens of prototypes needed to get to the valuable ones.

I often speak with large companies about AI strategy and implementation. My quick checklist of things to consider is people, process, and platform. This letter has addressed only part of processes, with an emphasis on moving fast. I’m bullish about what both startups and large companies can do with AI, and I will write about the roles of people and platforms in future letters.

[Original text: https://t.co/Jn1QLnrRlI ]