JohanvanSeijen  -

My name is Johan van Seijen. I'm a Software Designer. Let's do some Q and A.

Question: What is software designing?
Answer: It's something that doesn't necessarily include include Microsoft Word and Excel, although practice seem to prove otherwise.

Question: What's it good for?
Answer: It saves you money. A lot of it. That is if you're trying to build a piece of software.

Question: There are so many design methods out there, what makes the thing you do the right one?
Answer: Multiple roads can lead us to Rome. That still doesn't mean we should drive on the wrong side of the road trying to get there. Or walk for that matter. Both may work, but they could either get you killed or take you forever. During software projects sometimes a decision is made to not make a software design, the equivalent of driving yourself of a cliff thinking you can fly. Othertimes the decision is made to write a specification... emphasizing the word "write". That's the same as an architect sending you a 10 page document describing the house to the ones supposed to build it instead of drawing the damn thing. Guess what I'm trying to say is a picture paints a thousand words. So let's includes lots of appealing pictures in our design (having to do with the software we want to build).

Question: Will it be difficult to let our project teams work with you designs?
Answer: Depends. Quality, effectiveness, pride and professionalism sure isn't something everybody strives for in their job. On the other hand, it's something that can be achieved with my designs in the hands of people who are willing. I often remark that if personal goals are aligned with organizational ones there's nothing a company cannot achieve. The same goes for your projects. But even if you have doubts about your people, there's never an excuse not to design something you want to have build. I'd like to think that achievement is a personal choice to some extent.