Hacker Newsnew | past | comments | ask | show | jobs | submit | d0100's commentslogin

I've reduced queries from minutes long to 2s in Postgres by duplicating a CTE and keeping it unused

Query planner feels pretty LLM-esque already


This isn't a conversation about the guts of query planners but postgres is known for what can only be described as gremlins in the query planner. But that is not the same thing as being non deterministic.

LLMs seem to create abstract, local jargon as a side effect of way it reasons using tokens

ChatGPT told me its "semantic compression"


Gamers Nexus has a 2h video doing reverse engineering and a lot of tests


I checked their site and it looks like a write-up hasnt appeared yet. They did a good one for their GPU black market story so hopefully they didnt just forget :)


I'm guessing that's at least (partly) the impetus for why we're seeing these articles now.


by partly you mean entirely


We can always streamline creativity by allowing agents to post jobs on mechanical Turk


> We can always streamline creativity by allowing agents to post jobs on mechanical Turk

Which is maybe why Mechanical Turk will be shutdown in 3 weeks. No more people laundering AI.


Not anymore! [0]

[0]: https://www.mturk.com


> a self-contained, signed extension ecosystem

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


In 2.0 you can sign extensions with your own key and have your own extension repo. Thats the plan at least.

In 1.5 - Haybarn has its own signing key, but its much faster to get extensions released and deployed.


> we hire Juniors to help fill the talent pool with the hope that they will be productive in a few months

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


FWIW, your pessimism isn't entirely well-founded. If you're in a hot, tech-centric market, then yes, staff will be far more inclined to job hop for comp increases. But if you're hiring remote or you're located outside one of the very few tech hubs, employees value quality of life and workplace culture/relationships much more highly relative to comp. E.g. If you're hiring a SWE in Nashville or Portland or Columbus they're going to behave differently than if you're hiring in the Bay Area, Seattle area, NYC, Boston or Austin.


I think those sorts of priorities come later. I've never known a junior engineer that prioritized anything much beyond "holly shit, someone finally gave me a job, and I'm making money!". Then, with something on their resume, they realize how they're currently being taken advantage of, and hop to a significant pay increase.


Depends on the field I guess. Some smaller companies I've seen have dramatically lower leadership costs, so ICs get more of the share of the gross revenue. Even with perhaps a discount to clients for choosing a small business, they can still come out on top


An employee just got phished by adding a number to a legitimate deviceAdd login route that bypasses 2FA and adds a device with full access to office and mail

Probably working as intended...


Sounds like one of ADOs recent security misconfiguration vulnerability announcements. The customer is blamed, for not quite hardening everything the right way, when ADO config is... A sizeable task.


I always click NO to these, that's full human error. edit: The underlying issue is that they send a 2FA before asking for a password at all.


My workflow for production code:

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


> GPT 5.4 instead of 5.5.

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


> Python is, thus, clearly superior to other languages in terms of ease of review.

Do we get visual comparisons along with this bold claim?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: