HN user

hilariously

636 karma
Posts0
Comments250
View on HN
No posts found.

Yep, SO was dying before the GPTs - in some ways it was baked in the original SO design - to become the canonical source of information about programming stuff.

Many people talk about the negativity, and they are right, but I think the reason more than anything is the waiting. On SO a good question might get answered in minutes (if it was easy and someone was karma farming) but it could be days or weeks for general purpose stuff; compare that to a few seconds for an LLM its a no brainer.

A great point, you will also eventually be in a constant state of failure, and have to turn that into something you can manage, automatically.

It depends on who you are paying for it, but generally a distributed system is harder to reason about, harder to fix, has weirder edge cases, and much more easily get into situations where it requires even MORE expertise to fix than just having a big honking server.

When you start calculating things that are not just the server, the single server looks cheaper and cheaper. How do you get a consistent backup? How do you do DR? How do you tune queries when it could go to this node or that node? Now writes are going to be significantly slower if you need multi-node commit because no matter what you are racing the speed of light on the network.

Chromium is probably 30 million+ lines of code, and we generally see that as things get more complex its even easier to accidentally write code which can be exploited.

If it has 1 vulnerability in every 10k loc of code we'd be talking about 3,000 vulns (with no churn) - we used to care about defect density, and most software wouldn't go more than a few hundred lines without SOME bug, whether that's a "vulnerability" is often a layered question.

And one built without it and not coordinating with it is often much harder to reason about when you bolt it on later.

I think you and and your parent are in agreement, you CAN do something, but it's not useful, and then you have to either by convention or additional fields deal with the leading zeros and other non-numeric aspects of phone numbers.

I would also teach young programmers (about data) with the shorthand used above, things like "Do you want to add phone numbers? Multiply them? Utilize fractional components? Why are we storing these as numbers?"

Mostly because machine coffee tastes like shit, the incentives are off for it; its usually in a place where you cant get good coffee and they do not give a fuck if you like it or not, enjoy your caffeine that you are addicted to.

It's just purposeful blindness - I worked for a company building out tooling that insisted markdown based security was good enough and showed it off for anyone at the company to attack because they were so sure.

It took me less than 5 minutes to completely disable... nobody cared, they just kept going - check the box and move on.

Its sort of a CORE database feature, the "data control language" - access permissions, schema mapping and object mapping, views abstracting functionality, stored procedures granting RUN AS powers and proxying permissions - they are all very old and well worn tools.

The truth is that accountability isn't the problem, its the lack of resources, prioritization, and ability to change things that make them burdensome. After a certain point you're just trying to solve the problem in the least annoying way possible.

Why do you think the top 1% pays that much in tax? Because we impose arbitrary taxes on them or because they get the vast amount of the wealth as well?

What's the top income tax bracket? Does it go up to Jeff Bezos levels or does it taper off quite a far amount below that?

How much do you value a stable society that doesn't promote mass death? What percentage of the wealthiest's income should we recognize comes from a world that is stable and peaceable because of opportunities for us all?