Here is my e-mail & wish me luck.
I would like to write an article, discussing Rails/Salesforce development. I would like to focus on methodology, as in translating use-cases into useful architecture artifacts / models. Because Ruby/Salesforce application development is relatively young, I assume most of my audiences will be beginners who are seeking introductory information. Therefore, I will begin my article talking about the Pro/Cons of Rails, its strength and weakness. How its programming model differs from that of Apex, VisualForce, Spring, Python, etc.
The main goal of article is to communicate the urgency in exploring Ruby/Salesforce as a viable development venue. And, we will examine barriers facing traditional developers, who are already accustomed to Apex, Visualforce, Spring development methodologies. While all paths lead to Rome, there are shortcuts to rapid application development methodology. Some of which leads to time saving, while others lead to potential pitfalls.
As a developer of the Ruby/Salesforce Toolkit, I am keenly aware of those problems. I like to discuss from my first-hand experience, where I made incorrect assumptions, and where I did things correctly.
To keep things simple and easy to read, I will keep source-code to a minimum. Rather, I will be examining the development methodology and architecture considerations.
It will be an easy to read article, where laymen can understand, and not a highly technical article, where only a rocket scientist can comprehend its notations.