4 ms·
I think the core flaw here is thinking of software development as "manufacturing". It isn't at all. It's a design process. This Toyota methodology is about tak
by davidbanham 9y ago
I think the core flaw here is thinking of software development as "manufacturing". It isn't at all. It's a design process.
This Toyota methodology is about taking things that have already been designed and then incrementally improving them or figuring out better ways to put them together.
Building software is more akin to the process of taking a blank sheet of paper, a knowledge of what kinds of parts already exist, then designing a new car to fit a new market segment.
- 52-6F-62 9y agoI worked briefly in Toyota (as an operator: Toyoda Iron Works/Toyotetsu) sub-manufacturing and I'm a developer now. I agree completely. What might be more suited is operations development. It's quite similar to DevOps, as is, with DevOps just having been adapted more explicitly to software.
- hencq 9y agoYeah, true. Though there are definitely parts of the development process that are recurring. E.g. processes for code review, testing, etc. These are the areas the article focuses on as well. Since ultimately the software is developed by this design process, improving this design process _should_ lead to better software as well (whatever way you define better). For the actual design of individual pieces of software, I wonder if something like Toyota Product Development System is a better fit.