Over a million developers have joined DZone.

Dev of the Week: Eric Schabell

DZone 's Guide to

Dev of the Week: Eric Schabell

· Java Zone ·
Free Resource

Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Eric Schabell, JBoss Technology Evangelist for Red Hat and guest lecturer at the Radboud University Nijmegen. Some of his most recent DZone posts include:

1. What have you been working on lately?

I have been pushing pretty hard on the rules and BPM software here at Red Hat lately. We just released two products based on the JBoss jBPM and JBoss Drools projects. You might have noticed a lot of content around JBoss BRMS (Business Rules Management System) and JBoss BPM Suite. I have been rolling out tips & tricks articles, video howto's, and a series of online workshops that you can work on with labs being released weekly to get you started on both JBoss BRMS & JBoss BPM Suite.

I also just finished up a revision of my e-book, OpenShift Primer which you can find as of yesterdays release on GooglePlay, iBooks, Amazon, etc.  

2. Red Hat released the latest and greatest version of JBoss BPM Suite 6 in March. Is there any new feature that you've fallen in love with?

The whole suite is a big step forward in that we have now an integrated dashboard that allows you to create your business models, rules, events, processes, management reports, and view Business Activities (BAM). This is now really targeting the non-developer roles in an organization making it a product that seamlessly integrates into a developers daily projects without disrupting how the developers would work.

If I had to pick a feature I would say the move to integrate with both Git and Maven as the storage / build environments makes this product very easy to integrate into an enterprise architecture. These are the most pervasive of technologies for continuous integration and deployment strategies, so fitting into that development framework both eases adoption and increases productivity in a short timeframe.  

3. Are there any particular developer tools or resources you couldn't live without?

I can't live without OpenShift anymore... this is my PaaS of choice and I have not done any VM installations in years since it came out. I pretty much make sure most things I build can be hosted, run, and are available on OpenShift via my github.com/eschabell account.

Really it is not just the Cloud, it is a tool that a developer can no longer ignore.

Whatever you build, should run on OpenShift.

4. Do you have a favorite open source project (or projects) that you've contributed to recently?

I work rather closely with jBPM and Drools providing feedback on the eventual products that are produced and continue to maintain / grow the jbpmmigration project. I am also active within the OpenShift space, contributing a lot of projects and demos.  

5. Do you follow any blogs or Twitter feeds that you would recommend to developers?

I follow these feeds in the JBoss, Rules, and BPM space, you can find these lists here:

6. Did you have a coding first love -- a particular program, gadget, game, or language that set you on the path to life as a developer?

I would have to say my path to developer was a bit odd, I played with Basic on Apple II, Apple IIe, and Commodore64, then left it for quite a few years, swinging back around to hit Minix, Linux, Pascale, and eventually a bunch of Open Source projects.  

7. Is there anything else you'd like to mention?

If you have done anything in software development for more than 3 years, you should be teaching it. That does not mean official school teaching, but you should be mentoring, presenting, writing, and pushing your experiences out so that everyone learns from you.

Being a genius in the corner of your little world is such a shame in these times, so share it with us!

Thanks, Eric!

Check out Eric's blog and Twitter!


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}