Tito Boyet 🇺🇸 retweeted
this meeting could have been an MCP invoked search of our company’s internal knowledge base that aggregates data from virtually every service we use behind a unified retrieval layer and provides a streamlined interface for extracting critical business insights
94
551
6,858
270,197
Tito Boyet 🇺🇸 retweeted
Pretty smart marketing, showing everybody for 2 years what his tweets do to the market and then selling them 😬
🇺🇸 Trump's media company just started selling early access to his own posts
For up to $100,000 a month ($60,000 on a 3-year lock-in) trading firms get Trump's Truth Social posts milliseconds before everyone else, plus 8 other top accounts.
His posts already move markets. Tariff pauses, Fed comments, war updates... all posted there first.
Two former SEC officials say this may violate securities law outright. One trading-firm CEO put it bluntly: if this were any other public company's chief executive, it'd be jail time.
Trump owns roughly 41% of the company selling access to his own words.
Writer: Oliver
2
5
11
1,177
Tito Boyet 🇺🇸 retweeted
It’s so easy:
- rent VPS on hetzner or ovh or whatever
- get Claude to set it up for you, copy your dotfiles, install packages, setup swapfile and zswap etc
- lock it down by blocking all inbound traffic and using tailscale ssh
- use tmux or use the ssh feature of Claude/Codex desktop app if you are allergic to terminal
- use tailscale serve (within tailnet) or cloudflare tunnels (outside world) to expose servers
It’s als cheaper
✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now
All I can say it's just fantastic:
- no need to keep laptop open ever
- no laptop battery drain
- can switch to phone or any other device you like whenever you want to continue (like when you're outside)
- it just keeps going all night while you sleep (esp with /goal)
- you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver)
- it just feels like living in the future
I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out
But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to prod and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too
But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK
If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine
I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first
P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!
90
102
1,991
243,504
Tito Boyet 🇺🇸 retweeted
10 repositorios de GitHub para scrapear todo internet
Guárdalos todos. Cada uno extrae datos limpios de cualquier web. Ese nivel de acceso normalmente exige llamadas de ventas y contratos.
49
965
6,695
471,486
Tito Boyet 🇺🇸 retweeted
my new hobby:
find cracked devs on github and steal their skills
31
139
1,798
187,864
bodila
Community note
The video is a 2024 talk by Horace He at Jane Street as a guest speaker. He is not an employee there and did not land a role using AI for data analysis. The talk is about ML systems and infrastructure.
janestreet.com/tech-talks/bui…
horace.io
3
42
Tito Boyet 🇺🇸 retweeted
The best shorts come always come just after a bunch of smug motherfuckers tell you not to short. 🍸
64
26
446
40,618
Tito Boyet 🇺🇸 retweeted
ANTHROPIC ENGINEER DROPPED A 14-MINUTE GUIDE.
This is the fastest way to understand how real agents are built.
Bookmark this for the weekend.
14 minutes.
Real architecture.
No fluff.
What actually works.
Agents → Structure → Tools → Execution → Systems → Money
ANTHROPIC JUST DROPPED A 33-PAGE GUIDE.
This is the most practical breakdown of Claude Skills I’ve seen.
Bookmark this before you forget.
33 pages.
Persistent instructions.
No repetition.
No re-explaining every time.
Read it today. Link below.
Claude → Skills → Memory → Automation → Systems → Money
21
447
6,594
3,629,910
Tito Boyet 🇺🇸 retweeted
🚨 BREAKING: AI can now build trading algorithms like Goldman Sachs' algorithmic trading desk (for free).
Here are 15 insane Claude prompts that replace $500K/year quant strats (Save for later)
55
371
2,934
429,097
Tito Boyet 🇺🇸 retweeted
The 2nd amendment is not for hunting, it is not for self protection
It is there to ensure that free people can defend themselves if god forbid government became tyrannical and turned against its citizens
1,860
13,790
51,102
Tito Boyet 🇺🇸 retweeted
For the retards who still think this is a left/right issue:
You can be against illegal immigration and against government tyranny.
You can support deportation but oppose federal agents killing U.S. citizens.
3,720
6,236
63,093
2,160,091
Tito Boyet 🇺🇸 retweeted
As a Backend Engineer in 2026 aiming for Staff, please learn:
1. One language deeply (Go/Rust/Java)
Not “I can write APIs”, but runtime model, memory, concurrency, profiling, GC behavior (if any), and how to read stack traces like a native.
2. Data modeling and storage fundamentals
Relational modeling, constraints, isolation levels, indexes, query plans, locks, deadlocks, migrations, backup/restore, partitioning. Most “scaling” problems are schema + query shape problems.
3. Distributed systems basics that actually show up in prod
Consistency vs availability, timeouts, retries, idempotency, backpressure, message ordering, leader election, clock skew, eventual consistency, and what happens during partial failures.
4. API design and contracts
Versioning, pagination, filtering, error models, idempotency keys, rate limits, backwards compatibility, and how to avoid breaking mobile clients for months.
5. Performance and capacity engineering
Latency budgets (p50/p95/p99), tail latency causes, load testing, queueing theory intuition, connection pools, CPU vs IO bound, and capacity planning with real numbers.
6. Reliability engineering
SLOs/SLIs, incident response, postmortems, alerting that does not spam, error budgets, graceful degradation, feature flags, circuit breakers, bulkheads.
7. Observability like a pro
Structured logs, metrics, tracing, correlation ids, RED/USE metrics, sampling strategies, and how to debug “it is slow sometimes” without just guessing.
8. Security fundamentals
AuthN/AuthZ, least privilege, secrets management, token expiry, OWASP basics, SSRF, injection, secure defaults, audit logs, threat modeling for your own services.
9. Messaging and async systems
Kafka/Rabbit/SQS semantics, at-least-once vs exactly-once (and why “exactly once” is mostly a marketing term), consumer groups, retries, DLQs, replay, dedupe.
10. Caching with correctness
Cache invalidation strategies, TTLs, stampede protection, read-through/write-through, negative caching, and when caching makes bugs harder than latency.
11. Infrastructure literacy
Linux basics, networking (DNS, TCP, TLS), containers, k8s concepts, autoscaling, deployment strategies (blue/green, canary), and what your cloud bill is really paying for.
12. System design, but with tradeoffs
Designing is picking pain. Learn to write down constraints, failure modes, data growth, and operational cost. Staff is judged on tradeoffs, not diagrams.
13. Codebase leadership
Design docs, RFCs, review quality, mentorship, aligning teams, reducing complexity, owning a subsystem end-to-end, making boring systems that do not wake people at 2am.
14. Pick ONE domain to go deep
Payments, search, streaming, identity, infra, data platform, etc. Staff engineers are “the person for a hard area”, not generic API writers.
Stop hopping stacks every month. Pick a lane, build proof of reliability, and become the person people call when prod is on fire. That is Staff.
62
496
4,845
551,661
Tito Boyet 🇺🇸 retweeted
2026 🥹🥹
🚨 TL;DR — $TRU just nuked -100% on DEX 🚨
What happened?
• Truebit Protocol ($TRU) appears to have been exploited for ~$26.5M
• Attacker called a function literally named Attack on Truebit’s Purchase contract
• Drained 8,500 ETH ($26.5M) in a single move
• ~50% of funds already routed to Tornado Cash
This wasn’t slow.
This wasn’t subtle.
This was instant.
📉 Result: $TRU → -100% on DEX
Attacker address:
0x6C8EC8f14bE7C01672d31CFa5f2CEfeAB2562b50
@Truebitprotocol which way now ?
Another reminder that:
• Smart contract bugs don’t forgive
• “Battle-tested” means nothing without continuous audits
• On-chain exploits move faster than announcements
Stay safe out there.
1
2
5
2,349
Tito Boyet 🇺🇸 retweeted
🚨ALERT🚨Hey @Truebitprotocol Our system has detected suspicious transaction with estimated loss of 26M!
An address got around 8,535 $ETH from "Truebit Protocol: Purchase"
More information will follow!
If you wish to safeguard yourself against such incident, please contact us to arrange a demo of our solution at calendly.com/d/cqjd-77h-r6x/…
#CyversAlert
1
11
39
7,431
