Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
9rx
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
31 ms
·
541.
▲
by
9rx
9mo ago
> Your example worsens your position. Worsens what position? > Worse, because they believe only they’re able to know what’s best. Well, you certainly wouldn't hire a contractor if you knew better, would you? That would be poi
542.
▲
by
9rx
9mo ago
> The agile idea in itself is quite simple: Inspect and Adapt. Ish. Agile is, ultimately, about removing managers. - Individuals over processes - Working software over documentation - Customer collaboration over contract
543.
▲
by
9rx
9mo ago
> You certainly wouldn’t let your contractor improve things on your dime Where you have a contractor hired on a full-time basis with the intent to built the best house, or at least the most moated house, on the market so that all the p
544.
▲
by
9rx
9mo ago
Agile is really about removing managers. The twelve principles does encourage short development cycles, but that's to prevent someone from going off into the weeds — having no manager to tell them to stop.
545.
▲
by
9rx
9mo ago
For what reason? In case you have forgotten, the discussion is about self-driving technology, and specifically Tesla's at that. The original questioner asked why he is liable when it is Tesla's property that is making the decision
546.
▲
by
9rx
9mo ago
> Companies exist that buy cars just to tear them down and publish reports on what they find. What does it mean to tear down software, exactly? Are you thinking of something like decompilation? You can do that, but you're probably
547.
▲
by
9rx
9mo ago
If you bought and owned it, you could sell it to another auto manufacturer for some pretty serious amounts of money. In reality, you acquired a license to use it. Your liability should only go as far as you have agreed to identify the licen
548.
▲
by
9rx
9mo ago
You are missing that HN accounts needlessly overthink everything, perhaps? Otherwise, I doubt it. They have to write the tests again no matter what. Given that, there is no downside to reimplementing it while they are at it. All while there
549.
▲
by
9rx
9mo ago
> You're experiencing throttling. Use the API instead and pay per token. That was using pay per token. > Write every prompt like a government work contract in which you're required to select the lowest bidder, so put guar
550.
▲
by
9rx
9mo ago
Money is an IOU; debt. People trade things of value for money because you can, later, call the debt and get the exchanged value that was promised in return (food, shelter, yacht, whatever) I'm sure this is obvious. I am sure it is equa
551.
▲
by
9rx
9mo ago
> It’s funny that perfect capitalism (no payroll expenses) means nobody has money to actually buy any of the goods produced by AI. When you remember that profit is the measure of unrealized benefit, and look at how profitable capitalis
552.
▲
by
9rx
9mo ago
In a networked environment, which includes the web, it is typical to expose your database over the network. In the olden days clients started speaking SQL over the network, but there are a number of pitfalls to this approach. SQL was design
553.
▲
by
9rx
9mo ago
> You still gotta understand what you're doing. Of course, but how do you begin to understand the "stochastic parrot"? Yesterday I used LLMs all day long and everything worked perfectly. Productivity was great and I wa
554.
▲
by
9rx
9mo ago
Not likely. The alternative was for them to modify SQLite without the test suite and no obvious indication of what they would need to do to try to fill in the gaps. Modifying SQLite with its full test suite would be the best choice, of cour
555.
▲
by
9rx
9mo ago
> it looks like pglite is only useful for web apps Where else other than web apps (herein meaning network-attached database servers that, more often than not, although not strictly so, use HTTP as the transport layer) are at meaningful
556.
▲
by
9rx
9mo ago
> A database that can scale from in-process to networked is badly needed Why not Postgres? https://pglite.dev
557.
▲
by
9rx
9mo ago
Not so much a failure. Rather, there is no intent for there to be a market here at all. A market relies on offerings being reproducible. Intellectual property laws are designed specifically to prevent reproduction.
558.
▲
by
9rx
9mo ago
Definitely not. The Art of Software Testing wrote about "module testing" in 1979, which was revised as "unit testing" in a later revision after "unit test" was part of the popular lexicon. Perhaps that is what
559.
▲
by
9rx
9mo ago
> we all like Building software users like doesn't make for a good business model. Especially if that model has to satisfy VC.
560.
▲
by
9rx
9mo ago
Kent Beck, credited with coining the term "unit test", defines unit tests as tests that run without affecting other tests. In other words, unit tests are tests that do not introduce side-effects. I suggest that if you are writing
561.
▲
by
9rx
9mo ago
Tests are the specification. That they also happen to be executable is there only to automatically ensure that the program actually conforms to the specification.
562.
▲
by
9rx
9mo ago
Testing, which is better known as documentation, is the contract for users that defines what your program is for and how the user can depend on it forever into the future. The test runner is not the focus, rather the effort to validate that
563.
▲
by
9rx
9mo ago
I successfully vibe coded an app in 2023, soon after VS Code Copilot added the chat feature, although we obviously didn't call it that back then. I remember being amazed and at the time thinking the game had changed. But I've neve
564.
▲
by
9rx
9mo ago
I have only ever successfully tried "vibe coding", as Kaparathy describes it, once, soon after VS Code Copilot added the chat feature, but timestamps tell that was in November 2023. So two years is quite realistic.
565.
▲
by
9rx
9mo ago
Okay, Micro$lop.
566.
▲
by
9rx
9mo ago
> "when it's done" is somehow acceptable for the rest of the business to function. Well, it is the truth. It won't be done before it is done. It is understandable that there is a business that needs to function, but
567.
▲
by
9rx
9mo ago
> And I was referring to end rows, not the entire field. As was I. 10% loss is considered typical, but that amortizes to only ~4% and ~2% for two and five acre fields respectively. So you suggest that 2% is "terrible" and &q
568.
▲
by
9rx
9mo ago
It is, rather, that managing a manager is like training a dog. As in, if you take a day off later in the week after feeling slighted as the article suggests people do, the manager will never realize that your absenteeism is a result of what
569.
▲
by
9rx
9mo ago
Of course, the "object-relational mapping" problem is simply that of latency. In the theoretical world where latency isn't a thing, there is no such thing as the "object-relational mapping" problem. In the real worl
570.
▲
by
9rx
9mo ago
25% would be quite extreme. There is some evidence of that much loss on individual rows being possible, but not the entire headland. 10% is considered to be more typical, which works out to be around a 4% loss across the entire piece. Which
More ›