My name is Erich Ocean and I'm new to the Enyo community. I need your help and advice on some Enyo training I'm putting together this month.
Since 2008, I've taught a proven, framework-independent, end-to-end iterative methodology for development teams to think about, design, code, test, and maintain cutting-edge apps that people love to use. Apple, Eloqua, Cultured Code, and others have all successfully adopted my development methodology and developers tell me they now can't imagine working any other way.
My day long class is $1500/person, and I've taught it both onsite and remotely. The methodology I teach gives people a comprehensive mental model to think about app development and specifically helps with the 90% of code that makes their apps unique. My class is currently targeted at development teams, not individual developers, and that's what I want to change.
This month, I'm developing custom Enyo training materials targeted at individuals, not teams. My goal is to be able to do a regular, online class for people developing apps with Enyo using my methodology, approximately once every 6-10 weeks. I really want my training to fit as seamlessly as possible with the philosophy and idioms Enyo is built around, which is where you come in.
What I need are 6-10 experienced Enyo developers to work closely with me to adapt the presentation of my methodology to the coding and development idioms that are most appropriate for Enyo development. We'll do that over a remote GoTo Training session sometime in August (I'll coordinate a time that works for everyone who signs up to help).
I'll begin the workshop by teaching my development methodology for the first couple of hours, and then we'll spend the next couple of hours working out how to best integrate and teach that to other Enyo developers. This will be a hands-on, frank discussion of how best to introduce my methodology to Enyo developers, especially developers that aren't as experienced and need the extra guidance. In particular, I want to make sure I'm teaching as idiomatic as possible Enyo usage.
My hope is that after this workshop, a core of experienced Enyo developers will know both me personally, and understand at a deep level what I'm teaching to individual Enyo developers in my class and why. That should help keep everyone on the same page and give us all a common terminology to use in chatrooms, blog posts, and the Enyo forum.
If this sounds like something you can help me out with, there's a signup form at http://theoceanmethod.com/enyo-workshop
. The workshop costs $150—90% less than I typically charge to train people. I'm essentially paying you for the time you'll be spending to help me develop awesome Enyo training material for others. And you'll also learn a great development methodology you can apply to your own apps.
I can tell you upfront that what I teach will not detract from what makes Enyo great. I'm dealing with larger development issues, specifically, the 90% of code that is custom to each app—regardless of what framework is used.
My goal is to keep people using Enyo in the most productive way possible, while adding a dramatically better understanding of app development and the fundamental development habits needed to build great apps using Enyo, or any other framework. Think of what I teach as additive, not an alternative, to what Enyo developers are already doing.
If you have any questions or concerns about my training or this workshop, please email me at firstname.lastname@example.org and we'll arrange a Google Hangout or Skype session to talk about it. I'm also frequently available on the Enyo IRC channel as "TheOceanMethod".
+1 323 482-3204