3 ms·
Good article, but it doesn't really introduce any concepts that I haven't heard (or said) already. There was the line about "not introducing much process and s
by ChrisMarshallNY 5y ago
Good article, but it doesn't really introduce any concepts that I haven't heard (or said) already.
There was the line about "not introducing much process and structure," as basic Agile principles. I completely agree (and have said so, myself[0]), but the issue is that software folks (and engineers, in general), don't like "blurred lines." We need empirical data, measurable artifacts, concrete results, etc., so that "fuzzy logic," (what I consider) "true" Agile really needs, is difficult, in practice.
This is why I think that experienced engineers, that treat the vocation as a "craft," are often better suited to "true" Agile. They understand the ramifications of decisions that need to be made quickly (without having to run a formal risk analysis and methodology review).
Remember that the authors of the Manifesto were all highly experienced and capable engineers. They wrote a document that basically chronicled the way that they, themselves, approached development.
As for bugs and tech debt; personally, I abhor debt, of any kind. That posture has served me very well, in life. Tech debt is just another loan shark.
I like to run on what I call "constant beta." The application is always what I consider to be "bug free" (we all know it isn't, but let me have my happy place). If I encounter a bug, I stop all forward movement, and fix it; even if it is a "small" bug.
As you can imagine, this was not something my managers used to allow, but, as I no longer have a manager, I do it this way.
It works wonderfully.
[0] https://littlegreenviper.com/miscellany/concrete-galoshes/ https://littlegreenviper.com/miscellany/concrete-galoshes/
- carlmr 5y ago>If I encounter a bug, I stop all forward movement, and fix it; even if it is a "small" bug. Reading through the Toyota production system this is one of the things that is recommended for finding issues early before they become big issues. Stop the manufacturing line, find out what's wrong, fix it, continue. At the beginning you will be stopping a lot, and I still am in awe of the manager that got this technique approved the first time, but after a while you will find that you just produce fewer bugs by virtue of a) recognizing patterns in how you produce bugs and avoiding them, and b) not having to work around as much technical debt, these clever workarounds are what bites you later.
- ChrisMarshallNY 5y agoIf I recall, Toyota was really the company that prototyped a lot of techniques that have informed Agile, and other Lean/JIT processes.
- carlmr 5y agoI think so, but I never saw this stop the process type quality thinking from any agile proponents.
- marcosdumay 5y agoThe manufacture Lean and JIT were disseminated by Toyota. But the software development things called of Lean and JIT aren't exactly equivalents of the manufacture versions of them. I also disagree that the equivalent of stopping the production when you spot a defect is fixing your bugs as soon as you see them. The equivalent would be something more meta, as asking yourself why that bug was created and changing the way you work (like in adding a linter rule).
- deleted 5y ago[deleted]
- carlmr 5y ago>The equivalent would be something more meta, as asking yourself why that bug was created and changing the way you work (like in adding a linter rule). Which is exactly what you do after stopping that production line and finding the issue.
- xorcist 5y agoThe very idea that software should be produced by the same production techniques we use to manufacture cars is a sickness, and the sooner it can be eradicated from popular culture the better. It's everywhere from Lean to that insufferable Mary Sue of the Phoenix book. It makes for decent storytelling, but it has nothing to do with how any successful software has ever been made. There is no assembly line and we do not pause it. It is a parable that is actively unhelpful. Lean manufacturing was not even invented to develop or design cars, so it's purported origins doesn't even make sense. See also "software is like construction work" which used to be popular before. That wasn't useful either, and anyone who's seen the construction business knows it's nothing like management literature of yesteryear would make it out to be. Sorry for the rant. I don't hate agile. This just happens to be a sore spot, comparing software to "a car" is intellectually lazy. We should be able to do better. It's easy to imagine the day when someone asks why we can't design cars the same way we design software. Not the other way around.
- hutzlibu 5y ago"The application is always what I consider to be "bug free" (we all know it isn't, but let me have my happy place). If I encounter a bug, I stop all forward movement, and fix it; even if it is a "small" bug." I have the luxory of no manager either, but I like to move fast and not have the cost of context switch, to immediately fix every small UI bug or glitch, like I used to. I rather keep track of them and usually wait, till I drown in warning messages - and then I take the time to properly clean up and refactor things. I found out, this way I am more efficient. Because since I suffer from perfectionism, I would get lost in fixing and improving small things. Now I mostly ignore them and focus on the important stuff and only fix things immediately, if they are in the way.
- ChrisMarshallNY 5y agoBelieve it or not, I move very fast. In fact, I often have to stop, because the rest of the team can't catch up. A lot of that, is because I've been writing code for over 30 years, and a lot of my personal process is "muscle memory."
- hutzlibu 5y agoI see, we have to do a coding competition at some point ;) But sure, routine helps. And probably also what you are building. I am mainly working on a big project with lots of legacy code involved, that is just not right. I cannot just fix anything I come across. I would never get the priority things of my list.
- dasil003 5y ago> I completely agree (and have said so, myself[0]), but the issue is that software folks (and engineers, in general), don't like "blurred lines." We need empirical data, measurable artifacts, concrete results, etc., so that "fuzzy logic," (what I consider) "true" Agile really needs, is difficult, in practice. This is a good observation, but it's not just engineers: the fact is most people don't like ambiguity, and the more it cuts across org structure lines the less they like it. This is no big deal as long as the org structure lines are well drawn and business are covered adequately, however at scale it also limits the type of changes that can be done without massive pain, and creates a risk when new needs are identified that are not well served by the existing structure.