But a good part of this problem is that the businesses are focusing on the short term buck. Whether it's the big corporations or the brand new startups. Get a product out there, collect your $$ and cash out. The short term "gain" of rapidly building products (code) using AI sure may get something new and interesting out there (can't say it's innovative if AI is rehashing something for you), but any long-term prospects of reliable and secure code are laughable.

All hail the profits for today, because the profits of tomorrow are far from guaranteed, so get it all now and party like it's 1999.

(Totally coincidentally, next article for me to read is titled Samsung CEO warns of "do-or-die" situation, urges investment over short-term profits so someone may be paying attention)

"You've found the Wumpus"

I'd much rather see some sort of definition of repairable to at least allow goods to be repaired (or easily dismantled).

Sure, the idea of repair is natural. Hey, your toaster is busted, you can disassemble it without too many specialized tools and a quart of epoxy. But if you can disassemble it, it also means you can break it down into smaller parts that can at least be properly disposed of. (metal shell, plastic knobs, copper cords, etc.)

Alas, I fear it might still be too high of a hurdle for those people that don't even break down their Amazon boxes, but it at least help ensure that manufacturers have to put some thought into the afterlife of their goods...

... But how big is that survey sample size, and who didn't respond?

Basically the survey can only look at those people who bothered to respond to the survey, and it's tough to say how big the sample pool size is/was, compared to the real count of developers. Sort of a self-selection bias.

I'm aiming along the lines of the survey being skewed towards those already using (or needing to use) AI in their workflow, vs the hidden majority(?) that AI isn't either applicable, or don't want to bother answering the questions.

Why do I have a craving for microwaved hard boiled eggs now?

I thought Data was the new Bacon! Crunchy, Tasty, Slightly bad for you.

Just wish I had the T-shirt to prove it.

Thumbs up on HDFS. The next question to ask your groups how they will be analyzing it. HDFS (and Hadoop/Spark/Whatever) will hopefully fit in nicely there. Not only will your data be redundantly copied across multiple systems, but as your data needs (and cluster) grows, so does your computational power.

Getting data in & out can be done via Java API, Rest API, FUSE or NFS Mounts. The only issue is that HDFS doesn't play well with small files, but hopefully your groups will be using large files instead.

Now administration is another story, but then there's Cloudera's Manager that's supposed to greatly simplify management. I'm currently using it to store about .25 PB right now for random analysis, but growing it's capacity is a straightforward task.

As far as backing up, HDFS provides snapshots, 3x replication (or more) across nodes in the cluster. Of course there's always the big hammer of just getting a second cluster. As an old HW sage once told me, "If you can't afford to buy two, don't buy one"

Never ever ever do development on your workstation, unless it's close enough to your production environment. If his company had enough $$ for a Macbook, I'm sure they can shell out another $400 or whatever for a Dell workstation that runs the same distro as the server.

No I didn't RTFA, but give me a break. It sounds almost as bad as developing an application using MS Access.

(Yes I have a MBP, and I develop on Linux servers all day)