Enterprise Geeks Podcast – Rhythm and Ruby Blues


Will Blue Ruby strike an ABAP Chord?

This episode may be short on show notes, but it’s packed full of content. Listen in as hosts Ed Herrmann and Thomas Jung expand on and continue their ongoing discussion about ABAP and SAP Java. Other topics include Blue Ruby, SAP preview edition and subscription cloud talk, and all kinds of other fun tidbits.

If you have questions, suggestions, or topic ideas for future episodes, give us a shout here. Enjoy!

Running Time: 73 minutes

Talking Points

  1. 00:15 – Random Chit Chat
    • Why we love the eGheads
    • A fan gives Thomas blue Bawls
    • Ed promotes G33K B33R
    • Show us your eGhead pride and send us your photos, wallpapers, etc.
  2. 06:36 – More on ABAP & Java
  3. 39:26 – What will Blue Ruby bring to the table?
  4. 51:10 – Could the SAP Preview and Subscription Systems be moved to the cloud?
  5. 60:47 – Closing thoughts and ramblings
    • Battlestar Galactica final review by Thomas
    • Gotta love Netflix
    • What should Ed buy to replace his broken Zune? Vote here for iPod Touch, Nano, or Classic
    • What did you do during Earth Hour?

4 responses to “Enterprise Geeks Podcast – Rhythm and Ruby Blues”

  1. me.yahoo.com/a/abI0B_Anu… says :

    @Ed and @Thomas:

    Nice podcast as always -:)

    About Blue Ruby…I’m very excited about this and had already get in touch with the developers…To me why is important to have Ruby inside SAP? Easy, first because it demonstrates the power of NetWeaver as a development platform, second Ruby is very powerful and easy to learn, third because I don’t like Java and having Ruby as an Scripting Language will provide us the power to embed not only Ruby to ABAP but also ABAP to Ruby…You guys know I have wrote plenty of blogs about Ruby and SAP using Piers Harding’s RFC connector…Not having the need to use such a connector would be great too -;)

    AFAIK, Rails is not going to be supported, because we’re going to be able to use HTTP as both Server and Client. I’m not sure about Gems like #Camping, #WxRuby or #Gosu…But would be nice to have them too…

    About your broken Zune…I got an 4GB Ipod Nano…Which is working fine for the last 4 years…So I’m really happy with the IPods performance…My choice would be an IPod Touch…Thinking about getting one as soon as mine get broke -:'(

    Greetings,

    Blag.

  2. KK Ramamoorthy says :

    @Ed – My preference would be IPOD touch. Will go for it just for the apps. I had a bad experience with IPOD classic, my disk failed after 13 months (just out of warranty). But again, that was a couple of years ago. May be Apple perfected it now. I have a Nano now and use it as external hard drive as well.
    @Tom – Good points on ABAPers who don’t want to change. On another note, what I have noticed is that there is some reluctance with project managers (@system integrators) to have their teams venture in the newer development technologies, especially in new implementation projects. They haven’t used it before, so they will not risk using it in a new project, especially if it is a fixed bid project or a project with tight budgets and deadlines. Though not always true, but most times, newer technology, among other things, should reduce development effort but that’s a learning curve, decision makers have to deal with as well.

  3. Jon Reed says :

    Guys, another great listen. Thanks also for such an honest and good discussion of SAP programming skills, one of the best I have heard. Just today I heard from another ABAP person who wants to move to functional because there are supposedly no good careers in ABAP. These discussions matter.

    Classic Ed: “Go buy a book!” I think there’s something to it though. I think there is a lingering sense of entitlement that SAP careers are easy to bust into and that once you’re in, you can surf the wave. Hitting the books is a much better strategy in today’s here today/outsourced tomorrow market.

    Perhaps this is a strained analogy, but given we are in March Madness maybe I can get away with it. I watch a lot of basketball and one thing you make a note of is how many high-flying dunkers have short-lived NBA careers- especially after they tweak their knee or what have you. Then you contrast it with someone like Tim Duncan, who spent four years in college, picking up the skills foundation that earned him the nickname “The Big Fundamental” from Shaq.

    SAP is kind of like that these days – you’re not going to succeed in this changing market without sound fundamentals – in the case of your discussion, sound programming fundamentals in ABAP. Along with the fundamentals, people underestimate the importance of simply staying current. Object-oriented ABAP, Web Dynpro ABAP – instead of bailing on ABAP, if you juice on ABAP, then learn the stuff that makes the enterprise move.

    Thomas, you talked about how you can linger on older releases if you want, but I’m not sure you went far enough in terms of emphasizing just how vulnerable to the “global labor sourcing” trend we are if we allow our skills to become commodities. The way to avoid that is as you guys pointed out, NOT necessarily bailing on ABAP but taking that track of mastering fundamentals and moving to new releases pertaining to your core. (Rather than bailing on ABAP for Java or even functional stuff).

    Geez, I think I’m starting to go on a bit here, I think I’ll turn some of this into a more detailed blog post on my site and link back to this podcast for any SAP developer who is trying to understand how to make sense of this stuff.

    Before I close out, I just wanted to mention one thing: I think it would be cool if you had a real SAP Java geekhead on the program. You made a point about how ABAP was once an easy entry point into SAP, being easy to pick up (which might lead to the analogy of the high-flying dunker without the fundamentals). But doesn’t Java have an easy entry point also? As in: “I did the Java work on my cousin’s goth metal web site?”

    You talked about the differences between SAP Java and other flavors, but isn’t there also a leap between “my cousin’s web site Java” and “Enterprise Java,” whatever that enterprise flavor might be? So in future Java talks, you might want to touch on the journey so-called web programmers need to make in order to move into enterprise-level work, and maybe even the pros and cons of such transitions as clearly it’s not for everyone.

    Keep on geekin’!

    – Jon –

  4. Vijay Vijayasankar says :

    Great podcast – nicely done.

    Couple of comments
    1. People stick to “old” ABAP for few reasons other than comfort feel. Some get stuck in support projects on old versions, and still do classical reporting and BDC today. Their employers never give them a chance to do anything else. A few who cannot take it any more, quit and go elsewhere.
    2. The old ABAPers can succesfully move to be a functional guy. Very few functional guys have a technical awreness, or an ability to debug. You can solve most problems with debugging, even if you don’t completely understand the OO part or the presentation layer code. So this is a nice niche for older ABAPers to salvage their skills.

    I have a request – can you guys discuss BSP vs WebDynpro sometime? I am so frustrated in managing a team doing ECC on webdynpro and CRM on BSP. Do you think SAP will ever unify this?

    Cheers
    Vijay

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: