expand_less
CV Notes
Builder/Architect - publications are my works, software, systems, etc.
Order of presentation - As is the practice with resume "experience" lists of jobs and employers, the basic order is reverse chronological, start with the present. On the other hand, a CV protable is more "biographical' and needs to tell the story of your life course.
Is the "objectives" at the top still the pattern here? Not sure yet. Maybe something like:
Objectives
To teach by learning and developing new social architectures for collaborative learning environments. To mentor people in organizations to apply these architectures and social processes in their work. To produce leaders who will design and build the open future.
Learning and Doing
Most recently I have returned to making and building things in contrast to much of my life's work that has been involved in the creation of non-physical things; system architectures, computer programs and natural language texts. This is where I started; first learning to master physical things, applying paint, cutting wood, designing and building treehouses and much more. I still take things apart to see how they work and break and now more often than not I can put them back together, sometimes after being fixed or improved.
In the course of my technical career, I have used many computer languages and systems, but to list these and emphasize the specific ones would miss the forest for the trees. Most recently I have been learning [[https://golang.org|go]] to work on [[https://holochain.org/|currency protocols]] and Ruby on Rails for content management systems.
TheAs important point is just like I first learned [[https://en.wikipedia.org/wiki/BASIC|BASIC]] to get a summer job when I was still in high school, I learned Ruby and now Go in order to contribute to [[http://wagn.org|Wagn]] to further currency projects. In the first experience, I had just learned Fortran in school and was able to learn enough BASIC from a book to get the opportunity to get paid to do some programming. The motivation was differnt, but the languages aquired just as marketable. I put myself through MIT on the money I earned programming in BASIC and most of my recent paid work has come from learning Ruby and Rails in my work contributing to Wagn. Studying electrical engineering and computer science at MIT, I had a big advantage over my classmates from my early professional programming work.
New Directions - 21st Century Husbandry
More important than where we have been is what we are moving to. As our material culture changes at ever increasing rates, what one needs to know how to do changes. Horses and carraiges are no longer day to day technology, now only of historical and recreational interest, but smartphones, clouds and the Internet is. Knowing programming, HTML and CSS are just as important as shoeing a horse was in the past. In ten or twenty years you will need to know a host of new technologies and languages that are yet to be invented.
The work experience on my [[Gerry+PDF Resume|professional resume]] is largely confined to software development and systems engineering and administration, even there my interest in whole systems knowledge can be seen. Because I came up in the hobby computer era before PC when the Apple II was born, I had to learn about hardware and systems and assemble a computer system from kits, I had the hardware background to work in the PC industry. I started at Victor Business Products at the same time the first IBM PCs were shipping.
I have prototype Victor 9000 in my office. As an example this machine could become a learning by doing project to see if it might run again. Imagine a team of learners and doers powering this computer on for the first time in thirty years. Making sure the boot floppies are dust free and the drive is clean and ready and another team taking videos and learning to produce web content to document the process and teach others.
I am even more interested in the social architectures of learning and production. An integral part of any software development effort are the development methodologies used and recently many teams have moved to what are called agile processes. Not a one-size fits all methodology, but a set of social processes that are evolved in practice into working norms and process architectures that are matched to the team and its work. I am not interested in abstracting or separating this work in process architecture from the work being done. This meta-work must serve our ends, not only to make the work more effective or efficient, but to serve our human needs to work in supportive communities and to be invested in our work and the outcomes.
Builder/Architect - publications are my works, software, systems, etc.
Order of presentation - As is the practice with resume "experience" lists of jobs and employers, the basic order is reverse chronological, start with the present. On the other hand, a CV protable is more "biographical' and needs to tell the story of your life course.
Is the "objectives" at the top still the pattern here? Not sure yet. Maybe something like:
Objectives
To teach by learning and developing new social architectures for collaborative learning environments. To mentor people in organizations to apply these architectures and social processes in their work. To produce leaders who will design and build the open future.
Learning and Doing
Most recently I have returned to making and building things in contrast to much of my life's work that has been involved in the creation of non-physical things; system architectures, computer programs and natural language texts. This is where I started; first learning to master physical things, applying paint, cutting wood, designing and building treehouses and much more. I still take things apart to see how they work and break and now more often than not I can put them back together, sometimes after being fixed or improved.
In the course of my technical career, I have used many computer languages and systems, but to list these and emphasize the specific ones would miss the forest for the trees. Most recently I have been learning [[https://golang.org|go]] to work on [[https://holochain.org/|currency protocols]] and Ruby on Rails for content management systems.
New Directions - 21st Century Husbandry
More important than where we have been is what we are moving to. As our material culture changes at ever increasing rates, what one needs to know how to do changes. Horses and carraiges are no longer day to day technology, now only of historical and recreational interest, but smartphones, clouds and the Internet is. Knowing programming, HTML and CSS are just as important as shoeing a horse was in the past. In ten or twenty years you will need to know a host of new technologies and languages that are yet to be invented.
The work experience on my [[Gerry+PDF Resume|professional resume]] is largely confined to software development and systems engineering and administration, even there my interest in whole systems knowledge can be seen. Because I came up in the hobby computer era before PC when the Apple II was born, I had to learn about hardware and systems and assemble a computer system from kits, I had the hardware background to work in the PC industry. I started at Victor Business Products at the same time the first IBM PCs were shipping.
I have prototype Victor 9000 in my office. As an example this machine could become a learning by doing project to see if it might run again. Imagine a team of learners and doers powering this computer on for the first time in thirty years. Making sure the boot floppies are dust free and the drive is clean and ready and another team taking videos and learning to produce web content to document the process and teach others.
I am even more interested in the social architectures of learning and production. An integral part of any software development effort are the development methodologies used and recently many teams have moved to what are called agile processes. Not a one-size fits all methodology, but a set of social processes that are evolved in practice into working norms and process architectures that are matched to the team and its work. I am not interested in abstracting or separating this work in process architecture from the work being done. This meta-work must serve our ends, not only to make the work more effective or efficient, but to serve our human needs to work in supportive communities and to be invested in our work and the outcomes.