Current group I am working in is responsible for functional architecture. In spite of the fact that I don’t have any practical experience, I have been asked to help define a practice in Business Capability Modeling.
I think the reason for that is that I have some practical insight into the requirements that functional architecture or functional systems design places on a business capability model.
The most core principle of functional architecture involves the semantics of units of work. In fact business capability modeling is about defining the semantics of units of work – so there is my connection point.Continue Reading
I recently spent some time working my way through “Learn Python The Hard Way” by Zed A. Shaw. Zed is a programmer who has accomplished more than most in his short time on Earth. He is outspoken and often edgy, and has a reputation for being both brilliant and blunt. Zed is the creator of the Mongrel server engine that powers many Ruby on Rails sites.
Zed comes off as a Hard Ass, more than anything, and his proposed methodology to learn programming is hard, as in hard assed, not hard as in difficult. Learn Python The Hard Way is old school. Which is good, because I am old. It reminds me of learning Fortran in my freshman year of college in 1980. Hollerith cards. 039 keypunch machines. All batch processing. When you are dealing with “physical” cards, and physical sorting of program steps, and waiting an hour to see if your code compiled, let alone executed to completion or got a correct answer you tend to do alot more “desk checking” than we do today. That is the thing that I like about LPTHW is that it teaches some technique around old school desk checking. Like reading your code backwards to find errors, something that we often did on green bar paper at a table at Helmut’s Alpine Kitchen at two o’clock in the morning with a pot of coffee and an order of biscuits and gravy.Continue Reading
Its 2014, almost 2015 and conventional wisdom about computers and programming have changed dramatically in the last 30 years since I graduated college. The number of people who use computers have changed from 10% to 90% in that period of time. My Google Nexus phone has way more memory and compute power than the mainframe I learned programming on in college. The PC that I bought in 1986 had a 20 megabyte hard drive – that would hold about 10 images shot on the camera embedded in my phone, or one shot in raw mode on my DSLR.
In the 1950’s into the 1970’s, computers were physically large, occupying large rooms and requiring many attendants or operators to manage. In the 1970’s the microchip or integrated circuit technology allowed computers to be built that would fit on a desk. Now we all need a laptop, a tablet and a phone and maybe a watch or a pair of glasses that are all computers of some kind. We have computers in our cars, smart homes. All our video gaming consoles are just computers.
Conventional wisdom which 30 years ago saw that computer programming was a highly specialized skill, now sees that everyone should learn how to code, even if they don’t do it very often. This is because as computers become more ubiquitous, we need to understand them – the same way that every should know basic auto maintenance like changing the oil or mounting the spare tire when you get a flat. The same way we know how to unclog a toilet or sink drain or oil squeaky hinges in our home. Computers are so much a part of every day life that we need to understand more about how they work.
So lets just accept the conventional wisdom for a moment. What does learning to code mean? What is code exactly and how does one learn it?Continue Reading
Sometimes in life and work, we become convinced of a need to change before most of those around us. Either we read the tea leaves, or we see the bigger picture, or some how we just were able to jump through the problem straight to a potential solution. Maybe we have worked through all the analysis in our mind and have a detailed idea that could be a slam dunk, a quick win, or a major turn-around for the organization. The problem is simply that everyone else is stuck in the status quo. Maybe they don’t see the problem clearly yet, maybe they just are not willing give what change requires – or maybe they just see the obstacles to change as being unavoidable or worse, unforeseeable. Maybe they see the risk of the change as many times larger than the risk embedded in the problem.
You have tried telling them. You had tried to convince others that your idea is good, that it will work. You have “told them until you are blue in the face.” Somehow, you end up coming off as unhelpful. People generally get defensive when you try to tell them about the problem, you can’t even get the solution on the table.
Perhaps the issue is not that your analysis is weak, or your solution is not worthy, but only that it is not shared. How do you get others to share your perspective, and to help champion your ideas? How do you get them to understand that the status quo (which they have been working hard to build and keep going) is going to turn out to be insufficient to achieve the larger vision? How do you get them to “disinvest” themselves in the way things are, so that they can invest in a new idea? How do you get them to be open to your ideas, instead of getting defensive?Continue Reading