Most of the time, light models like gpt mini does the real work, all the "advanced thinking" models are "thinking" in the wrong direction, drifting away. Apple - Give us a real AI auto-completion, I don't want agent mode, just great auto-completion, still using VSCode
There is a small and clean demo in github demonstrating event driven architecture using CQRS pattern. That's a good use of SwiftData Query, decoupling data from UI, powerful technique πͺ !
https://t.co/iQb00at9Sq
Oh, we are going into the direction of CQRS no? Would that work ? `Query` for read only operations, direct SwiftData container for writing data from domain layer
Oh, we are going into the direction of CQRS no? Would that work ? `Query` for read only operations, direct SwiftData container for writing data from domain layer
Using `Query` in SwiftUI sounds like binding Data layer to UI layer skipping the Domain , sounds like a violation even for offline first apps. Ok for a demo project, but does it scale well in a production app?
Maybe we can have a container for the UI layer which contains view models - aggregated models ready to be presented, and use anther container for the normalized data
I have a modular iOS proiect which has most of the code in three Swift package modules, the Xcode project is the binding layer, when I ask Claude to do something it first says it canβt find the file and needs to use system βfindβ tool
#ios#claude#xcode
@pointfreeco Neat!
But is that two lines of code really a problem? The macro generates even more boilerplate. AI can generate that computed property in miliseconds so "manual" management is reduced. I prefer the left solution here and in many cases
I've made myself a 25minutes playlist in spotify. Start work, βΆοΈ the music, music stops βΉοΈ, stop work and take a break, then repeat. #pomodorotechnique