My name is Steve and I am a learn-a-holic.
(all together now: “Hi, Steve!”)
I believe strongly that any day that goes by in which I don’t increase my knowledge is a wasted day.
I am a practicing software architect and engineer (yes, they are two different skills and roles) whose formal training and education is in the building architecture field (I hold a B.S. in Architecture from The Ohio State University and practiced ‘real’ architecture for years before formally moving into the software field for good).
I came to the profession of software development because of an unrequited thirst to investigate why things work the way they do and to uncover for myself the dark underbelly of the world of software engineering. I have a strong interest in software development as a process and understanding software projects’ contribution to the overall business (whatever that means).
I am a born skeptic and tend to challenge most assumptions thrown my way; I find myself to be sympathetic to most of the Agile-leaning philosophies but feel that the zealousness with which they are often espoused at the expense of dealing with reality on the ground to be off-putting.
If you want to know more about the principles that guide my approach to the professional practice of software architecture and engineering, I would encourage you to take a look at this post.