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
2
5
448
Algorithm, I want opportunities like this
Ambassador applications for @spacexsi / @cursor_ai are open Details + apply here: anysphere.typeform.com/space…
3
Wow a new phase in the space frontier is opening up 🔥🚀 @grok explain this patent
BOOM 🚨 @SpaceX has patented a cosmic card dealer that fans out an entire deck of satellites with one slow spin 🃏 A rocket stage punches into orbit with sixty satellites stacked on top like a fresh deck of cards. Now every one of them has to leave, and not one can so much as graze its neighbor on the way out. That exit makes or breaks the whole trip. Packing dozens of satellites onto one rocket splits the cost of the ride, but only if the rocket can set every one of them free cleanly. The classic fix is a dispenser, a dedicated rack that cradles each satellite through liftoff and pushes them out one at a time. It gets the job done, but it’s bulky and heavy, and every pound it adds is a pound of payload the rocket can’t carry. Stacking the satellites right on top of each other ditches the rack but swaps weight for complexity. Fasteners lock each layer to the next, a controller releases them layer by layer, and springs nudge them apart. Those springs have to be tuned so each satellite leaves a touch faster than its neighbor, and getting that right makes the whole setup a headache to install and control. SpaceX scraps the layer-by-layer routine and lets the entire stack go in a single instant. Then the rocket’s own motion hands every satellite a different speed, the exact job those tuned springs used to do. It starts by turning the satellites into their own scaffolding. One version splits sixty flat satellites into two side-by-side piles of thirty, with one pile bumped up by the thickness of a single satellite. The stack climbs like a staircase, and each satellite overlaps its neighbors the way bricks interlock in a wall. Sturdy cylindrical fittings on each satellite’s edges line up one on top of the next, building four columns at evenly spaced points around the stack. The brutal forces of launch pour straight down those columns, so the satellites carry their own weight and there’s no separate frame holding them up. Every joint in those columns is a cone resting in a cup. The cup is just a hair wider than the cone, so the two seat snugly but never jam the way a cork wedges into a bottle. That fit stands up to squeezing, sideways shoves, and bending on the way up, yet it lets go in orbit without any extra force. Slick finishes such as hard-anodized aluminum or a dry lubricant film can help the joints slide apart. A small wave spring, basically a thin ring of rippled metal, may also sit inside each joint to give it a nudge. Four sets of tension rods clamp the whole tower together. Each set runs the full height of the stack alongside one column, hinging at the bottom on the payload adapter, the cone-shaped base that links the stack to the rocket. At the top, each set latches onto a cap called a load head. An air- or fluid-powered piston pulls the rods tight, and they bear down on the column like two hands squeezing a stack of books, locking satellite to satellite and the whole tower to the rocket. Once in orbit, the second stage, the top section of the rocket that carries the stack the whole way up, cuts its engine and starts to twirl. Its thrusters ease it into a slow, steady flat spin around its center of mass, its balance point, like a baton turning in a level circle. At roughly three degrees per second, one full turn takes about two minutes. Before letting go, SpaceX lines up the exits. The stack sits turned about 45 degrees, angling the four rod sets so two will shoot ahead along the orbit and two will drop behind. Without that twist, two sets could drift off sluggishly and tag along with the stage and satellites, risking a collision. Then the rods let go. The tension drains away, the load heads unlatch from the tops of the columns, and the rods swing outward on their hinges like a flower opening until they’re completely clear of the stack. They may even break free of the adapter and sail off on paths of their own. Now the spin takes over. It’s the same physics as a merry-go-round, where the kid on the rim whips around while the kid by the hub barely moves. The satellites at the top of the stack ride farthest from the stage’s center of mass, and speed grows right along with that distance. So the top satellites leave fastest, the ones nearest the rocket drift off slowest, and the tower unzips into a spreading stream without a single tuned spring setting the pace. Where a satellite sits becomes how fast it goes, which can make the whole release cheaper, lighter, and easier than a bank of carefully calibrated springs. Back on that rocket stage, the deck isn’t a deck anymore. Sixty satellites stream away in a long, widening fan, the fastest already pulling ahead and the slowest trailing behind, and not one of them needed a dispenser to send it on its way. The old way needed a heavy machine to deal every card by hand. SpaceX just lets go of the whole deck mid-spin, and physics deals each card its own speed.
1
3
62
1/ I'm building my first mobile app with microservices. Seven backend lessons I'm keeping: 1. Each service owns its own data. 2. Make retries safe, or the retry becomes the bug. 3. Put the rule in the database, not just the app.
3
1
3
26
2/ 4. Auth lives in one place, not copied into every handler. 5. Version your contracts and never break callers silently. 6. Observe before you scale: small deploys, metrics, searchable logs.
1
1
1
18
3/ 7. Ship the smallest backend that works, then harden it. A backend you can change beats a clever one you are afraid to touch. Follow along.
10
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
22
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
22
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
2
41
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
1
24
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
1
19
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
20
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
1
13
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
20
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
1
13
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
10