Enterprise Software Predictions 2014

  1. "Good Managers Are Able To Manage Everything" attitude will be still taken seriously in the IT.
  2. Companies will still try (but fail) to save money on developer's hardware (RAM, CPU, storage space).
  3. There will be still attempts to build complex business software cheaply with outsourcing.
  4. Waterfall decorated with agile vocabulary is going to be the development process of the year.
  5. Non-coding architects will still aim to simplify developer's live by sharing their wisdom on slides.
  6. We will get even more languages running on the JVM, what will significantly increase the productivity :-).
  7. Empty layers and extensive, not tested, mappers are still going to be the most popular "pattern".
  8. Software metrics and plain numbers will outweigh common sense.
  9. Small and productive corporate developer teams are going to be further reduced in favor of external consultants--for cost reduction.
  10. ...and small, reasonable, focussed and motivated teams and companies will be order of magnitude more productive and cost effective, than any other dogma-driven competition.

See you at Java EE Workshops at MUC Airport or on demand and in a location very near you: airhacks.io!


this is so true :-)

Posted by leonardo kenji shikida on January 22, 2014 at 10:33 AM CET #

I 100% agree with every single one of these 10 points. Well spoken.

Posted by So true on January 22, 2014 at 02:43 PM CET #

No Kidding. I think Adam is spot on.

Posted by on January 22, 2014 at 06:25 PM CET #

So right, most of them, but 9. I am external. And being productive is not a question of being external or internal. And if - then 9. is wrong in may case.

Posted by on January 24, 2014 at 02:31 PM CET #


I'm also an external developer and never was internal.

I made the following observation: internal developers stick longer with a
company and therefore have more domain knowledge per definition.

In my opinion a solid domain knowledge is far more important for productivity,
than any technical skills.

Therefore internal developers will always be more productive, than external

There are always exceptions from the rule like e.g. external developers
spending years in a single project...

I hope you can agree with the points made here,

thanks for your comment!,


Posted by Adam Bien on January 27, 2014 at 03:11 PM CET #

well spoken and hilarious. :)

I also have some comments regarding #9.
Internal and external teams, separately or together, can be both very unproductive. Management can be really productive at keeping internal teams away from technical skills while keeping external teams away from domain knowledge. In my view both technical and domain knowledge are equally important, the lack of any of them leads to disaster.
So while I don't necessarily agree with the internal vs. external comparison, I strongly agree with the need for smaller, more focused, organized, and transparent teams.

I'd also add #11 (or rather #0) with something like "Companies/management will still strongly believe, and find whatever false explanation (e.g. deadlines) to, that they can make progress and even succeed without actual domain / business process / requirement analysis and technical design."

Keep up the great work.
Cheers ;)

Posted by Patrik Varga on January 30, 2014 at 10:31 AM CET #

juts to follow other comments

Posted by ali on April 26, 2014 at 07:04 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments