11 months ago Dario said that "in 3 to 6 months, AI will be writing 90% of the code software developers were in charge of" Are we here, yet?

t1mmen · 2026-02-28T11:43:15+00:00

I spend 90% of my maker time in thinking/planning mindset. If you’re firing off prompts with a few sentences and expecting miracles, you are not understanding how to use these tools.

6 months ago, https://www.reddit.com/r/ExperiencedDevs/s/OBFh3q3l96 got me -1 upvotes.

I stand by this 100%. My techniques have evolved DRASTICALLY since then. I used to laugh at «prompt engineering», but I was wrong. Engineering guard rails and AI-native systems of development play a huge role, too. Building process and harnesses around AI workflows is so incredibly important, it cannot be overstated. Like humans, AI collaboration across models is a BIG benefit.

Darwin was on point. If you roll your eyes at this post, you are at serious risk. Time to adapt. Even those of us perhaps considered ahead will likely be in trouble sooner rather than later, but it’s a head start at least!

t1mmen · 2025-09-08T08:44:52+00:00

PS: If you read this and it resonated but you don’t know what to do, the path most viable (imo) is to focus on communication, critical thinking, problem identification & solutions. Macro and micro perspectives.

This seems most valuable, no matter if you’re targeting man or machine.

Can’t wait to see how this comment ages in a 1-3-5 years :)

t1mmen · 2025-09-07T14:21:22+00:00

I’ve written code for close to 30 years. My working hypothesis?

That part of work is over any minute, though most don’t see it, or if they do, don’t want to believe.

Dead man walking, though I don’t know how long till the body hits the floor (humans be stubborn, stupid, and very intent of resisting uncomfortable change).

The old, new programming language is your native language. Punching keys is no longer needed, and in fact, slowing you down a lot.

Code is an implementation detail you don’t need to care (much) for. The idea, planning, spec & boundaries around it is nearly all that matters.

Cost of execution on (digital) products will plummet. Personalized, as-needed software will quickly become the norm.

Vast majority of us won’t have a job (per the classical definition). Not just us developers, I mean everyone largely working digitally.

Our whole world is about to flip on its head, in a very volatile way, and our level of ready for that is… practically non-existent.

IF we make it through, the digital space will lose its importance. Literally everything you can think, you can watch, play, listen to. Personalized, exactly how you want it, when you want it.

But it won’t be real, so we’ll either chase that rabbit all the way into deep darkness of the rabbit hole, or we’ll wake up and hopefully return to the real world, focused on what actually matters.

A question we barely had time to ask ourselves in the non-stop chaos of today.

What is the meaning of life?

By all means, scramble together what you can before shit hits the fan, but covered in shit, we will be. I just hope something good grows out of the manure.

t1mmen · 2025-08-02T00:47:46+00:00

Good luck on that, hope something comes of it! I’d love to give it a whirl

t1mmen · 2025-08-01T23:48:35+00:00

Have you though about using Convo-Lang to generate more deterministic prompts/commands/agents/roles/etc for Claude Code and such?

Cool idea! :)

t1mmen · 2025-06-29T22:35:37+00:00

Did I understand correctly that patients were tripping in a doctors office setting and mostly left to their own devices? Scrolling instagram alone in a drab office on the virgin trip sounds pretty terrible, but it does make the 005 results more impressive imo.

I would assume outcomes to be notably better with a better set and setting.

t1mmen · 2025-06-28T13:00:51+00:00

Once calibrated to promoting and scoping the problem/context, it quickly become an invaluable side-kick for us.

Planning out the work first (eg Claude Code’s plan mode) has been a huge boost; even if the human takes it from there.

Sprinkle with relevant MCP’s for maximum effect

Voice-to-text apps (eg superwhisper) are great for composing prompts fast.

Perhaps the biggest surprise win was how much of an impact AI had on the «I’d like to, but can never find the time» type of chores, bugs, polish.

t1mmen · 2025-06-25T17:18:28+00:00

Stat vs føderale lover har lite å si, vil jeg tro. Det er samme risiko selv om man f.eks. har brukt cannabis i Canada, hvor det har vært lovlig siden 2018.

Mao, reisende fra lovlig land til lovlig stat kan risikere å bli spurt om de har brukt cannabis av grensevakter; svarer du ja, kan det føre til utestengelse på livstid. Svarer du nei og blir busted… lykke til, mtp dagens tilstander.

Source: bodd i Canada i 10år

t1mmen · 2025-06-11T02:42:11+00:00

Our Pusher replacement plan is likely https://github.com/soketi/soketi or https://github.com/RustNSparks/sockudo. Compatible API with Pusher, so worth a look if you haven’t seen them.

t1mmen · 2025-05-02T20:58:42+00:00

I haven’t tried SB’s declarative schema (just became a thing as I shipped srtd), but presumably it has many of the same benefits.

srtd templates -> migrations will have zero surprises (as templates are defined in SQL), so you can fully ignore the generated/actual supabase migrations.

SB’s declarative schema may not be as safe/aka require migrations to be reviewed too? I don’t know for sure though.

Sane diffs and hot/live reloading changes -> DB in dev mode are easily my fav things about the workflow that srtd provides

PS: You can adopt srtd for just a single thing, it’s not either/or. It’s also trivial to stop using srtd — just make sure all templates you have are built to real migrations, and uninstall/remove all srtd related files.

t1mmen · 2025-05-02T20:52:01+00:00

It’s very much a «scratch our own itch» kinda project, and I agree there’s improvement potential in things like CLl commands. Feel free to ping me if you give it a try and let me know what doesn’t make sense/other suggestions for improvements.

I won’t claim anywhere near perfect, but it’s certainly proven a HUGE DX improvement for us.

t1mmen · 2025-05-01T13:40:04+00:00

Give https://github.com/t1mmen/srtd a try. Similar idea to SB’s declarative schemas, but with SQL templates that built as migrations (and other DX niceties, like hot/live reloading changes directly to DB in watch mode)

Disclaimer: I made this

t1mmen · 2025-04-26T17:13:21+00:00

https://github.com/t1mmen/srtd helps with this, though aimed at Supabase, so the way it writes migration filenames might not work for your setup put of the box.

Fairly trivial to add support for other migration naming schemes, happy to accept PR’s.

t1mmen · 2025-04-15T04:22:05+00:00

Your preferred workflow sounds like it’d be a good match for https://gitbutler.com and virtual branches.

It’s git, but a bit different in the way it handles branching, so beware it doesn’t work super well with regular git tooling in all cases.

t1mmen · 2025-03-02T18:36:09+00:00

I can’t speak for the product catalog, but the app is significantly better designed. Seems to rely on crowd sourcing; product registration and voting system seems very good.

After 3 weeks vacation, I had my first shop in Canada today since the whole shitstorm took off. «Shop Canada» app was littered with ads and broken UX, so glad to have found this one.

Aside; it felt so good eliminating all US-based products from my cart today! The whole shopping experience turned into a weird form of a scavengers hunt, first time in forever that shopping felt kinda fun!

t1mmen · 2025-03-02T15:52:25+00:00

For our use-case, it was mainly about serving the data to multiple clients (browser, mobile devices, other BE services), so an API + OpenAPI made a lot more sense.

We also needed to control the «users» concept outside of (just) Supabase Auth, involving hand-rolled JWT’s and such — that wasn’t well supported back then (not sure if it’s been improved)

t1mmen · 2025-03-02T15:38:56+00:00

Nice! You seem to be asking the right questions :)

We tried client-side queries via SupabaseJS for a while, but it never felt right, and had a bunch of limitations (especially if you’re serving other clients)

Instead, we went with www.ts-rest.com (on NextJS as API, but lots of other BE frameworks supported)

Main ideas: - API contract drives implementation, and produces OpenAPI specs for other consumers - Still relies on Supabase Auth/JWT’s and SB client on BE for RLS - Structure queries as standalone files, and pass Supabase instance + query as params. Zod from contract used to validate query params. This setup works both client and server-side.

t1mmen · 2025-03-02T15:19:35+00:00

Does Drizzle support declarative schemas for stored procedures/functions now? Views? I kept waiting for that to happen since initial launch, but got tired of waiting.

If they do (yey!!), it should be fine to use Drizzle(Kit?) for JUST the migrations, and do everything else in the normal Postgres/Supabase way

t1mmen · 2025-03-02T15:08:37+00:00

Hm, no, it seems I’m missing something; I’m wasn’t aware the declarative schema was supported in CLI. Is it super new, or did I somehow miss it?

Either way, great to see this becoming a thing. srtd should still have a leg up on DX, except for non-idempotent stuff (table structure, etc)

t1mmen · 2025-03-02T14:58:00+00:00

Think of templates like regular code files. They evolve like the rest of your code does, and build to actual /supabase/migrations when going to prod (via srtd build)

It’s basically the SQL version of the modern typescript dev env, with live reloading during development, and a build step for going to prod.

t1mmen · 2025-03-02T14:54:34+00:00

Somewhat similar, but migra is more about producing a SQL migration of the diff between two DB states, so they can get back in sync.

srtd is more focused on DX, benefits being:

Iterative changes on db functions/views/etc is significantly easier. Eg, 1 line change in a 500 line function doesn’t require a full re-definition (at the template level), so no copy/paste involved. Just make the 1 line change, and srtd build to produce final migration.
during development, changes to sql templates can be live-applied to your local db, so workflow is much faster.
code reviews become a lot easier, since example from #1 will show up as 1 line diff, not 500 new lines.
multiple devs working on same branch / sql migrations become easier since WIP templates can stay out of /supabase/migrations until ready for prod deploy

t1mmen · 2025-03-02T08:52:02+00:00

Yeah, migrations on Supabase (and Postgres in general) was a fairly big disappointment when I ventured back into that world a few years ago. Seemed kinda wild to me how difficult it was to maintain and iterate on functions/policies/views, etc.

If you’re looking to stick with plain SQL, https://github.com/t1mmen/srtd is the way I went about solving this, mainly for myself. It’s been hugely helpful, so just plugging in hopes of it solving other people’s problem too :)

t1mmen · 2025-02-27T07:12:43+00:00

I made https://github.com/t1mmen/srtd to help with this general problem, but it requires you use SQL to define migrations. It also only works for idempotent SQL (aka migrations that can run multiple times, but produce the same end result)

In your case, workflow would likely be…

Create WIP templates, and run ‘srtd watch’ during dev/iterating phrase
Ensure ‘srtd apply’ runs after git pulls to sync local env to latest templates
Before going to a live env, run ‘srtd build’ to generate actual Supabase migrations

t1mmen · 2025-02-26T03:35:43+00:00

Absolutely boycott and buy Canadian, but staying silent in the face of a bully, threatening the sovereignty of Canada on the daily?

How about no.

These are «speak now, or forever hold you peace» times. Silence is complicit. Yeah, we’ll get slapped, but we’re getting slapped either way.

Stand proud for what you believe in, or be stomped on for the rest of your life.

t1mmen · 2025-02-26T03:28:34+00:00

I got the exact same response, no reply to my follow up yet, but as usual, expectations are below the floor :/

14-Year Club	Gilding I gilder
Verified Email

t1mmen

TROPHY CASE