Business requirements are often presented as a boogeyman to developers. They are boring, work on them is futile, and we never get them right. But it doesn't have to be like this. I hope I can inspire a few folks that there is value in understanding the subject

I had to write the article about the Technical architect position, especially because the position has been recently questioned in many circles. And it is not because I am a serving technical architect, as that means very little. I find immense value in the position, as do many other developers.