My name is Dr. Mark Roden and I have been developing Domino applications since 1997.
I have a Ph. D in Chemistry and to this day the most I had ever used it for is teaching a science class for my elementary school kids. My years at school taught me how to drink think and solve problems. Solving problems is a great way to learn and improve.
Teaching and sharing of information is critical to the success of any culture, including software development. The more we learn the better we are, it is a life long experience to cherish.
Many years ago I did a professional personality test and I was determined to have a “Visionary” personality. I am the kind of person who solves the problems, comes up with the solutions and then moves on to the next challenge. That doesn’t mean that I can’t do a project from start to finish, it just means that I get the biggest kick personally and my greatest contribution to a team environment is up front in a project.
But a Vision is not something which ends once development begins. The customers requirements and vision for the project translate into a vision for the application interface, a vision for the architecture, a vision for the documentation and a vision for the help and support. These things come together over the length and breadth of the project.
My Vision for this blog is to become not only another recourse which users will come to read examples and find answers to their problems, but I want it to become a place where other people also post their ideas. If this is useful to you please share you ideas, thoughts, modifications and improvements so that the next person reading the article will be more educated, more inspired and from that we all benefit.
I grant any reader the right to use my code which I publish on this blog in their application (personal, commercial or otherwise), on the understanding that you do not claim it as your own and give credit where credit is due.
All code samples and downloads are copyright Mark D Roden and licensed under Apache License 2.0.
The opinions expressed on this blog are my own and do not reflect on my employer or anyone else unless I specifically state as such. If you are bold enough to follow any of my rambling/babbling/buffoonery you do at your own risk and don’t blame me if I told you to do something stupid and you did.