@simeon A decade later my focus is now on trying to teach code reading to a level of proficiency that people can hold a very clear mental model in their head of how systems work.

Two (very different) sides of the same coin, and it was fun to go deep on the opposite end back then.

@skillstopractice I’m almost finished with your book and I love it because it shows that developing software is much, much more than producing code. It’s a shining light amidst all the “genAI will replace you pesky developer” doom and gloom.

As for the other side of the coin: I feel we’ll be needing these skills a lot in the not too distant future.

@simeon If you haven't read the last chapter yet I don't want to spoil it for you but I had a spot-on prediction of the development trends a decade ago but I can tell you my reaction has been... "No! No! Not like that!"

Because what has happened, has only similarities at the surface level to what I was trying to express. And fundamental incompatibilities with what I think will make things genuinely human-centric.

(That said, I still believe we can get there)

@simeon Will attempt to collect my thoughts in a more complete way and send a link when I do, but the short story is I thought the only probabilistic element of that kind of workflow would have been matching natural language to corresponding APIs, and I had hoped we would have built high level enough tools in all other ways that stacked like Lego bricks all the way up to the surface.

By contrast, GenAI drags us deep down into the Turing tarpit, especially for those who don't know how to code.