@lauriewired Same conclusion it might be because the market got flooded due to job security, high salaries (and probably other factors I'm forgetting). I wouldn't be surprised to see smaller passionate communities coming back to life
@colinhacks I have to say that so far it has been great, I mostly used it to review PR (need to tests the other usecases) and I have been impressed with the kind of details that it picked up
most companies already have a semantic layer. it's a YAML file last updated by someone who left 18 months ago.
this is why agents can't answer basic questions about your data. manual curation doesn't scale. you need systems that self-configure and stay current without human intervention.
📚 Creating thin abstractions is easy, until you’re trying to build them on top of functions that heavily rely on generics.
I wrote about the tradeoffs of wrapping useQuery and why type inference makes this trickier than it looks.
https://t.co/IHaPOtqodI
@kitlangton Really felt like Douglas Adams was trying to teach me layers 😅 As usual great post, to me the greatest strength of layers is not having to think about what is a service and what is not, it's a pattern you can repeat over and over again
@cnakazawa I am struggling on this as well, I ended up using 2. Where it fails: if you have a shared internal package used by a package that you publish to npm, you will have to fight with https://t.co/5FemFyWVfV to make it work (open to suggestions)