Is Go a Java replacement? Of course not, but I do wonder what Google's up to.
Even if you love Netbeans, don't you think Eclipse is worth $5?
I heard the news while driving home last night... This is really very good news for Java.
If you are a Developer who builds sites where folks go to "do things", then I hope can inspired you to think a bit about those "things" as part of a larger Process.
Rumor has it that IBM is buying Java - and the company that spawned it.
Chris Adamson recently questioned the value of Swing 2 and I have to go one further... Isn't it time to admit that the Desktop is dead?
There's an interesting thread going on over at InfoQ regarding the relationship between BPM and Software Engineering.
One subtext of this discussion raises a wider question - When is it "Programming" and when is it "Software Engineering"?
Which came first? Object Oriented Methodology or Object Oriented Languages? From where I was standing at the time I'd have to say Object Oriented Methodology.
Back when I was working on Tandy's DeskMate we were trying to build a personal computer "that Mom could use". I think we came pretty close to that goal... Mom could use it. Unfortunately Mom didn't want to use it :-(
Is there any chance at all of coming up with Data Modeling notation that Mom could use?
My blog entry on User Manual Driven Development prompted Chris Adamson to share some thoughts of his own: Should you have to understand the application you're writing?
Back in the days before objects, our development methodology was simple but effective... the marketing group wrote the deskmate user manual and we built the applications to match the manual.
Friends were troubled when I blogged "Object Only Programming is Silly". They know from experience that life after OO is dramatically better than life was before OO... so my criticisms just don't sit well... Obviously I must have gone off the deep end :-)
Is Programming hard... or are we making programming hard?
That thought came to mind while I was reading Johan Den Haan's well stated opinions on Reasons Why Model-Driven Approaches (will) Fail over at Info Q.
Fill in the blank in the following statement:
Most Software Development Obstacles are ______
If you answered (A), then I am intensely jealous :-)
Tom Baeyens, of JBoss jBPM fame, published a great overview of BPM's past and possible future in his article: Process Component Models: The Next Generation In Workflow ? over at InfoQ.
Check it out!
Every so often I come across a blog entry that makes my own attempts to put my thoughts in writing seem pathetically inadequate. Stevey's Blog Rant: Execution in the Kingdom of Nouns is one such entry.
Any tools can be used wrong, and I believe that's the reason many developers hate BPM. They just don't know how the BPM tools should be used... and I'd love to rectify that situation.
It's not too late to Give One and Get One...
A few years ago I posted a short blog entry "The SOA Elevator Speech" to try to distill SOA into talking points that you might be able to cover on one elevator ride. With that posting in mind, here's my attempt at explaining BPM as concisely as I can...