25: CASE tools are expensive

Not... sure... what this has to do with *checks title* software development... A tool is expensive... OK... I mean... Is the emphasis on CASE tools a sign of... OK; so I don't actually know what a CASE tool is. I have a vague familiarity with the term... TO THE GOOGLES!…

24: Give software tools to good engineers

I don't like this. Right off the bat you're creating a separation between the engineers you have. There's the "good" ones and they get new shiny objects. Then there's the "not-good" ones and they have to suffer. If you don't think the engineer is good -…

23: Use tools, but be realistic

I played a lot of Dungeons and Dragons when I was in high school. It was a lot of fun. I wanted to DM. I always struggled with some elements of it. I bought a BUNCH of DM books. I had practically every 2nd edition book. Read them all. I…

22: Technique before Tools

I find that tools exist to simplify something. Either to make it easier in some fashion, or speed it up. Electronic Story Trackers make it easier to do a number of things, including modify when not physically present. Refactoring tools let us do what we know we want to do…

21: Different Languages for Different Phases

I don't like the "Langauge", but I understand it's a term we still use to refer to our different representations. As we progress in our design and implementation, we need many different representations to help us understand the system, and varying levels. Sequence, Use Case, Timing, Object, State.…

20: Record your assumptions

I think recording our assumptions is hard. If it's an assumption, how do we know we're making it? I assume stuff all the time without consciously doing it. I'm not sure we can effectively record our assumptions. Often we'll make assumptions around values that are going to be static. Or…

19: Every Complex Problem has a solution

OK... I doubt this means the cynefin framework type of Complex. That's what I use though. If it's a complex problem it's one that must use an emergent approach. We can not define the solution up front. Is there a solution - yes. That's what puts it into the Complex…

18: Build software so that it needs a short user manual

Honestly not sure what this means. OK - My take on it: Hire a REALLY GOOD UX TEAM! If it's a big product, it's gonna be a big guide. Even with a really good UX. A good UX will reduce the need for referencing the manual... That's my take. OK…