All parts of BAPO have a home turf of problems/aspects/challenges it can address efficiently. For instance, maintainability is best addressed in the architecture, rather than some complex maintenance processes or special teams designated in the organization. In most cases, modifiability is best first addressed in the business, where only the essential modifiability is prioritized and rest is eliminated to save on complexity. Knowhow management and regulations etc. are mostly best addressed in the organization and process areas. While some technical risks are best addressed in the architecture, I was surprised to hear of a case where the business people covered against a risk by just arranging an insurance, thereby relieving the architecture of the complexity. Continue reading BAPO imbalance
Some of you have probably noticed that there was a long delay in the posts. The reason was, as I indicated before, our move as a family to Switzerland. The move still tends to take most of my available time (ramping myself up in the new role as well as chores such as registration, insurance, finding daycare…), so I still cannot promise a regular rhythm of posts. In the meantime, I’d like to convey two observations about my posting rhythm. Continue reading The vicious cycle of delay
Anecdotal observations tell me that NIH (not invented here) is for the most part dying, and the general level of software reuse has increased significantly in the last ten years: Continue reading Choosing SW for reuse
When I was a developer, I could work on a single task for several days. It was a bliss. When I started doing architecture, I noticed I had to do a lot of multi-tasking. At the very least, there will be multiple developers working on different tasks, whom I will support. Moreover, I need to talk to testers about testability, integration strategy etc. At the more senior end of the architect role, I need to talk to business stakeholders about product strategies and so on. And sometimes all this happens on a single day. Frank Buschmann wrote a nice article demonstrating A Week in the Life of an Architect, where he emphasizes keeping focus over the course of the week to ensure progress.
Thus, around the time I started architecting, I also started looking for some time management techniques: Continue reading Personal time management for the architect
Hello, it is somewhat embarrassing to have to send another heartbeat after such a short while. I’m mainly busy moving from Turkey to Switzerland, and my blog suffers from the interruption of the routine. Anyway, next post will come up in a few days. Stay tuned.
A good vision can be demotivating. An architect maintains a vision (north star) for a system that is hopefully shared by at least the key stakeholders. Every step of the evolution of the architecture is taken towards to this vision. However, there are also cases where the evolution is not advancing towards this vision: it can be stagnating, maybe even moving in another direction due to uncontrollable factors. “We could be so much better, but we are still faltering in this quicksand!” Such a situation is frustrating as hell. Continue reading The demotivation by vision
In a couple months, I’m going to switch to another division of my company, so I’m leaving my current project after 5+ years as an architect. The new architects of the project, the project leadership and I have thought about how to manage a successful transition. I’d like to share the measures we are currently implementing, and kindly ask for feedback on them and for new ideas, as well. Continue reading When an architect leaves his project
Hi there, I know it’s been awhile since the last post. So here a heartbeat to tell you: next post will come up in a few days, blog is alive and well. ;-)
Most architects, me included, are passionate about their work. They follow the state-of-the-art of their profession, they think about refactoring topics to improve the architecture under their responsibility etc. And the point is, they do these without anybody telling them to do so. On the contrary, most architects will negotiate with the management to be able to access more resources on architecture such as books, conferences; or to be able to implement the refactoring ideas. This is a good example of intrinsic motivation.
This context prepares us, the passionate architects, for a mistake: we assume that everybody is passionate about architecture, yet, in fact, people have different sources of motivation. So we do not invest time in aligning with other stakeholders, and we end up with a bad architecture or a failed change initiative. Continue reading Levels of aligning with people
I was a late adopter of podcasts, but I came to like them a lot. They are much more relaxing than reading articles or watching videos after a busy day at work with strained eyes and visual cortex. In addition, they give me a linear stream to follow, which is also relaxing compared to hypertext with a lot of links and pointers to divert my attention. In fact, if I’m really tired, a podcast lulls me nicely to a nap, a trait I had only experienced with books before. And I can also combine podcasts with some manual work like washing the dishes. Finally, it’s a not-yet-completely-monopolized part of the media, so I can find some ad-free good content directly from experts working in the fields I’m interested in. I learned a lot from the podcasts in the last 4-5 years, and I would recommend them to any software architect.
So here some of the podcasts I listen to regularly, in a bliki fashion I intend to update the list over time. Continue reading Podcasts I like