jacobsenscott

It takes a lot of discipline to keep secretes out of dotfiles. You should do that anyway, even if you have a private dotfile repo. Even if they aren't secrets per se - they can still be useful for social engineering. I don't understand why people think their configs are so special it is worth the risk.

There are plenty of countries where all government services have "expired". Which one would you like to live in?

Yeah. Imagine everything else that's completely wrong in that app.

> Also what's the business model?

The hype cycle business model never changes.

The problem with LLMs is the answer always sounds right, no matter if it is or isn't. If you already know the answer to a question it is kind of fun to see an LLM get lucky and cobble together a correct answer. But they are otherwise useless - you need to do all the same work you would do anyway to check the LLM's "answer".

When all you get back is a wall of LLM generated text blocking ads will be impossible. This will go the same way as google search results. Probably within six months.

I've yet to see an LLM produce anything but disastrous bugs. Remember they don't know they're writing code that can destroy companies and livelihoods. They are just spitting out plausible but always wrong text.

AI replacing devs talk is about short term stock pumping and short term COGS reduction. The long tail is someone else's problem.

Weekend HN is always like this.

Today we have humans being trained on llm garbage - kids using it to do their homework - programmers using it to "learn" how to code, med students cheating their way through med school, etc. So the content the humans are producing and will produce is really just LLM statistical word jumbles - ie human generated content will soon be as useless as LLM generated content.

This is always because people would rather than twiddle their thumbs in meetings than work - so they drag it out as long as possible. Getting paid for doing nothing is a good deal. Meetings are never necessary, and usually the worst possible way to convey information.

You can partition that over 20 or 30 or more tables on one PG instance and have good performance - assuming a good partitioning key exists. If you need to query all 10B rows you'll have a bad day though.

PG requires a lot of expertise to keep running when you get to a billion rows or massive ingest. It can do it, but it doesn't just do it out of box running the defaults.

CH excels at extremely high volume writes. You probably can't throw enough data at it.

Random chance, and maybe a little skill.

Having a garage isn't enough. A lot of people with garages need to work everyday to pay for their garage, and food, and everything else. Bezos and Jobs both had free garages and free time paid for by their parents. I would bet the others mentioned in the post had the same sort of freebies.

That's because it's glorified search. The postgres docs tell you that without risk of hallucination. You are correct that it won't produce code that does the right thing in that context though.

Soon most software devs will just be transcribing LLM trash to code with no concept of what's actually happening (its actually required at shopify now - MS is bragging 1/3rd of their software is written this way), and no new engineers are coming up because why invest the time to learn if there won't be any engineering jobs left?

This is a marketing blog for some AI startup trying to sell AI voodoo to the insurance industry, so it just needs to sound like it might be useful for finding fraud.

This isn't a good way to learn this. If you don't know how rust memory management works you don't know if the llm is just hallucinating the answer.

"He would chuck, he would, as much as he could, if a wood chuck could chuck wood" is how I learned it.

Well, this is want American Elites want - so they can buy up the pieces at a discount.

You might want to read Moby Dick all the way to the end.

That loyalty and affection your are feeling is only going one way. I've worked for small and large places. Work is always transactional. The day the CFO at your 10 person startup that "feels like a family" gets some pressure from investors to cut costs, well, your loyalty does not factor into the decision making.

Everything devolves to ad sales. Do you know the minute details about their lives people type into chat gpt prompts? It's a gold mine for ads.

s/is/was/

That's a marketing page for something called qodo that sells ai code reviews. At no point were the ai code reviews judged by competent engineers. It is just ai generated trash all the way down.

These incremental benefits don't translate to an order of magnitude more productivity, or stability, or profitability. Given the choice, as a business owner, future proofing is about being able to draw from the most plentiful and cheapest pool of workers. The sausage all looks the same on the outside.

They're all good and bad in different ways. You just need to pick one. Ansible is GPL3, opentofu is Mozilla Public License.

In abstract CSV is great. In reality, it is a nightmare not because of CSV, but because of all the legacy tools that product it in slightly different ways (different character encodings mostly - excel still produces some variant of latin1, some tools drop a BOM in your UTF8, etc).

Unless you control the producer of the data you are stuck trying to infer the character encoding and transcoding to your destination, and there's no foolproof way of doing that.