HN user

judgardner

71 karma

comprehend.com

Posts1
Comments30
View on HN
EnshittifAIcation 4 months ago

Had a similar experience with a vendor. Marketing team requests we add some DKIM settings for yet another vendor that is gonna spam people on our behalf. The requested record is

* TXT test

I explain that's gotta be a bug on their UI, we send a screenshot to the support of the vendor. The marketing team has 4 turns with an AI that refuses to escalate to a human and is convinced this is the only entry it needs us to add to our DNS. Dropped the vendor. Someone from their retention team followed up and we linked them the ticket talking to the bot about the obvious bug. Never heard back.

Agree. I have been using Postgres and Oracle in production since ~2000 (oracle 8i). Postgres is an amazing project but the oracle core database has billions of R&D dollars. Don't confuse the oracle core database with the awful applications they hang off of it. Oracle will still destroy pg for most OLAP workloads, now you have to decide if the insane licencing cost is worth it.

Also just want to add an oracle developers post that I find hilarious...

https://news.ycombinator.com/item?id=18442941

I think there are two use cases here, I was referring to debugging during development and a lot of replies are regarding troubleshooting an active prod system.

Of course we all hope for well thought out logging to troubleshoot issues we're seeing in prod.

I'm referencing an pattern I see with junior devs who simply use "printf debugging" in development instead of learning to use a debugger properly, even with distributed systems.

Fair enough, but attaching multiple debuggers across several interacting components with conditional breaks gets me there faster than incrementally inserting progressively more print statements, in a dev environment. Proper logging is a given doping out problems in a production system to then verify and correct in dev.

DRM in TIG welders 11 years ago

Agreed, this is pretty standard. One production run reduces cost and if you want the advanced features you pay more.

> GNI is just a grand total divided by population;

Right, per capita, as I stated, but really just GNI is fine too.

> people would be making more if the money was divided up evenly but it's not, particularly in the U.S

Unfortunately the google public data didn't have enough US data but take a look at these two charts for India.

First is just India's per capita GNI the second is India's income distribution over the same time frame. Notice how the income distribution is relatively flat and how the GNI is growing.

http://www.google.com/publicdata/explore?ds=d5bncppjof8f9_&#...

http://www.google.com/publicdata/explore?ds=d5bncppjof8f9_&#...

I see this problem among less experienced developers who have a lot of talent. These devs exude 'know it all' and can back it up on some narrow set of knowledge/skills. Part of maintaining this impossible image requires not asking questions that might show cracks. Pretending to know everything is a sure path to not knowing much of anything given enough time and I've seen developers go down this path.