
Stars don't stand still in the sky 💫 Chief Vibecoding Officer at @StablewatchHQ & @OseroHQ
Poland
Joined December 2018
- Tweets3.1K
- Following310
- Followers1.8K
- Likes7.3K
Max Long retweeted
NEW on Stablewatch: Non-USD assets.
Track and compare yields beyond the dollar. All in one place.
Max Long retweeted
We’re bringing the Stablewatch Street Workout to Singapore.
Start the day with pull-ups, dips, and good company before Token2049 madness starts.
All fitness levels are welcome.
Sign-up link below.
Max Long retweeted
Always room for non boring animations on my sites XD
went through a ton of portfolios while making mine and found way too many beautiful ones
some of them are genuinely works of art. you can tell how much time and care went into making them.
so i decided to put my favourites in one place
directoryyy.com
Max Long retweeted
Elon Musk with the President of the United States:
Elon’s ‘tism is tisming
Readers added context they thought people might want to know
This photo is altered by AI and not marked as such.
While Elon did this during a lighthearted moment at a Mar-A-Lago dinner last year, he did NOT do this during the State Dinner with President Xi.
This can be proved by the official livestream at timestamp 11:26
youtube.com/watch?v=9cCZhc…
Max Long retweeted
Tokenization Ecosystem Map.
A snapshot of the assets, platforms, and infrastructure shaping tokenized finance in 2026.
Max Long retweeted

Mitchell Hashimoto@mitchellhAug 13
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
I'm so incredibly tired of seeing low-effort AI-designed web pages. I basically bounce off any new product immediately when I see it (never get a chance to judge the product itself). Lots of thin lines, glowy styles, inconsistent fonts, lots of monospace. You know who you are.
Max Long retweeted
Neutrl has temporarily paused minting, redemptions, and other protocol functions following circumstances affecting protocol reserves. These measures have been taken in the interest of our users, after advice from legal counsel, to preserve an orderly process while the impact is assessed.
Users will be provided with a clear and orderly process in due course. Further information on timing, and next steps will be shared as soon as available.
Max Long retweeted
This week someone hit our Stablewatch news channel with 16k bots. The same thing happened to Osero's announcement channel.
No idea what the intent is. Anyone dealt with this before?
Max Long retweeted
We’re announcing our $13.5M Series A led by @Standard_Cap.
AI has taken over engineering and companies are wasting millions. Weave gets you the most out of every dollar spent on tokens.
Have fun watching a man attempt to conquer his fears in the video.
We've raised $1.6M to build Europe's first daily live technology show and we're live right now.
State-of-the-art newsroom near Kings Cross.
First guests being announced shortly.
Coming to you 5 days a week.
What a time to be live.
12-3 GMT.
Max Long retweeted
I think I finally figured out how to use AI at scale
of course, the fact Fable is good is part of it. but I also changed how I work, and it all comes down to one key realization: you don't need to audit the code, but you NEED to audit the *choices* it made. if you just do that, things will work out, and you'll never lose a codebase to chaos. with Fable at least, the following seems to hold:
if I give it a good decision:
Fable implements it PERFECTLY
if I let it decide instead:
Fable may make some bad choices
that's how I see Fable: as a perfect execution machine capable of converting good decisions into good codebases, no matter how large. given a concrete plan, it lands its implementation. but when anything is underspecified, it can, and will, make bad choices. that's what you must audit.
"while working on this, which choices did you make that you're not confident of? list all."
then, you just review that. not the git diff, not 1000's of lines of code. just the choices it made along the way.
below is a fresh example. overnight, I asked Fable to fix an issue related to MatMul parallelizing worse than expected. it tracked the culprit with perfection, and landed a solution that DID work. but the solution was not general. it just doubled a buffer, which coincidently fixed the program at hands, but the underlying issue was still present.
when it completed the job, it declared success. if I just merged it blindly, the issue would still be dormant. that's the main mistake one can do with AI. instead, I asked it to spell out all decisions it made, spotted the bad one, corrected its course, and now the codebase is clean, correct and the issue is gone for good
I really think that if you do that religiously - i.e., NEVER merge without this "which decisions you made?" audit - you can go VERY far without ever reading a single line of code. at least on Bend, this is working incredibly well. despite heavy use of AI to implement an ungodly amount of features I could never dream of, the codebase is still in a superb state, with no signs of degradation
fresh example below ↓
Max Long retweeted
Our Discord server has been compromised.
Please do not click any links or interact with any announcements posted in the server until further notice. Any links or messages currently being shared should be treated as malicious.
This is a Discord platform compromise only. The Extended protocol, trading platform, smart contracts and funds are not affected.
Our team is actively working to regain control of the server. Please follow updates on our official X account.
Thank you for your patience, and please stay safe.
Max Long retweeted
One question. A lot of awkward answers.
We stopped people in Warsaw and asked about their savings.
Watch what happened.
Max Long retweeted
JUST IN: @gauntlet_xyz raises $125 million from Japanese financial giant SBI Holdings.




























