Panta
@pantas.net
Amateur developer, professional contrarian.
I post whatever comes to mind, kind of just what I'm thinking about at the moment. Tends to break down ~ 50% tech, 50% whatever. @thepanta82 at twitter.
https://pantas.net
I post whatever comes to mind, kind of just what I'm thinking about at the moment. Tends to break down ~ 50% tech, 50% whatever. @thepanta82 at twitter.
https://pantas.net
Last time I picked DB tech, I opted for doing raw SQL over query building.
Reason: experience from a prev project, where converting from SQL to a knex command chain was super annoying.
If I was picking today, I'd 100% go for a query builder. LLM solves the conversion now.
Reason: experience from a prev project, where converting from SQL to a knex command chain was super annoying.
If I was picking today, I'd 100% go for a query builder. LLM solves the conversion now.
April 17, 2025 at 8:10 PM
Last time I picked DB tech, I opted for doing raw SQL over query building.
Reason: experience from a prev project, where converting from SQL to a knex command chain was super annoying.
If I was picking today, I'd 100% go for a query builder. LLM solves the conversion now.
Reason: experience from a prev project, where converting from SQL to a knex command chain was super annoying.
If I was picking today, I'd 100% go for a query builder. LLM solves the conversion now.
Tech influencers used to be upstream in the dev FOMO pipeline. "Here's a new lib all the cool kids are using, but you can't because of your trash legacy project."
But since AI tools aren't tied to a codebase, we're now all following along and FOMO-ing at the same time. Hmm.
But since AI tools aren't tied to a codebase, we're now all following along and FOMO-ing at the same time. Hmm.
April 12, 2025 at 12:19 PM
Tech influencers used to be upstream in the dev FOMO pipeline. "Here's a new lib all the cool kids are using, but you can't because of your trash legacy project."
But since AI tools aren't tied to a codebase, we're now all following along and FOMO-ing at the same time. Hmm.
But since AI tools aren't tied to a codebase, we're now all following along and FOMO-ing at the same time. Hmm.
I managed to setup zero downtime deploys WITHOUT clustering, staggered migrations, or blue/green deploys.
Frankly, it was way more DIY than I thought it would be. Reverse proxies should just come with this stuff built in.
Frankly, it was way more DIY than I thought it would be. Reverse proxies should just come with this stuff built in.
March 9, 2025 at 8:39 PM
I managed to setup zero downtime deploys WITHOUT clustering, staggered migrations, or blue/green deploys.
Frankly, it was way more DIY than I thought it would be. Reverse proxies should just come with this stuff built in.
Frankly, it was way more DIY than I thought it would be. Reverse proxies should just come with this stuff built in.
After getting used to typescript's various forms of template strings and unions, it's hard to go back to only having ordinary opaque strings in other languages.
January 7, 2025 at 7:01 AM
After getting used to typescript's various forms of template strings and unions, it's hard to go back to only having ordinary opaque strings in other languages.
Most remotes works like UDP rather than TCP, and it's kind of annoying.
January 4, 2025 at 9:11 AM
Most remotes works like UDP rather than TCP, and it's kind of annoying.
Factory functions > constructors in js.
The reason: they can be async.
With constructors, you often end up in an awkward state, where the class exists but isn't valid to use yet.
Sometimes necessary, but still annoying.
The reason: they can be async.
With constructors, you often end up in an awkward state, where the class exists but isn't valid to use yet.
Sometimes necessary, but still annoying.
January 4, 2025 at 9:10 AM
Factory functions > constructors in js.
The reason: they can be async.
With constructors, you often end up in an awkward state, where the class exists but isn't valid to use yet.
Sometimes necessary, but still annoying.
The reason: they can be async.
With constructors, you often end up in an awkward state, where the class exists but isn't valid to use yet.
Sometimes necessary, but still annoying.
When I first start a cursor project vs when it matures a bit.
January 3, 2025 at 10:13 AM
When I first start a cursor project vs when it matures a bit.
AI can generate any image, except all the ones I need.
AI can write any text, except any I'd want to publish.
AI can code any program, except the ones that matter.
AI can write any text, except any I'd want to publish.
AI can code any program, except the ones that matter.
January 3, 2025 at 9:48 AM
AI can generate any image, except all the ones I need.
AI can write any text, except any I'd want to publish.
AI can code any program, except the ones that matter.
AI can write any text, except any I'd want to publish.
AI can code any program, except the ones that matter.
Oh God, it escaped control.
The jihad has began.
The jihad has began.
January 2, 2025 at 1:16 PM
Oh God, it escaped control.
The jihad has began.
The jihad has began.
This app is the worst. Don't use it.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
January 2, 2025 at 11:55 AM
This app is the worst. Don't use it.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
The reason: pg collation is subtly different on mac vs linux, where your actual stuff will be running.
Run db in docker or remotely instead.
Today: Working on Mac is both satisfying (hardware) and infuriating (macOS).
15 years ago: Working on Mac is both satisfying (OSX) and infuriating (hardware).
15 years ago: Working on Mac is both satisfying (OSX) and infuriating (hardware).
December 30, 2024 at 10:51 AM
Today: Working on Mac is both satisfying (hardware) and infuriating (macOS).
15 years ago: Working on Mac is both satisfying (OSX) and infuriating (hardware).
15 years ago: Working on Mac is both satisfying (OSX) and infuriating (hardware).
Reposted by Panta
1 like = 1 take
December 24, 2024 at 2:08 AM
1 like = 1 take
Wild how the internet turned out to be just a temporary caching layer for the internet archive.
December 24, 2024 at 10:15 PM
Wild how the internet turned out to be just a temporary caching layer for the internet archive.
I used to hate bash. Always kept an eye out for a more sane shell environment.
I no longer care. GPT writes that slop for me now. Its obscure syntax no longer hurts.
AI will enshrine bad languages forever. We will never get rid of them.
But maybe that's OK.
I no longer care. GPT writes that slop for me now. Its obscure syntax no longer hurts.
AI will enshrine bad languages forever. We will never get rid of them.
But maybe that's OK.
December 24, 2024 at 11:00 AM
I used to hate bash. Always kept an eye out for a more sane shell environment.
I no longer care. GPT writes that slop for me now. Its obscure syntax no longer hurts.
AI will enshrine bad languages forever. We will never get rid of them.
But maybe that's OK.
I no longer care. GPT writes that slop for me now. Its obscure syntax no longer hurts.
AI will enshrine bad languages forever. We will never get rid of them.
But maybe that's OK.
"A meeting can completely kill my flow"
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
December 23, 2024 at 11:48 AM
"A meeting can completely kill my flow"
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
ANY context switching can kill the flow. Even between projects, or different types of work.
It's just that most corporate devs only do one type of technical work, so all their experience with flow interruptions is centered on meetings.
CSS tip: if you can't get a smoothly looping animation (eg. due to quirky way percentages work in different contexts), just increase the duration.
Your visitors will probably never notice it glitch out once every 10 minutes.
Your visitors will probably never notice it glitch out once every 10 minutes.
December 23, 2024 at 10:55 AM
CSS tip: if you can't get a smoothly looping animation (eg. due to quirky way percentages work in different contexts), just increase the duration.
Your visitors will probably never notice it glitch out once every 10 minutes.
Your visitors will probably never notice it glitch out once every 10 minutes.
Thank you tailwind, for no longer having to name things.
December 23, 2024 at 9:44 AM
Thank you tailwind, for no longer having to name things.
This is how Butlerian Jihad begins
December 22, 2024 at 7:48 PM
This is how Butlerian Jihad begins
Best UI-s are deeply hardcoded. Strings, images, colors - all directly produced and manipulated by your own code.
The moment you start extracting "content" into resources, CMS-s, translation files etc, the end product starts to suffer.
(you gain other benefits, though)
The moment you start extracting "content" into resources, CMS-s, translation files etc, the end product starts to suffer.
(you gain other benefits, though)
December 19, 2024 at 9:49 PM
Best UI-s are deeply hardcoded. Strings, images, colors - all directly produced and manipulated by your own code.
The moment you start extracting "content" into resources, CMS-s, translation files etc, the end product starts to suffer.
(you gain other benefits, though)
The moment you start extracting "content" into resources, CMS-s, translation files etc, the end product starts to suffer.
(you gain other benefits, though)
We've adopted anarcho-tyranny for privacy.
People who can harm you get all your private data, and people who can help you get none.
People who can harm you get all your private data, and people who can help you get none.
December 19, 2024 at 10:43 AM
We've adopted anarcho-tyranny for privacy.
People who can harm you get all your private data, and people who can help you get none.
People who can harm you get all your private data, and people who can help you get none.
Time for the monthly Apple humiliation ritual
December 18, 2024 at 8:21 AM
Time for the monthly Apple humiliation ritual
Chrome dev tools is probably the best suite of development and debugging tools in the world, across stacks.
I am suspicious of any framework or coding approach that makes it less useful.
I'm specifically thinking of:
- tailwind
- binary RPC protocols
- RSC
I am suspicious of any framework or coding approach that makes it less useful.
I'm specifically thinking of:
- tailwind
- binary RPC protocols
- RSC
December 18, 2024 at 8:07 AM
Chrome dev tools is probably the best suite of development and debugging tools in the world, across stacks.
I am suspicious of any framework or coding approach that makes it less useful.
I'm specifically thinking of:
- tailwind
- binary RPC protocols
- RSC
I am suspicious of any framework or coding approach that makes it less useful.
I'm specifically thinking of:
- tailwind
- binary RPC protocols
- RSC
Common senior dev mistake: just because something is easy, doesn't mean it will be quick.
December 17, 2024 at 7:21 PM
Common senior dev mistake: just because something is easy, doesn't mean it will be quick.
PostgreSQL devs (smart): "We must make sure only superusers can create extensions, because extensions might allow arbitrary code execution."
PostgreSQL users (dumb): "Oh... I guess I'll just use a superuser for everything."
Safety FTW
PostgreSQL users (dumb): "Oh... I guess I'll just use a superuser for everything."
Safety FTW
December 13, 2024 at 9:57 PM
PostgreSQL devs (smart): "We must make sure only superusers can create extensions, because extensions might allow arbitrary code execution."
PostgreSQL users (dumb): "Oh... I guess I'll just use a superuser for everything."
Safety FTW
PostgreSQL users (dumb): "Oh... I guess I'll just use a superuser for everything."
Safety FTW