Skip to main content

Worthless Practices (IBM's list)

I just saw via InfoQ that IBM maintains a list of Java EE best practices.

Now I've never really been good with bile, but there is just so many things wrong with this list on so many levels. Just listen to the title: "IBM WebSphere Developer Technical Journal: The top Java EE best practices". A bit of paradoxial, isn't it?

Let's take a quick look through the list and comment on each point:

1. Always use MVC.
Yeah, right. Always use MVC. Remember to design a rigid 3-tier architecture upfront no matter what sort of application you are going to build. Use Struts, right? Right.

2. Don't reinvent the wheel.
Well, duh. Struts, right? Right.
3. Apply automated unit tests and test harnesses at every layer.
I'd actually support this one if I could append "if possible".

4. Develop to the specifications, not the application server.
Well that certainly was a good tooting from the wrong horn, coming from the deranged nit-wits that gave us WSAS and WSAD.

5. Plan for using Java EE security from Day One.
Yes, and build it into your whole application using WebSphere Application Server's Java EE security(tm). There is no better way to tie yourself to your application server than using the embedded access control and security mechanisms.

6. Build what you know.
Well, duh. Struts, right? Right.

7. Always use session facades whenever you use EJB components.
How bout never using EJB components?

8. Use stateless session beans instead of stateful session beans.
Sounds a lot like Struts action thinking to me. Drink you own poison any way you like, EJB suckers.

9. Use container-managed transactions.
Uh. Yeah, using WSAS Transcation Management(tm)!

10. Prefer JSPs as your first choice of presentation technology.
Indeed! Never mind that JSPs is the most designer and developer unfriendly templating language around. I love having to compile my templates into servlets, then loading them into the application server!

11. When using HttpSessions, store only as much state as you need for the current business transaction and no more.
No kidding. I'll try to remember that session actually uses memory somewhere.

12. Take advantage of application server features that do not require your code to be modified.
Wait, isn't this the same as point 4? Except that it binds you to the functionality of an application server and thereby invalidates the point.

13. Play nice within existing environments.
I guess this means that we should use WSAS. Period.

14. Embrace the qualities of service provided by the application server environment.
Really, how much more of this list is going to be about WSAS ball-licking?

15. Embrace Java EE, don't fake it.
And buy our fully Java EE compatible application server today! Seriously, tell this to the thousands of developers who have uneccesarily suffered under EJB's.

16. Plan for version updates.
Yes, there will always come a patch for your WSAS installation. Usually the one that fixes the bug in WSAS which is paining your development. And the techies will tell you they can't install the patch before 6 months.

17. At all points of interest in your code, log your program state using a standard loggingframework.
Yeah.. WSAS logging is just lovely to look at and modify.

18. Always clean up after yourself.
Now this is the point where I really start getting annoyed. How bout you guys cleaning up after yourself? Your company is largely responsible for soddling the development of Java EE into the state it is today!

19. Follow rigorous procedures for development and testing.
Yes, develop and test as rigorously as the application server and the web framework forces you to. Make sure you have a 100 page testing plan that lines up the procedures.



Summary: Buy IBM, use WSAS and use Struts.

Bile being done, the text actually has some good principles and points, but the concrete solutions so provided are a bit too much 2002 for my taste.

Comments

  1. Haha, I love the post Thomas!

    I could not agree more on that IBM really want you to be application server dependent. We also have problems with WSAS and RAD. RAD being IBM Rational Application Developer, where they have an old version of eclipse which they have ruined with a lot of wizards and clodding it up with WSAS integration. It is really a pain to not being able to generate code that you can trust.. We even have to fix generated code after we deploy.. This so a call to DB2 do not fail..

    We would maybe keep using WSAS if we had got any feedback and information from IBM, but as the reality is different we are migrating to JBoss instead.

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit