Architectures

So, at work I am the guy who draws shapes with mysterious blocks and lines that other people eventually try to convert to software. Furthermore, I tend to have an opinion on almost anything. Don't ask why, but they call me Ming the Merciless here.

It's a little more than just software. I operate at the boundaries of software design and business. I bug everybody.

IT strategy

  • Should my company expose its APIs, or should we wait?
  • How do I crank up the numbers of my software distribution?
  • I have a legacy system that doesn't communicate with our web front end, but I still like it; is it possible to change it without throwing it away?
  • Should we deploy a uniform IT infrastructure, or could we combine products on different platforms just as easy?
Stuff like this matters. I deal with it every day.

Agile methodology

To establish a rhythm in development, that will keep the project members on track even when the going gets tough, a development method can be used. I like agile methodologies like XP, SCRUM and WUP.

Implementing a new methodology hurts, but is also very rewarding. I have seen teams up their speed enormously by doing so. And it's a hobby, too.


You are trying to view the newsticker in a browser that doesn't support it. I am sorry.