Software Engineer

Joined July 2016
Alexander Obukhov retweeted
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax. - 100-500× faster than mermaid.js - 6× smaller bundle - No dependencies - Easy to theme - Responsive to device width In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now. Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
290
892
190
11,457
665,949
Alexander Obukhov retweeted
Rewriting Postgres in Rust: complete. 1:1 reproduction of Postgres behavior. All test cases pass. Production-ready.
200
172
47
5,617
349,430
Migrated my personal site from Jekyll to Astro with a coding agent. It picked an older Astro version, so I upgraded it. The next day, Astro shipped a new major release. LLMs are still catching up, JavaScript keeps moving fast, and somehow I hit three major versions in a few days
27
Everyone seems to be building an AI harness now. So I’m building one too. In Elixir. I’m currently on my third attempt…
1
1
37
The second attempt also went off track pretty fast. I do not even remember all the details now. But after cleaning it up, I kept a few pieces. Those pieces became the base for the current version.
1
16
The third attempt is intentionally bottom-up. First, a tiny loop. This lets me get closer to the basics and understand them by building them myself. There is still a lot ahead. But many parts of the harness are already more clear now. Let’s see where this takes me.
15
Alexander Obukhov retweeted
Elixir v1.20 released! Now officially a gradually typed language: Elixir type checks every single line of code, finding bugs and dead code, without developer overhead (no typing signatures) and extremely low false positives rate. Plus a faster compiler! Links and reports below.
55
307
47
1,491
129,577
Alexander Obukhov retweeted
Replying to @bcomnes
Just click the eye icon to see a rendered preview of Markdown.
1
1
1
17
1,318
Alexander Obukhov retweeted
From @josevalim's first commit to millions of lightweight processes running in production — happy anniversary @elixirlang! 💜
39
1
211
7,689
Alexander Obukhov retweeted
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.
501
1,891
394
15,246
1,624,426
Alexander Obukhov retweeted
So many tools could learn from this. Keyboard shortcuts should be driven by being physically efficient, not by necessarily actually sharing letters with the action being performed. We had this right in the "keyboard sticker" era, everyone does it wrong now!
Replying to @ivbobrov @paper
100%... we think about keyboard hand vs. mouse hand a lot
13
5
1
145
32,331
Alexander Obukhov retweeted
if cli has tui - you do it wrong if cli startup time is 5s - you do it wrong the new wave of cli tools undermine the power of cli tools the unix systems used and tuned for perfect.
3
1
21
3,550
Alexander Obukhov retweeted
Very suspicious that OpenAI and Anthropic both dropped major announcements within hours of me publishing this: dashbit.co/blog/why-elixir-b… They want to silence it. Don't let them. Read it twice. Share it with your colleagues and friends.
40
80
14
629
78,020
Alexander Obukhov retweeted
The best thing about working with Codex/Claude Code is that when you give it a task, no matter what it is, it doesn’t get upset because it’s hard or because it doesn’t like it. It just gets to work without unnecessary questions. ❤️
1
55
Alexander Obukhov retweeted
The ACP Registry is live in today's Zed release Register your agent once, and it will be available to every ACP-compatible client. Adopting ACP has never been easier! Thank you to @JetBrains for pushing forward the registry specification 🙏
8
17
2
269
17,097
Alexander Obukhov retweeted
Congratulations @duboc_guillaume! There is still work ahead, but having a whole PhD thesis on Typing Elixir is a massive step forward! Thanks to the CNRS, Remote, Dashbit, Fresha, Starfish*, and Supabase which made this research possible!
Defending my thesis today at 1:30pm CET: "Typing Dynamic Languages with Set-Theoretic Types: The Case of Elixir". A few years of research on typing Elixir using set-theoretic types. Feel free to join, Zoom link in my website.
4
29
285
11,694
Alexander Obukhov retweeted
Today we celebrate 15 years since Elixir's first commit. To mark the occasion, we shipped an early release candidate for Elixir v1.20 which has TYPE INFERENCE FOR ALL CONSTRUCTS.🎉 In the latest article, I break down the next ~15 weeks and the challenges for the next ~15 months.
26
111
9
568
33,892