Readit Newsmattdeboard commented on Lexega Turns SQL into Signals lexega.com/blog/how-lexeg... · Posted by u/whoami4041
Looping back here - trial licenses can now be obtained instantly through the free trial form on the website with just an email. No outreach needed on your part. Here for support if you decide to try it.
Hey just saw this. I will probably take a look at this on Monday.
I also have a a scratch-my-own-itch project[1] that leverages an LLM as a core part of its workload. But it's so niche I could never justify opening it up to general use. (I haven't even deployed it to the web because it's easier to just run it locally since I'm the only user.)
But it got me interested in a topic I have been calling "token economization." I'm sure there's a more common term from it but I'm a newb to this tech. Basically, how to optimize the "run rate" for token utilization per request down.
Have you taken a stab at anything along this vein? Like prompt optimization, and so on? Or are you just letting 'er rip and managing costs by reducing request volume? (Now that I've typed this comment out I realize there is so much I don't know about basic stuff with commercial LLM billing and so on.)
[1] https://github.com/mattdeboard/itzuli-stanza-mcp
edit:
I asked Claude to educate me about the concepts I'm nibbling at in this comment. After some back-and-forth about how to fetch this link (??), it spit out a useful answer https://claude.ai/share/0359f6a1-1e4f-4ff9-968a-6677ed3e4d14
mattdeboard commented on Lexega Turns SQL into Signals lexega.com/blog/how-lexeg... · Posted by u/whoami4041
Yeah, it's one of those things that is hard to catch unless you've been bit by it before and know to look for it. Analytics teams at scale are at a much higher risk of this sneaking in, which is where automatic blocking with Lexega is helpful. No one wants to have to explain to their leadership why their dashboards were wrong from such a subtle SQL bug months down the road.
Honestly this insight feels very actionable to me. I do more SQL reporting for biz analysis than i would like (i'm a dev not a biz analyst).
I may take a crack at this tool next week.
mattdeboard commented on Lexega Turns SQL into Signals lexega.com/blog/how-lexeg... · Posted by u/whoami4041
Interesting note about left join in the CTE being converted into an inner join. Didn't know that
mattdeboard commented on Lexega Turns SQL into Signals lexega.com/blog/how-lexeg... · Posted by u/whoami4041
Great question! sqlfluff catches real things like "= NULL" bugs, implicit cross joins, unused CTEs, and SELECT *. It's a genuinely useful code quality tool. The dialect coverage of sqlfluff is also extensive. Lexega's dialect implementations focus on depth over breadth.
Lexega is asking a different question though. sqlfluff asks "is this SQL well-written?", while Lexega asks "is this SQL dangerous?". It parses into a full AST and emits signals (categorized AST components) that can be matched against YAML rules to block PRs or execution in agent runtime mode. DELETE without WHERE, GRANT to PUBLIC, PII exposure without masking, DDL that drops tables in production pipelines. The output isn't "fix your style", it's "this query violates an organizational risk policy and shouldn't be allowed to hit production".
Think code quality vs. risk analysis. Both useful, different jobs.
Good call on the GitHub link - I need to fix that.
did you use AI to write this response? Why?
> The "AI will replace all junior devs" narrative never accounted for the fact that you still need humans who understand the business domain, can ask the right questions, and can catch when the AI is confidently wrong.
You work with junior devs that have those abilities? Because I certainly don't.
Not many, but junior devs grow into senior devs who do, which is the point. If there are no junior devs there is no one growing into those skill sets.
mattdeboard commented on Microsoft forced me to switch to Linux himthe.dev/blog/microsoft... · Posted by u/bobsterlobster
My work-issued dev device is a Surface Pro 10. I can't use WSL2 for various regulatory reasons. I will never, ever work on software like this again. Worst development experience of my life because of what a miserable dev env windows is.
I know that's been a meme since forever, but my first hand experience supports it to the extreme.
mattdeboard commented on Elevated errors across many models status.claude.com/inciden... · Posted by u/pablo24602
Trying to understand what this means.
Did the bad route cause an overload? Was there a code error on that route that wasn’t spotted? Was it a code issue or an instance that broke?
it means their servers were unreachable due to network misconfig.
Is a half-empty bus more efficient than a 4-seater sedan carrying 3 people? Or an electric scooter? An electric trike? A golf cart?
Yes