Introducing LiveStore (beta)
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
livestore.dev
Introducing LiveStore (beta)
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
livestore.dev
For each domain, I prefer to follow "the Onion Architecture". These clear boundaries lead to less friction and therefore less decision-making when it comes to changing things within the codebase.
Less friction = better DX
The debate around which web framework to use is (often) less important than one might think.
I treat the framework only as a binding layer between the UI and my domains, carefully crafting them to be framework-agnostic.
Sometimes I genuinely don't understand the attitude of people in GitHub issues.
I think we need a mindset shift in Open Source: from 'I use it because it's free' to 'I genuinely care and want to ensure its sustainability.'
And... If you haven't explored @effect-ts.bsky.social yet and want to learn about it, don't hesitate to reach out. I'm more than happy to jump on a call to share my experience and give you an introduction.
A huge shout-out to the organizers for doing an amazing job, the speakers for delivering high-quality content, and the participants for the thought-provoking conversations.
It was fun, inspiring, and simply an amazing experience. Thank you so much!
I can't wait for next year!
I'm on my way back home.
My biggest fear was that I would get so much inspiration at the Effect Days that I would become completely sidetracked and want to try all the new things I just learned.
Effect Days just delivered! It was such an amazing conference.
I'm currently in Livorno, Italy, looking forward to meeting some of the brightest engineers at the Effect Days, a breathtaking location, and an influx of enough gelato π¨ to last me the next three years.
Itβs an incredible tool (no doubt!), one that should be integrated into daily workflows. However, I don't buy the hype around that "it's over for software engineers."
When it comes to truly well-crafted, quality software, LLMs still have A LOT to prove.
Not so bad.
As humans, we tend to think in extremes, and I believe this is partly why thereβs such a buzz about "AI taking over software engineering jobs."
In my view, every seasoned software engineer knows that we're not there yetβand IMO itβs unlikely we'll see that scenario anytime soon.
That said, it was the perfect opportunity to let an LLM build the entire app while I played the role of a guide. And hereβs the final result.
He writes the letters in mirror image, which is hilarious, and according to his teacher, it's completely normal at this stage.
Inspired by this, I decided to invest 30 minutes to build a simple app to help him trace the correct path for each letter.
On AI:
Today I attended my son's first parents' evening at his school. Heβs just wrapped up the first half of his initial year and everything seems to be in order. His teacher mentioned that he occasionally struggles with forming some letters of the alphabet. π§΅
Great conversationβI enjoyed every single minute, as many of the moments resonated with me, since I see myself as just one thread too. Prioritize each aspect of your work based on your energy level, and you may discover peace even in such a challenging yet truly fascinating industry.
I do it via coder.com
There are a lot of benefits in having your dev environment in the cloud. For example, when building web apps you get a similar latency like your users (without artificially throttling your connection via the DevTools in the browser).
βCraftβs truth emerges only through the friction of material engagement.β
This piece by Ryo poetically captures the nature of my journey through the last 4 years crafting both Overtone and LiveStore.
Must read for any creative out there! 10/10
ryolu.notion.site/how-to-make-...
Episode #18 is out.
James Arthur (@thruflo.com) on ElectricSQL, read/write-path syncing and PGlite to run Postgres everywhere via WASM.
Full episode links and show notes in the comments.
What many label as "over-engineering" is often the result of thoughtful, proactive design by skilled engineers.
In reality, what might seem like unnecessary complexity can be a nuanced approach to solving complex problems.
This is what we should strive for.
Thoughtful Engineering:
We all appreciate elegant abstractions and intuitive APIs, yet there's a common mantra warning against "overthinking" and "over-engineering". However, I believe this perspective is "overly simplistic".
Really excited to kick off the Cause & Effect podcast!
The goal is to share the stories of various companies and projects building production-grade applications with Effect.
I hope you like it - as always, would love to hear your feedback!
LiveStore 0.2.0 (in early access):
β Schema-aware query builder for SQLite
β New example app: Linearlite for Expo
β Type-safety improvements & bug fixes
See GitHub for early access: github.com/livestorejs
After working with LiveStore over the past months, I can't express how excited I am about this release!
The DX is great, the vision is superb, and the sustainable development model behind the project is amazing.
Give it a try; you'll experience a fun ride!
The WOFR ("Works On First Run") rate is high with @effect-ts.bsky.social
I have never experienced anything similar before.
In my current project, I established a pattern that turned out to be quite handy:
Encoding the entity type within the ID.
Product IDs get a `pro_` prefix, tenant IDs use `ten_`, and so on.
This allows me to quickly identify the type of the entity just by looking at its ID.
I challenged the routing part and built a lightweight wrapper: github.com/akoenig/effe...
Maybe my post nerd-sniped somebody who wants to take over the request / form validation? π
From there it could move into areas like persistence, etc. as Effect offers primitives for these use cases as well.
1. Routing
We could utilize Remix (React Router) as the underlying routing mechanism and build an Effect -based API Surface on top of the loader / action primitives.
2. Request / Form Data Validation
Effect Schema is perfect here. Needs to be integrated into 1. in an easy-to-use manner.
I think there is huge potential in building an @effect-ts.bsky.social -based web framework.
First, we could start with a thin layer that only takes care of the "controller part". This would involve the following aspects:
From the era when every app was local-first by default, to today's renaissance of local-first architecture with modern tech. Not a renaissance where we come full circle, but where innovation happens, like leveraging the cloud where syncing makes sense.
Loving it.
VB6 and later VB.NET were my gateway to software engineering, and seeing this brings back memories!
bandysc.github.io/AvaloniaVisu...
My ToDo List Provider: The TypeScript Compiler.