@texpat the one place where I’m sure agile is a bad idea is designing public APIs. You can’t get your api consumers to change in a reasonable amount of time. If you control both ends (micro services/SOA) that’s not an issue.
@texpat You’re right that agile methods are usually really bad about accumulating any sort of design artifacts. Every decision is made in the moment and it can be hard to go back and puzzle things out - I don’t think I’ve seen that done well. About the best I’ve seen is a big test suite that has a test case with a good description for every weird corner case that turned up. Growing and adapting a database schema seems scary, but I haven’t had too much trouble in practice.
@texpat Done well it is super great. Done poorly it sucks. It is easy to do it poorly. OTOH none of the other methodologies I’ve tried has managed to do better than acceptable, so 🤷♂️
https://youtu.be/RmIgJ64z6Y4 Charles Stross talking about how corporations can be viewed as AIs that have run amok and how they use deep learning to manipulate their environment.
Smudge has a bit of the resting cat face. #mastocats
Also, this goofball seems to be afraid we will run off and abandon him again. #Mastocats
I read a lot, run, and play with fountain pens.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!