Blastin (@blastindev) header
Blastin (@blastindev) profile picture

Software builders

Brisbane, Queensland
Joined November 2025
Photo by Blastin (@blastindev)
Timesheets suck! As a developer, are you tired of doing admin work? Check out #clocktopus. It automates your timesheets from your git commits. #Timesheets #SoftwareDevelopment #DevTools
2
1
1
1
63
Blastin retweeted
im gonna crash out all the replies here seem to think that the React2Shell vuln was because of mixing client and server code emergency video explaining the hack, how RSC works, and how other frameworks like Tanstack start and sveltekit differ youtube.com/watch?v=kmlMNtjF…
At the risk of sticking my neck out during a bad time: I’m sick of seeing this photo This is 100% server code, this isn’t a client side component that sends SQL to a server. You can’t add click handlers, state or hooks. The code renders on the server an wires up a form action just like you’d do with PHP
16
59
8
643
180,046
This is not React2shell, this is something else. Stay alert.
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
30
Very controversial post, but food for thought. The last architectures we designed were monolithic web applications with background services running somewhere else, sharing the same logic as the webapp and always built and deployed together, avoiding compatibility issues.
Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.
26
There is some misunderstanding in the community what open source is. The main ones are: 1st. Open source is not free software 2nd. Open source contributors aren't your employees
If you make open source software, you are the bearer and bringer of gifts. Don't let anyone tell you how to define "open" or "source". Just pick a license, stick to the terms, and tell people they can accept the code with gratitude or they can fuck right off.
17
ISMS vulnerability review is coming earlier for every react shop out there. If you are using react server components, upgrade.
There is critical vulnerability in React Server Components disclosed as CVE-2025-55182 that impacts React 19 and frameworks that use it. A fix has been published in React versions 19.0.1, 19.1.2, and 19.2.1. We recommend upgrading immediately. react.dev/blog/2025/12/03/cr…
17
Runway gets to the next level of video generation
Introducing our new frontier video model, Runway Gen-4.5. Previously known as Whisper Thunder (aka) David. Gen-4.5 is state-of-the-art and sets a new standard for video generation motion quality, prompt adherence and visual fidelity. Learn more below.
12
Javascript that we S2 so much
Thankful for 𝙽𝚊𝙽 !== 𝙽𝚊𝙽, [] == ![], “” == 0 and “” !== 0, “𝟻” - 𝟹 == 𝟸 and “𝟻” + 𝟹 == “𝟻𝟹”, 𝚝𝚢𝚙𝚎𝚘𝚏 𝚗𝚞𝚕𝚕 == “𝚘𝚋𝚓𝚎𝚌𝚝”, and 𝟶.𝟣 + 𝟶.𝟤 !== 𝟶.𝟥.
1
Our team loves Omarchy, it's goddamn good. If you're a dev, you'll likely use most of the stuff installed without much extra config.
Omarchy does not contain one gram of bloat. I use everything we install by default. And it's incredible how light that package is: Just ~6GB for a complete system with all the apps, styling, and configuration needed to start doing professional work 🤩
2
32
2,212
Let's get started, no docu needed.
23