Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sgarland
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
37 ms
·
751.
▲
by
sgarland
1y ago
As a non-Haskell programmer, all of that was easily readable. Straightforward words for functions makes that pretty easy.
752.
▲
by
sgarland
1y ago
AWS: “We’ve separated compute and storage by a large physical distance, which makes relational databases better.” People who knew better: wild laughter.
753.
▲
by
sgarland
1y ago
Much like how the more you know about how computers work, the more mind-boggling it is that they work. The Internet? Magic. CDMA? Wizardry. EUV? Sorcery.
754.
▲
by
sgarland
1y ago
Fun fact, I was a Nuclear Electronics Technician, and have a decent understanding – though admittedly not to the level of an EE – of how computers work at a very low level. I also worked for a chip fab for a couple of years, and literally m
755.
▲
by
sgarland
1y ago
Interactive terminals didn’t write code for you, and also unlocked entirely new paradigms of programs. Debuggers, if anything, enabled deeper understanding. Intellisense is in fact a plague and should not exist. Stack Overflow, when abused,
756.
▲
by
sgarland
1y ago
Cursor has been confidently incorrect repeatedly when discussing databases at my job. It doesn’t understand how MySQL works, and wants to make terrible indexing decisions because of it. You wouldn’t know that it’s wrong unless you already k
757.
▲
by
sgarland
1y ago
No, you missed the point entirely. The author was correctly pointing out that if you don’t struggle, you will not understand how things work. Claim otherwise all you want; centuries of pedagogy have proven this time and time again. You have
758.
▲
by
sgarland
1y ago
> The real horror isn’t that AI will take our jobs—it’s that it will let people in who never wanted the job to begin with. I fully agree. This already happened with the explosion of DevOps bullshit, where people with no understanding of
759.
▲
by
sgarland
1y ago
The other reason to not do this is that most functions someone might want to add are very simple, enough so that even if you don’t know C, you can probably muddle your way through it. JS in an RDBMS… shudder
760.
▲
by
sgarland
1y ago
Because I/O isn’t free? If you can write code that does fewer things, it will be faster.
761.
▲
by
sgarland
1y ago
Why not use the native functions [0] of the DB? Presumably they're going to be faster. For example, computing the median of a table `nums` with columns `id` and `num` can be done like this: WITH ordered_nums AS ( SELECT num
762.
▲
by
sgarland
1y ago
Fair point. I did briefly think about finding the Unicode symbol on my phone. My bad.
763.
▲
by
sgarland
1y ago
For the same reason that every other Imperial measurement is absurd – they’re completely arbitrary. 1 inch is 3 barleycorns, which can have very different sizes. 12 inches to a foot, because a human foot is a decent measurement, I guess? 3
764.
▲
by
sgarland
1y ago
Sure, but a. IME, volume controls with 1-10 are nowhere near log b. many manufacturers don’t even do this. A lot of car manufacturers seem to use 0-40 for the stereo volume, which seems completely arbitrary. I’m assuming they decided that’s
765.
▲
by
sgarland
1y ago
Nothing better than spending hours encoding something, only to discover you got one of those wrong.
766.
▲
by
sgarland
1y ago
> The units are implied by the context. This is the absurd part. There do exist other ratios that masquerade as units, e.g. specific gravity, and its meaning also changes depending on what you’re using it for - liquids are compared to pu
767.
▲
by
sgarland
1y ago
Do you also leave trash on the ground when you come across it in public? Try to leave things better than you found them.
768.
▲
by
sgarland
1y ago
Tbh I’d rather have MariaDB. It’s wire-compatible, but has way more features, like a RETURNING clause. Why MySQL has never had that is a mystery (just kidding, it’s because Oracle).
769.
▲
by
sgarland
1y ago
Your one-off analysis doesn’t trump the normal OLTP workloads.
770.
▲
by
sgarland
1y ago
> I've seen plenty of works rejected because "why train a small model when you can just tune a large one?" or "does this scale?" I'd also argue that this is important because there's not infinite data n
771.
▲
by
sgarland
1y ago
Sure, but if the product in question is at best tangential to your core products, it sucks, and makes your work flow slow to a crawl, I don’t blame employees for not wanting to use it. For example, if tomorrow my company announced that ever
772.
▲
by
sgarland
1y ago
Then don't use a relational database. Sorry for being rude, but joins are an integral part of the relational model. If you want a KV store, you should use a KV store; if you want a Document DB, you should use a Document DB.
773.
▲
by
sgarland
1y ago
> Except stuff like addresses or names, those I intentionally don't push to be normalized IMO, it depends. While the idea of normalizing names is amusing, I probably wouldn't ever push for that either. For addresses, though, I
774.
▲
by
sgarland
1y ago
The only thing UUIDv7 exposes is its creation time, which isn't tremendously useful or secret information.
775.
▲
by
sgarland
1y ago
I'm so glad I'm not the only person pointing this out every time they're brought up. I don't think I've ever felt the need to name and shame a company before, but this was just an egregiously horrible decision that
776.
▲
by
sgarland
1y ago
Because I know the language...?
777.
▲
by
sgarland
1y ago
Given that their first query example has a leading wildcard as a predicate (WHERE p.product_name LIKE '%shoe%') and doesn't take case into account, I have doubts.
778.
▲
by
sgarland
1y ago
> It depends, sometimes just feeding back broken SQL with "that didn't return any rows, can you fix it" and it comes up with something that works. But how do you know if the SQL is correct, or just happened to return resul
779.
▲
by
sgarland
1y ago
Can't wait for another regex-induced massive outage [0]. [0]: https://blog.cloudflare.com/details-of-the-cloudflare-outage...
780.
▲
by
sgarland
1y ago
Unless you have a much more regimented code review process than anywhere I've seen, "a random person" can impact prod quite easily by introducing a bad query into the app. Since ORMs are rampant, it's probably heavily ob
More ›