Totally amazing! I love it!!! I'm going to have to use it in a song.
Slashdot videos: Now with more Slashdot!
I started out with the same thing that a lot of other people have talked about: pretend to go along, be a bit (or a lot) stupid, mis-hear or mis-apply instructions, etc. Then, for some perfectly legitimate reason I coughed. Inspiration struck. I faked a heart attack even telling the guy I wasn't feeling good, making noises, and then pretending to fall and drop the phone for some real banging sounds. The guy on the other end of the line was so concerned he stayed on the line an extra five minutes without me saying a word. He hung up and then called back. I let it ring through to VM. I was chuckling for weeks afterwards.
This might be interesting for people: Enterprise Agility - Pragmatic or Transformative.
Practical professional stuff to learn about: design patterns, refactoring and test-driven development. Start learning this stuff as soon as possible otherwise you'll make all kinds of awful mistakes when your doing your first professional gigs (assuming you get to that point).
LOL!!! Although I have to say, that even learning _about_ homeopathy would probably be a good idea... just to avoid it.
For wanting to learn something.
Disclaimer: I work as a consultant for large and mid-size businesses.
My experience is that there is no magic bullet for quality, but that there are a few things you can do that will dramatically improve things. What Agile methods bring to this is that they provide fast feedback with customers and users. This means that if the team actually bothers to use the feedback, that they can produce things that have better customer and user perception of quality. Additionally, Agile engineering practices such as refactoring and test-driven development can be used to effectively prevent most technical quality problems. Agile borrows heavily from Lean thinking in which one of the ideas is to build quality in (instead of testing at the end). Lots of practices of Agile methods support this idea and, on rare occasions, I have seen Agile teams building complex systems with defect rates close to 1 or 2 low impact defects per year.
That said, the disciplines of waterfall thinking are often lost when an organization switches to Agile. These disciplines around deep analysis, seeing the big picture, etc. are all still important. They should be done differently with Agile, but they shouldn't be forgotten.
Unfortunately, most teams and organizations do neither waterfall nor Agile well. This is because management has a poor understanding of what it takes to properly support staff who are doing complex creative problem-solving work. Instead, management tries to control staff as if they were assembly-line robotic resources. Ultimately, to be effective with software development, management needs to treat software developers as each being unique, autonomous, and deeply valuable for their own talents, skills and experiences. Likewise, software developers have to stop treating customers and users as idiots... they're not. Agile methods, as a set of values and principles, are about changing these relationships to make them more healthy for everyone involved.
The military has a huge budget. Why not re-direct some of that to climate change reduction efforts? Solve the problem not the symptoms. Maybe it's because climate change is just another reason to grow budgets, grab more money... and perpetuate the system itself.
Backdoors, privacy laws, etc. etc. etc. are all about reacting to problems that have already happened. I wish people would recognize that we have a fundamental "spiritual" problem (not religious) which is that we need to learn to care about others. Any society that focuses on individual satisfaction and freedom is going to loose the balance with good social behaviour. "Save the children" is all about reaction to a society that fundamentally values the individual freedom too highly and over and above societal health. I think of this as spiritual because it is about our fundamental beliefs and feelings. Wouldn't it be much better if we could effectively educate everyone so that we all cared about each other? Our education systems focus on individual accomplishment and have only minimal support for service, teamwork and other activities and attitudes that would help educate us on supporting each other. In other words, preventing perversion through education.
For a lot of robotics work you need to be able to install software on the computer. Not sure if that would be a problem or not, but Arduino and Lego both require good access to the computer. Something like a Raspberry Pi or Oodo which is already a computer itself might be a better starting point if there are restrictions on accessing a host computer.
I did work in construction (and land surveying, and drafting, and other related fields) but only for a short time. So maybe I had no idea what I was doing... but that's actually the point of the article: software folks who want to use the construction analogy to come up with an "architect role" are doing something from a place of profound ignorance and the analogy is deeply flawed.
Lack of architecture is not the same as lack of an architect. Indeed, no architecture in a system == chaos. But how you get good architecture, unfortunately, is rarely from architects.
Oops. Meant to say "there was never a moment when all the applications weren't fully functional.
It's true that the old system(s) were a sort of guide, but it really was a complete replacement/re-architecture. Not only that, but there was no time in the project when we had a document that said "this is the current architecture". We had to do a lot of exploring along the way.
My job title prior to the project was architect but I told the CIO that it was unnecessary and so at the start of the project I was no longer the architect. We didn't have one. That said, there was a big team of us and we had lots of ongoing discussion about architecture - as we were building out the new systems. No doubt I influenced those discussions somewhat, but I certainly was no longer the authority.
Great article! Thanks!
I was the senior architect reporting to the CIO of Charles Schwab. I was responsible for huge systems at an architectural level. Then, with the permission of the CIO we launched a two year enterprise re-write covering hundreds of applications and dozens of technology platforms from old green-screen cobol systems to modern Java and
Of course, I'm not saying that there was no research, that there was no good design thinking, or that we never thought about the future. But there was certainly no architect and there was not technical lead who had the final authority on the overall design or any particular detail.
I've seen this approach work with $20M projects and with $200K projects. I've seen it work and result in systems with zero defect rates extended over years. I've seen it work on systems with thousands of lines of code and systems with millions of lines of code. It's possible, it's just that most people have been so brainwashed by the construction analogy and "scientific management" thinking that it's hard to imagine that it's possible.