One concept that Aikido has thought me, is a profound insight about what perception truly entails. For me personally it is the development of a subtle constant focus of everything around you, from people to your environment.
There has been books written about using the principles of Aikido in the business world. But what about software development? Software only being technology still gets designed and used by people. I like to think that I apply the principles I have learned in Aikido to my work environment. Yet it has come to an interesting situation. Taking into account my peers with their strengths and weaknesses I decided to guide them to keep their work simple. As such that the framework I designed was kept simple in standard Java technology. No new or external tools/frameworks/utilities. I knew that if I were to use to much of the latest and greatest that inherently the complexity would have been raised, making their learning curve so much steeper.
So there is no fancy utility, no automated build tools, no framework simply copied from the web. The work done has been designed from scratch with my fellow developers following all the way. I like to think that they have a better understanding what frameworks in general is all about and why we use them. Question is, by taking a bit more interest in my peers technical skills development, will I be considered as a good architect? Or should I have spend more attention on the solution? Have my heighten perception of those around me cause me to make incorrect decision concerning delivering a project. I read in an article the other day that return of investment in software development does not lie in the lines of code, but in the developers that can read that code and turn it into business sense.
FYI my team have met all their deliverables with probably the most stable code I have seen in the last few years.
[ add comment ] ( 2 views ) | permalink |
( 2.8 / 108 )
Calendar
