The most powerful form of AI collaboration is not AI generating code but using AI for understanding code.

Fullstack Engineer Remote - UK, Ireland, or Netherlands

We have an open position for an #elixirlang developer in the UK, Ireland or the Netherlands. You can find the post here, or reach out to me directly.

job-boards.greenhouse.io/workera/jobs...

GitHub - bytebottom/turso_ex Contribute to bytebottom/turso_ex development by creating an account on GitHub.

It's still a shell of a library, but personally I'm really excited about it. BEAM nodes are easy to deploy near users, getting the data there as well has always been the hard part. Hopefully this solves that.

For now, it's just me having fun with NIFs. #elixirlang

github.com/bytebottom/t...

I'm learning so much about how the beam works by implementing a library with Rustler. Very interesting stuff. #elixirlang.

@drewr.dev love the things you are doing with ecto_libsql. I was thinking to leverage the new turso library so I get the vector and search support that it has. Were you planning to support the new Turso library at some point? What's your thinking on that?

Big upgrade to my Claude Code. Guess which movie this is?

Cognitive Debt. When you use AI to build fast, the debt doesn't accumulate in the code. It accumulates in your head.

Design is the work now. Cognitive debt is the newest drag on productivity.

petar.dev/posts/cognit...

100%, that's why I build a skill library for our company where we are sharing skills with each other.

3rd rewrite of a new agentic system in 48 hours. Frustrating? Yeah, a little. But I'm learning so much.

It's a relentless loop: hours on the design, execute fast, hit reality, learn, restart. Each pass I'm making fewer mistakes and building real intuition for how the system I'm building works best.

Maybe if I reach a 1.000 followers, my kids will think I'm a cool dad.

Let me know what you think and how we could improve them. PRs or comments are welcome. Let's share best practices so we can use LiveView and all its benefits without compromising on the user experience.

Second is working with forms, where you have to make sure that forms don't get wiped on reconnect, or when and how to use debounce to make sure you don't spam the backend.

github.com/wunki/amplif...

I created two skills which I always found to be gotcha's when working with #elixirlang and LiveView. Both can have a big impact on user experience.

First, LiveView and optimistic updates, making sure that the UI stays responsive, even when there is latency.

github.com/wunki/amplif...

With this setup, I built an app in ~ two days that exposes internal knowledge as a bot in Slack and via MCP for ChatGPT and Claude. Every conversation is logged and easy to debug, so you can see exactly which choices were made. All without external libraries.

One of #elixirlang’s superpowers is how easy it is to reason about: its functional model keeps complexity in check, built-in observability is excellent, and Tidewave pushes it even further.

For observability, I record and correlate every important session. Through Tidewave, codex can use that context to debug itself.

I even have it build custom UIs so I can inspect everything in real time.

Codex is mind-blowingly good at writing #elixirlang. I can spend hours iterating on system design with it, optimizing for simplicity and observability.

Once that clicks, the result is a system that is easy to understand and easy to debug, for both me and Codex.

If Codex fails on #elixirlang with "failed to open a TCP socket in Mix.Sync.PubSub.subscribe/1, reason: :eperm" try this setting in your ~/.codex/config.toml:

[sandbox_workspace_write]
network_access = true

It's the small things, but things like this make agentic coding in #elixirlang much better.

GitHub - ocean/ecto_libsql: Elixir Ecto database adapter for libSQL/Turso Elixir Ecto database adapter for libSQL/Turso. Contribute to ocean/ecto_libsql development by creating an account on GitHub.

This is a very interesting project that pairs perfectly with #elixirlang LiveView, where data locality is so important. Put servers around the world (easy), have data close to the user (hard).

github.com/ocean/ecto_l...

Thank you! Just got a DM, will follow-up if that doesn't pan out.

Anybody by any change have a Lobste.rs invitation for me? There are some good discussions happening there and would love to participate.

My thinking on Finde has evolved and I couldn’t be more excited. The scope is bigger and sharper: a second brain that improves while you sleep, with you driving every decision.

While it with blogging, a blog is now just an output of you sharing one of your notebooks.

beta.finde.app

Note: Copy/Paste for OpenCode with Ghostty and Tmux Remote devs: fix OpenCode clipboard on Ghostty + tmux by enabling OSC52 clipboard access and tmux passthrough.

I like to work on the server, but copy-paste was not working in my Ghostty/Tmux and OpenCode setup. After some debugging, I got it to work:

petar.dev/notes/copypa...

Made my #neovim theme available. Also lots of extra to have harmony with ghostty, tmux and opencode :)

github.com/wunki/gondol...

Brain fart, record all key strokes and commands in Neovim. Give that to an LLM to analyze. Let it make suggestions to improve your flow.

Honestly, I don't care at this point. But, it's also fine because I'm using Dokploy and it has zero-downtime deployment capabilities (docs.dokploy.com/docs/core/ap...)

With Elixir you have to make sure you build things "the right way" because a LiveView reconnect will happen off course.

I have the AX42 server on Hetzner for 54 euro's per month and it's more than enough for many projects. Always had good experiences with them.

Right now, I'm mostly using it for beta.finde.app.

Happy 2026! I reworked my landing page for Finde. What do you think? Is it clear what I'm trying to build here? Like the design? Would you use it?

beta.finde.app

Love that, thanks for sharing! In the Netherlands we have "vinden", which means finding something.

I thought it was nice for "finding your own voice" or others "finding" your content :)