Query planner feels pretty LLM-esque already
708 karma · joined August 3, 2013
Query planner feels pretty LLM-esque already
ChatGPT told me its "semantic compression"
What does this mean? Can I easily sign my own private extensions with my own key?
We are currently allowing unsigned extensions, loading them, then locking the duckdb config to prevent loading unsigned/untrusted extensions
The sad reality for smaller companies is that we cannot compete salary-wise, which means training juniors that will leave the minute they become productive
But mostly the issue is with the market, there are only so many things you need a junior to do in a body shop that is getting squeezed
Other companies are also cash constrained and need to pivot fast to "AI"-something, which juniors wont really help with on the short-term
Probably working as intended...
1. Pick the most complete project boilerplate (fullstack JS can easily introduce security bugs, SPA + API is best as cheap linting solves most problems)
2. Project skills (how to CRUD without mess)
3. Use worktrees for concurrent features, local session for conflicts
4. Local session for QA and refinement
I use Copilot and GPT 5.4
Managed to shorten pre-AI priced ongoing projects to 2 weeks or a month
I am exclusively using 5.4 because its only 1x and very good, but the github calculation showed my once $40 become a $680 billing
That is too expensive and not worth paying
Do we get visual comparisons along with this bold claim?
We have a simple worker setup and temporal is pretty easy to setup
Out only issue is really needing an intermediary data store for task result storage
We are using DBOS in new projects as it's even simpler and the downside (task log interface behind saas) is easily remedied with a copilot generated task viewer
If I make the LLM generate code that follows my own code architecture and style, that should be enough creative input
It's a very good model for a very good price
If you create a plan it follows it closely
Are we supposed to expose all entities and relationships and rely on row level security?
Althought it still hasn't solved procrastinating the next plan prompt
That's how Brazilian media conglomerate culture works
Being able to import from "https://my-vpn.com/mypackage@1.2.3" or "npm:package@1.2.3" and just running code without having to worry about scaffolding node_modules makes sandboxing code much easier
"Leito" sounds more premium than "cama", despite being both valid words for "bed"