codethoughts.io

I've been thinking lately on what bothers me about how AI is being discussed and why the performative nature of the people in the space bothers me so much (amongst other things).

I recently set out to finally get hot reloading working for my Rust GraphQL API, after getting annoyed by the usual cargo watch flow, which would kill my server in between code changes and it finishing the rebuild + setup.

I recently started using Turso, which is a great database option for serverless as well as to keep costs low.

From a couple of founders, to a small team, to being a “small startup”, moving into scale-up territory, and finally transitioning beyond, there are many changes your organization will go through.

I recently moved my blog from https://codetalk.io (now my commercial site) to https://codethoughts.io.

One of my absolute favorite methods of deploying Frontends is to pre-generate all routes statically, and then let each route load the dependencies they need for interactivity.

This is for sure something that will keep evolving over time, but I got inspired by this Hacker News post to share in more detail how I organize myself and my work (you can see my short answer here).

💡 2026 update: These days I would highly recommend using Expo + React Native for Mobile + Web development, if Mobile is a core platform for you.

This is a part of the post Mobile: A different way using Rust?.

This is a part of the post Mobile: A different way using Rust?.

In the last post we built up two Frontend Apps, one using Next.js and another using Leptos (Rust/WASM).

Generated Table of Contents by inserting a {{ toc() }} shortcode with a depth of 3: This shortcode actually just inserts <!

In the last post we set up our deployment, fully automated on merge to our main branch.

In the last post we created our Control Tower structure with all of our AWS Accounts in it.

In the last post we went over the overall goals of "The Stack" and what we will be building.

This will be a series of blog posts where we will build up the perfect infrastructure setup for the majority of usecase, aka "The Stack".

Governance and setup Goals: Low cost, high flexibility, modular approach to infrastructure pieces.

What are we looking for?

What are the motivations?

A lot of web development is transforming JSON one way or another.

With Apple increasing their focus on making the iPad a viable device for work, it is time to revisit using my iPad as a workstation for programming.

Recently I was faced with the challenge of having to migrate a set of AWS DynamoDB tables to completely new tables.

A lot of progress has been going on to make Haskell work on mobile natively, instead of e.g. generating JavaScript via GHCJS and using that.

If you want to grab the whole code from this post, it can be found at codetalkio/Haskell-Electron-app.

This seems to be an often asked question, so I thought I'd try and share the approach that I've arrived at after having explored a couple of solutions to the problem.

In a recent thread on /r/haskell about how to motivate the AMP proposal in teaching, I read a comment that finally helped me understand the purpose of Functors, Applicatives and Monads.

Having recently discovered sameroom.io I wanted to update the codetalk IRC server to be compliant with their authentication method.

I have recently started caring a bit more about security on my AWS applications, and to this end Identity & Access Management (IAM) users are a great way to limit access to a need-to-use-only basis.

Or really anywhere that https://pushover.net supports.

So, if you're like me and like to have your IRC client (in this instance irssi) running on a server in a tmux or screen session to never miss out on the conversation, you might feel like you're missing some of the benefits of running a local IRC client.

UPDATE: I wouldn't really recommend this approach anymore!