Re: The AutoDesk File
Thanks for the link to the online version.
12 publicly visible posts • joined 31 Jan 2013
The fairphone 3 sounds great -- I'm tired of replacing phones just because the battery is worn out. The fact that one can replace the display, cameras, speakers, and microphone by oneself is great news. Too bad it won't work on most networks in the U.S.A.
Suggestion for fairphone 4: move radios to a single module, then offer different modules for EU, UK, USA, etc.
I'm certainly showing my age/experience here -- over my career in software development I've endured iso9000 certification, six sigma, total quality management, and a few others that escape me at the moment. Somebody is always writing a dissertation, gets their degree, writes a magazine article/book, and bingo, the management types see something they can implement to discuss in their annual review -> get raise for. Unfortunately, for us, this results in yet more silly process stuff and buzzwords to learn and slow down development.
Agile is just the latest fad iteration, which I'm seeing fail regularly today -- much to the chagrin of management. IMHO, Agile seems fine for small, relatively straight-forward projects without many dependencies. It fails for large, complicated projects with many dependencies / stakeholders. I've seen it over and over again. For such large projects, we're back to using the waterfall process -- which provide the schedule / resource information managers need, and we meet the schedule we've produced, so management has learned (again) to trust us.
I remember the day management first sprang Agile on us -- all of us experienced folks had the same look on our faces -- time for a blanket party for the Agile advocates -- using our copies of "The Mythical Man-Month" book by Frederick P. Brooks Jr. to beat them with. But, of course, experience has show us that sometimes trying to reason with management doesn't work and you have to go through the motions and let them see the folly of their ways themselves. First large project using Agile was a disaster. Testing folks didn't get what they needed when they needed it, Documentation folks couldn't get people's attention, components didn't work well together, quality greatly suffered, and we had no idea when we'd be "done". Senior folks performed triage, rescued the project. So -- now we do Agile for small projects, waterfall for larger ones.