Mike
@mootoday.com
Building https://pipestack.dev - Distributed workflows at scale.
25 years of helping businesses from 0 to 1. Now building my own product to do it all over again, solo.
Excellent developer experience leads to excellent customer experience.
25 years of helping businesses from 0 to 1. Now building my own product to do it all over again, solo.
Excellent developer experience leads to excellent customer experience.
If you've ever looked at your web app and wondered why the changes you made didn't reflect in the browser*, here's a component for you to add to your @svelte.dev `src/routes/+layout.svelte` file, right at the top :)
* it's because you looked at the production site, FYI 😅
* it's because you looked at the production site, FYI 😅
November 12, 2025 at 2:22 PM
If you've ever looked at your web app and wondered why the changes you made didn't reflect in the browser*, here's a component for you to add to your @svelte.dev `src/routes/+layout.svelte` file, right at the top :)
* it's because you looked at the production site, FYI 😅
* it's because you looked at the production site, FYI 😅
If you use shadcn-svelte.com in your @svelte.dev app, here's a command to update all your components.
npx shadcn-svelte@latest add $(ls -d ./src/lib/components/ui/*/ | xargs -n1 basename)
npx shadcn-svelte@latest add $(ls -d ./src/lib/components/ui/*/ | xargs -n1 basename)
November 6, 2025 at 2:39 PM
If you use shadcn-svelte.com in your @svelte.dev app, here's a command to update all your components.
npx shadcn-svelte@latest add $(ls -d ./src/lib/components/ui/*/ | xargs -n1 basename)
npx shadcn-svelte@latest add $(ls -d ./src/lib/components/ui/*/ | xargs -n1 basename)
Not too shabby given all it had was the project URL.
November 2, 2025 at 6:12 PM
Not too shabby given all it had was the project URL.
November 2, 2025 at 4:26 PM
But wait, it gets better.
Now I can freely rename fields and the SQL query will still work.
Variables > strings :)
Now I can freely rename fields and the SQL query will still work.
Variables > strings :)
October 31, 2025 at 9:01 PM
But wait, it gets better.
Now I can freely rename fields and the SQL query will still work.
Variables > strings :)
Now I can freely rename fields and the SQL query will still work.
Variables > strings :)
In case I haven't shown enough @remult.dev beauty, here's another one.
This field is calculated based on the SQL expression and I can access it anywhere in my code (server and client). I can also use it to find and filter entities.
This field is calculated based on the SQL expression and I can access it anywhere in my code (server and client). I can also use it to find and filter entities.
October 31, 2025 at 6:08 PM
In case I haven't shown enough @remult.dev beauty, here's another one.
This field is calculated based on the SQL expression and I can access it anywhere in my code (server and client). I can also use it to find and filter entities.
This field is calculated based on the SQL expression and I can access it anywhere in my code (server and client). I can also use it to find and filter entities.
TIL (and I can't believe it took me that long!) that @zed.dev has a Helix mode!
Oh... My... Goodness.
`gw` is by far the most efficient way I know to navigate in a file. Not yet supported in Zed, but at least I can now use one set of keybindings when I work in Zed vs Helix in the terminal.
Oh... My... Goodness.
`gw` is by far the most efficient way I know to navigate in a file. Not yet supported in Zed, but at least I can now use one set of keybindings when I work in Zed vs Helix in the terminal.
October 29, 2025 at 11:02 PM
TIL (and I can't believe it took me that long!) that @zed.dev has a Helix mode!
Oh... My... Goodness.
`gw` is by far the most efficient way I know to navigate in a file. Not yet supported in Zed, but at least I can now use one set of keybindings when I work in Zed vs Helix in the terminal.
Oh... My... Goodness.
`gw` is by far the most efficient way I know to navigate in a file. Not yet supported in Zed, but at least I can now use one set of keybindings when I work in Zed vs Helix in the terminal.
Does anyone use OrbStack on Mac and has seen this?
It started to happen about a week ago and now happens once or twice a day.
To fix, a full laptop reboot is required.
It started to happen about a week ago and now happens once or twice a day.
To fix, a full laptop reboot is required.
October 27, 2025 at 1:58 PM
Does anyone use OrbStack on Mac and has seen this?
It started to happen about a week ago and now happens once or twice a day.
To fix, a full laptop reboot is required.
It started to happen about a week ago and now happens once or twice a day.
To fix, a full laptop reboot is required.
I'm all set 👍.
Now more than ever protecting one's online identity is important.
Now more than ever protecting one's online identity is important.
October 25, 2025 at 10:02 PM
I'm all set 👍.
Now more than ever protecting one's online identity is important.
Now more than ever protecting one's online identity is important.
October 25, 2025 at 8:43 PM
For all the prompt enthusiasts out there who want to study this masterpiece, here's the prompt and screenshot I uploaded.
October 23, 2025 at 6:06 AM
For all the prompt enthusiasts out there who want to study this masterpiece, here's the prompt and screenshot I uploaded.
A project I came across just now hits all the buzzwords of 2025 😂.
"Blockchain execution layers for AI dApps"
"Blockchain execution layers for AI dApps"
October 21, 2025 at 10:50 PM
A project I came across just now hits all the buzzwords of 2025 😂.
"Blockchain execution layers for AI dApps"
"Blockchain execution layers for AI dApps"
Click on a node and it opens a settings pane. Each now with its own shadcn-svelte form (which uses Formsnap and Superforms) 💪.
Crazy what's possible with modern technologies.
@svelte.dev
Crazy what's possible with modern technologies.
@svelte.dev
October 18, 2025 at 9:27 PM
Click on a node and it opens a settings pane. Each now with its own shadcn-svelte form (which uses Formsnap and Superforms) 💪.
Crazy what's possible with modern technologies.
@svelte.dev
Crazy what's possible with modern technologies.
@svelte.dev
Goodbye self-hosted telemetry, hello hyperdx.io hosted on @clickhouse.com!
A customer asked if it was possible to connect to the telemetry data programmatically. Securing all that didn't feel like something I wanted to do.
Now, I can give them access to ClickHouse, done.
A customer asked if it was possible to connect to the telemetry data programmatically. Securing all that didn't feel like something I wanted to do.
Now, I can give them access to ClickHouse, done.
October 15, 2025 at 10:53 PM
Goodbye self-hosted telemetry, hello hyperdx.io hosted on @clickhouse.com!
A customer asked if it was possible to connect to the telemetry data programmatically. Securing all that didn't feel like something I wanted to do.
Now, I can give them access to ClickHouse, done.
A customer asked if it was possible to connect to the telemetry data programmatically. Securing all that didn't feel like something I wanted to do.
Now, I can give them access to ClickHouse, done.
Watch out, before you know it you go from one service to running your entire platform on Railway 😅.
October 13, 2025 at 1:02 PM
Watch out, before you know it you go from one service to running your entire platform on Railway 😅.
I'm slowly but surely getting back to more regular @pipestack.dev development.
With NATS security all buttoned up (that was a big one!), it's time to spend this week adding new node types.
To start, I refactored the code so all it takes is a new directory with a few files for each node type.
👇
With NATS security all buttoned up (that was a big one!), it's time to spend this week adding new node types.
To start, I refactored the code so all it takes is a new directory with a few files for each node type.
👇
October 8, 2025 at 5:07 AM
I'm slowly but surely getting back to more regular @pipestack.dev development.
With NATS security all buttoned up (that was a big one!), it's time to spend this week adding new node types.
To start, I refactored the code so all it takes is a new directory with a few files for each node type.
👇
With NATS security all buttoned up (that was a big one!), it's time to spend this week adding new node types.
To start, I refactored the code so all it takes is a new directory with a few files for each node type.
👇
I read the docs. I like what I saw.
3 minutes 33 seconds later, I have Omarchy.
3 minutes 33 seconds later, I have Omarchy.
September 25, 2025 at 5:18 AM
I read the docs. I like what I saw.
3 minutes 33 seconds later, I have Omarchy.
3 minutes 33 seconds later, I have Omarchy.
Hey, at least you get the extra chocolate on top :)!
Here, all you get is the very end of the ice cream cone 😭
Here, all you get is the very end of the ice cream cone 😭
August 30, 2025 at 9:59 PM
Hey, at least you get the extra chocolate on top :)!
Here, all you get is the very end of the ice cream cone 😭
Here, all you get is the very end of the ice cream cone 😭
When seconds aren't granular enough to measure your platform latency, you know you're onto something 🚀.
~45 nanoseconds is the baseline to execute a pipeline with one Wasm Component that converts a string to upper case.
From `curl ...` to receiving the data in the webhook.
~45 nanoseconds is the baseline to execute a pipeline with one Wasm Component that converts a string to upper case.
From `curl ...` to receiving the data in the webhook.
August 28, 2025 at 2:42 PM
When seconds aren't granular enough to measure your platform latency, you know you're onto something 🚀.
~45 nanoseconds is the baseline to execute a pipeline with one Wasm Component that converts a string to upper case.
From `curl ...` to receiving the data in the webhook.
~45 nanoseconds is the baseline to execute a pipeline with one Wasm Component that converts a string to upper case.
From `curl ...` to receiving the data in the webhook.
There we go, the LLM-generated code is gone.
It's 30% more code than the single file written by the LLM, but now it's maintainable and easy to understand where to find what.
Not to mention that extending it with additional nodes and providers is dead simple.
It's 30% more code than the single file written by the LLM, but now it's maintainable and easy to understand where to find what.
Not to mention that extending it with additional nodes and providers is dead simple.
August 13, 2025 at 10:01 PM
There we go, the LLM-generated code is gone.
It's 30% more code than the single file written by the LLM, but now it's maintainable and easy to understand where to find what.
Not to mention that extending it with additional nodes and providers is dead simple.
It's 30% more code than the single file written by the LLM, but now it's maintainable and easy to understand where to find what.
Not to mention that extending it with additional nodes and providers is dead simple.
Them, "I need my pipeline to make a HTTP request to my API."
Me, "Sure thing, consider it done."
Also me... HTTP method, Content-Type, headers (add/remove), authentication (api key, bearer token, basic auth), timeout.
Me, "Sure thing, consider it done."
Also me... HTTP method, Content-Type, headers (add/remove), authentication (api key, bearer token, basic auth), timeout.
July 30, 2025 at 6:21 PM
Them, "I need my pipeline to make a HTTP request to my API."
Me, "Sure thing, consider it done."
Also me... HTTP method, Content-Type, headers (add/remove), authentication (api key, bearer token, basic auth), timeout.
Me, "Sure thing, consider it done."
Also me... HTTP method, Content-Type, headers (add/remove), authentication (api key, bearer token, basic auth), timeout.
The folks over at blacksmith.sh aren't joking when they say GitHub Actions run faster with them than on GitHub.
Left: GitHub
Right: Blacksmith
Left: GitHub
Right: Blacksmith
July 18, 2025 at 9:00 PM
The folks over at blacksmith.sh aren't joking when they say GitHub Actions run faster with them than on GitHub.
Left: GitHub
Right: Blacksmith
Left: GitHub
Right: Blacksmith
JSON schema for yaml files 🥰
I don't know which editors support it, but it works great in @zed.dev!
# yaml-language-server: $schema=./my-schema.json
I don't know which editors support it, but it works great in @zed.dev!
# yaml-language-server: $schema=./my-schema.json
May 31, 2025 at 6:13 PM
JSON schema for yaml files 🥰
I don't know which editors support it, but it works great in @zed.dev!
# yaml-language-server: $schema=./my-schema.json
I don't know which editors support it, but it works great in @zed.dev!
# yaml-language-server: $schema=./my-schema.json