Half of All Engineers

Question

Post reply

Half of All Engineers

Steve Jones - SSC Editor

SSC Guru

Points: 741933
More actions
April 29, 2026 at 12:00 am

#4768916

Comments posted to this topic are about the item Half of All Engineers

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80411 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Doctor Who 2 SSCrazy Eights Points: 8254 More actions · Answer 2

WOW!

Steve, you've given me a lot to think about in this post. I've got to think about this for a while.

Rod

Jeff Moden SSC Guru Points: 1004725 More actions · Answer 3

I wonder why people think that "moving slower" is a bad thing.

The good part about that is, they're going to need people to fix the stuff that the companies that moved fast produced.

Ah... what of AI? I've been testing certain aspects of that for more than two years and I'm writing an article about one of the "Silent Failures" that it writes, which is actually a catastrophic failure that could get a company sued or worse.

I also use AI to help me "speculate" on code and sometimes it comes up with some pretty good answers. But... here's the catch there... you need to know enough to ask the right questions. Otherwise, it simply resorts to the "Most common answer that can be returned the quickest". In other words, it's works like a "consensus engine" near the beginning of most sessions for a whole lot of people that don't know what to ask next. And so, what I call "Corpus Infectious" (my name for the "band wagon" that frequently has chicken poop in the hay) prevails and becomes even more self-perpetuatingly infectious.

And, because a whole lot of people just don't care to learn and just want a "good enough for now" answer, AI will prevail.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Steve Jones - SSC Editor SSC Guru Points: 741933 More actions · Answer 4

I think moving faster is good, but, as Jeff noted, you have to know what you want to move faster and evaluate the outputs. For repeatable stuff, where I know what I Want, it can be amazing. For speculative stuff, or things I'm investigating, not as much.

I like the slowness of some things. I've tried audio AI prompts and it's too fast. My brain doesn't interact will or smoothly enough. Writing slows me down a bit and I do better.

Like most things, it depends. Fit the tool to the job.