Full-stack engineer building https://xitter.cf/t.co/Nsd77USNDo Substack publication: https://xitter.cf/t.co/GTqCQdQBYw Drop a follow

/etc/init.d
Joined March 2022
heypascal.me is LIVE. My home on the internet. Months of building, rewriting, second-guessing every pixel. Full-stack engineer, founder, writer — one site, whole picture. If you've got something to build — an API, an AWS setup, a document workflow — the work-with-me section has real prices and a direct way to start. No pitch deck required. Here's what I built and what it cost me 🧵
1
1
3
414
Pascal retweeted
We’re literally in the early stages of a paradigm shift
Excited to share Genie 4 today our most realistic and interactive world model: - steer dynamic environments in real time, shaping events, camera angles, and actions - generate native audio matched to the world, from realistic background sounds to characters who can converse in real time! - simulate photorealistic scenes and real-world physics - create more coherent multi-step events through reasoning from Gemini We've started to roll out as a research preview to trusted testers. Coming soon to Google AI Ultra subscribers in Project Genie and early access partners via the Gemini API and AI Studio.
1
11
We’re literally in the early stages of a paradigm shift
Excited to share Genie 4 today our most realistic and interactive world model: - steer dynamic environments in real time, shaping events, camera angles, and actions - generate native audio matched to the world, from realistic background sounds to characters who can converse in real time! - simulate photorealistic scenes and real-world physics - create more coherent multi-step events through reasoning from Gemini We've started to roll out as a research preview to trusted testers. Coming soon to Google AI Ultra subscribers in Project Genie and early access partners via the Gemini API and AI Studio.
1
11
In a monolith, a bug lives in one place. In microservices, one user action can cross 5+ services. Signup: Auth → User → Notification → Email provider. It fails halfway — where do you look?
2
1
36
Without centralised logging and tracing, you open four dashboards and four log formats, and you guess. Each service can honestly say "it worked on my side."
1
21
The fix: one request ID carried across every hop, centralised logs searchable by that ID, and tracing that shows where the chain broke. Centralise the evidence, and the mystery goes away. Next: 7 backend lessons I learned the hard way. Follow along.
12
Never leaving this app 😂😂
Replying to @SenAlexPadilla
Investigate your wiener
16
Flight 15 is about to be The first fully demonstrated reusable rocket 🚀
Full duration 33-engine static fire for the Super Heavy booster preparing for Flight 15
1
1
17
Pls follow me🙏
I’m really grateful for the first 200 persons that followed me; just a normal indie dev trying to grow. Here’s the 200 more 🥂
1
8
Flight 15 is about to be The first fully demonstrated reusable rocket 🚀
Full duration 33-engine static fire for the Super Heavy booster preparing for Flight 15
1
1
17
Pls follow me🙏
I’m really grateful for the first 200 persons that followed me; just a normal indie dev trying to grow. Here’s the 200 more 🥂
1
8
The better pattern: the repository layer. All DB access lives in one place. Controllers ask the repository; they never touch the ORM. Schema knowledge — joins, filters, transaction boundaries — lives in one module per entity.
1
1
27
One mistake I see in backend codebases: ORM queries scattered everywhere. Controllers query the DB. Services query the DB. Helpers query the DB. Change one column and you're grep-ing the whole repo, praying you found every query that touches it.
1
1
29
Anthropic filed to go public. The S-1 is where the takes stop: revenue, compute spend, margins, all public for the first time. For builders, the number to watch is serving cost vs revenue per user. That ratio decides whether models stay premium or become a utility.
1
15
Anthropic filed to go public. The S-1 is the interesting part: the first real numbers on what running the model layer actually costs.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO. Read more: anthropic.com/news/s1-sec Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
1
1
27
Anthropic’s IPO filing reveals just how extraordinary the economics of frontier AI have become. $16.3B in revenue in just six months, yet still investing enormous sums in compute and infrastructure. The real test for public markets won’t just be how fast AI grows, but whether that growth can become sustainable and profitable at scale. We’re entering a fascinating chapter for the AI industry.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO. Read more: anthropic.com/news/s1-sec Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
1
9
Anthropic’s IPO filing reveals just how extraordinary the economics of frontier AI have become. $16.3B in revenue in just six months, yet still investing enormous sums in compute and infrastructure. The real test for public markets won’t just be how fast AI grows, but whether that growth can become sustainable and profitable at scale. We’re entering a fascinating chapter for the AI industry.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO. Read more: anthropic.com/news/s1-sec Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
1
9
Anthropic filed to go public. The S-1 is the interesting part: the first real numbers on what running the model layer actually costs.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO. Read more: anthropic.com/news/s1-sec Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
1
1
27
Anthropic filed to go public. The S-1 is where the takes stop: revenue, compute spend, margins, all public for the first time. For builders, the number to watch is serving cost vs revenue per user. That ratio decides whether models stay premium or become a utility.
1
15
One mistake I see in backend codebases: ORM queries scattered everywhere. Controllers query the DB. Services query the DB. Helpers query the DB. Change one column and you're grep-ing the whole repo, praying you found every query that touches it.
1
1
29
The better pattern: the repository layer. All DB access lives in one place. Controllers ask the repository; they never touch the ORM. Schema knowledge — joins, filters, transaction boundaries — lives in one module per entity.
1
1
27
Three wins: cleaner code, safer schema changes (rename a column in one file, not seventeen), and a clean seam for tests. The rule I keep: no raw ORM calls outside the repository. Break it once and it's no longer a rule. Next: debugging a distributed mystery. Follow along.
19