I help businesses create valuable software.
Kansas
Joined April 2008
- Tweets6.9K
- Following461
- Followers1.3K
- Likes543
Build a Kanban Board With AI, Live: No Hand-Coding Required - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1vKpPNvMr…
If your team isn't delivering any working software, you don't have a scaling problem. You have a "we haven't delivered any working software" problem.
Context, Tacit Knowledge, and the Future of Software Development - AgileLnL - Troy Tuttle xitter.cf/i/broadcasts/1mxPaZggD…
Bob is a developer who says that the code he writes is so good that it is a waste of time for him to create or maintain tests.
This a visual diagram of Bob adding a new feature to the application.
That's disappointing.
Microsoft cuts M365 Family and Premium OneDrive cloud storage from 6TB to just 2TB
neowin.net/news/microsoft-cu…
Very disappointed to see that as other services increase their storage limits, the Microsoft 365 plan my family uses is being switched from 6TB of storage (a major selling point of the service) to 2TB. @MSFTCopilot
Vibe Coding vs. Vibe Engineering: AI Amplifies Your Skills (and Your Mistakes) - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1mGPaZAOB…
Why would we waste time refactoring our code as we go? Lets just finish the ticket and move on.
... a shore time later...
Maybe fast creation of code means we can spend most of our time asking if we SHOULD add new functionality instead of whether we CAN afford to do it.
There's this notion surrounding AI-assisted coding that the entire process should be infinitely fast. People gnash their teeth and wring their hands because review takes longer than the generation, and testing even more so.
So, as a thought experiment, imagine that all those bottlenecks go away. The process is now frictionless, and you can spit out eight months' work every eight hours, all day, every day. Eight months' work involves many UI changes, feature modifications and additions, etc. Let's say that 10% of the program changes during those eight months. As a user, do you really want to sit down every day, only to discover that 10% of the things that worked yesterday don't work anymore, that you'll need to learn 10% of the program all over again from scratch? A program like that is literally unusable. You spend 100% of your time dealing with the changes and 0% getting work done.
The fact that software is released gradually over time makes changes palatable. The speed of change has to be within our capacity to deal with the change. A firehose of AI output is simply impossible to deal with.
Did Well, Do Better: Reliable Retrospectives With AI - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1wxWjlOYa…
Developer: I think we've covered every possible way a user might use or abuse this.
User after 5 minutes of getting the software:
Coding With AI, Warts and All: Building a Retro Tool Live - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1qKVmyrOP…
Is this an example of doing the best with what you've been given, or an example of not caring enough to fix the problem.
A Pirate's Guide To Agile - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1kKzDPyXM…
Yes. Your code theoretically does things at the same time, just like the user asked.
But that doesn't mean anyone is going to be willing to actually use it.
Mark Shead retweeted
If you didn't measure productivity before you started using AI, a current claim that AI improved your productivity has no legitimacy whatsoever.
And even then, how did you measure productivity? That's very hard to do.
Simplicity: Maximizing the Work Not Done (Agile Principle #10) xitter.cf/i/broadcasts/1oKMvNDAb…
Agile teams need healthy urgency--not desperate panic. The role of manager is to inspire the former, but not create the latter.
Five AI Secrets That Will Give You Better Results - AgileLnL - Mark Shead xitter.cf/i/broadcasts/1nxeLMnoY…
