Friday, 13 June 2008

So here I am



Yes, i want to become a software architect at some point :). I'm coming from the world of network management, with 5 years experience in development and maintainance of large, distributed and heterogenous network management system.


At some point in the past i did a study of this domain (methodologies, models, standards, products, sub-domains, etc.) and I thought it was a vast land.





But now, when half through gathering materials to dive into software architecture domain, I can see that SA spans even wider area with even higher number of different perspectives.

It is hard to tackle this topic without being easily locked to some specific language or technology (or hype :)). On the other hand it is hard to stay technology agnostic without the risk of levitating too much to the ivory tower tops.

From what I have learned so far, SA is an aspect of software engineering, that spans through variety of sometimes orthogonal topics. In other words, as a software architect you ought to have a broad (but not necessarily too deep) knowledge on every possible topic related to software development and even beyond that.


This might be discouraging at the beginning, especially that if you want to get some knowledge on SA from the web (or books), there is a lot of noise out there :).

So in this blog im going to post various links to (IMHO) valuable materials for aspiring architects :). They will include architecture and architect blogs, podcasts, articles, etc.

The topics will include:
- software design,
- software architecture (patterns, good practices, etc.)
- software development lifecycle (process, methodology, techniques),
- technology (beware, as im biased a bit towards Java, and i decided to choose this one as my tool of trade).

No comments: