The attitude behind this tweet has me flabbergasted. The poster seems to think that the work involves lying back and raking in the big bucks while doing nothing but the easy stuff. 1/7

Another ridiculous poll. What actually slows releases? 1) Building things nobody wants. 2) Unnecessary complexity. 3) Lack of effective communication. 4) A culture of centralized control. 5) Bad process. 6) Dependencies. 7) Not trusting the people who do the work. 8) Large batches. 1/2

I recently came across this misguided poll 👇. The answer is none of the above. The biggest QA challenge is creating a culture of quality that pervades the organization. 1/2

Regarding the speed of an AI and the volume of code it can create: None of that matters.

The attached post 👇 is absolutely true for those companies that approached AI in a mindless way. The fact is that pretty much everybody is using AI. The "you'll be left behind if you don't adopt AI" thing is stale. Everybody's adopted AI. 1/10

Tim Ottinger posted this drawing over on LinkedIn 👇 [https://t.ly/bll9E]. He's absolutely correct about this. Here's an example: I once built what amounted to a small blog system that had a comments feature. My initial idea was a standard comments dashboard. 1/11

In the continuing saga of @ebay turning to crap, the entire site is down this morning. You'd think they'd want to get a handle on quality, but I guess AI is more important 🙄

Surely ebay has the money to do basic QC. I'm getting so tired of this stuff, and "AI" is making it much worse (though, honestly, this might be plain old amateurish programming). No, you can't trust the generated code. Sorry.

ISTM that above-average communication skills are an essential part of the programmer's job—always have been. The days of locking a developer in a room and throwing meat under the door once a day are over. To me, programming has always been a social skill, even more so if an AI is involved. 1/5

Plans are not roadmaps; they are sea charts. Chart your current position, your destination, and the known hazards; the route changes with the wind. Plans are experiments that need to be validated as they unfold. Plans are questions, not answers.

The attached post is interesting in that it argues AI is dangerous, contrasting it with a word processor, which the author claims is not. Putting aside the inflammatory rhetoric, let's focus on that "dangerous" notion. 1/12

It will come back. (Gartner predicts that will happen within the next six months.)

"War is peace. Freedom is slavery. Ignorance is strength" We are living in Oceania.

So? If you want to write buggy software, don't let me stop you. As for bug bounties:

@zettberlin.bsky.social I just tried misspelling my name, and it corrected it. That said, my name is plastered all over its training data. In any event, I would _always_ present the "corrected" version of something to a user for verification. In a text field, this could look like a spelling mistake

Maybe the third time's a charm 😄. Yesterday, I posted that we could eliminate things like country-name dropdowns and replace them with free text, perhaps using an LLM to correct errors. 1/8

So, a few weeks ago, I posted about those ridiculous country-name drop-downs with 100 or more lines and similar 50-line ones for US state codes. (Don't get me started on year-picker dropdowns with 100+ sequential numbers in them 🙄. 1/6

If we need to invest $206,756.00 in 40 Mac minis (fully loaded), something's seriously wrong with the way we do our work.

This image is a perfect example of everything that is wrong with the usual code-review process. People debate the grammar, even though there's no universe in which the prepositional phrase "of cell phones and earbuds" can be the subject of a sentence. 1/9

Seems like the good folks at Amazon could use some instruction in basic arithmetic 😄.

An interesting choice. The devs have been spending too much time watching historical romances or GoT. I wonder how many people in the nobility have been calling tech support, demanding proper titles in the name-entry field, and why have they left out Sir and Dame and skipped straight to viscounts?

Interesting wording from Google. Are there alien settlements, too? How about dragon settlements? I'd like directions, please.

The attached screen grab should make everybody who programs AI systems pay attention. As programmers, we should never forget that so-called AI is just numbers and probabilities. 1/10

I've always hated the Apple-style infinitely-long animated web pages where the scroll wheel just moves stuff around on the page rather than scrolling. All that does is add confusion and make me work harder to see actual content. 1/12

Amsterdam!

The attached graphic is an excellent summary of everything that a good Product person does. You will note that "_project_ management," "manage tickets," "compel or browbeat people to build X," and "use Jira" are nowhere to be seen. 1/7

I can't emphasize this👇 too much. Our job is not to build the most sparkly "innovative" pie-in-the-sky "unicorn" idea. Maybe one in 10,000 of those take off, and I'm being conservative. Instead, address the pain. 1/3

Yet another defense of story points over on the Lean-and-Agile group [https://t.ly/BrLp9] got me thinking I should repeat the following as a public service announcement: Re story points (vs story counting) don't work. Story points require estimation. 1/9

I'm copying this BlueSky post👇 for amplification [t.ly/lSbSF]. "The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't." Far from a big enough sample set, but the 1/5