Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

The Unspoken Truth About Why Your IT Sucks

Lucas123 (935744) writes | more than 4 years ago


Lucas123 (935744) writes "If you expect IT to be used to reduce costs, increase capability and reduce work load, then along with the technology you need competence to advanced knowledge of possibilities, the creativity to derive or invent solutions with that knowledge, and the (un)common sense to assess the implications of such solutions. As Computerworld columnist Jeff Ello so eloquently puts it, 'Technology is unable to produce intelligent results without intelligent direction, a truism encapsulated in the formerly popular computer acronym GIGO, 'garbage in, garbage out.' Everyone claims to value competence. And yet your IT still — for lack of a better term — sucks. It's just that simple. What goes unspoken, or at least unheard, is that the way the typical organization positions and utilizes its IT resources sucks.'"
Link to Original Source

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

An IT department that sucks (1)

Orion Blastar (457579) | more than 4 years ago | (#30293116)

has more than just IT people who aren't competent, they also have managers who did the employee screening and hiring who are incompetent for hiring incompetent IT workers.

Seriously in the USA before the Dotcom bubble bursted, Quality was the first priority, but after the Dotcom bubble burst most IT departments and business management went for "Good Enough" quality in that so long as it compiles with no errors (even if it has compile warnings ship it) it gets shipped. The Dotcom companies failed due to incompetence in computer programming and management being incompetent and really really bad (not evil bad, but miserable failure bad). The colleges then after the Dotcom bust turned out mediocre IT and Comp Sci graduates, and programming languages had to be "dumbed down" to include garbage collection, memory management, error trapping, elimination of pointers for Java and C# and Visual BASIC.Net. Why? because the new graduates didn't know how to do them, and the high quality programmers did know how to do them but wanted six figures in pay while the "good enough" codemonkey programmers took $25K/year salaries to write awful code that works good enough but crashes the system and servers twelve times a day. Follow that up with sucky help desk, sucky QA, sucky managers, sucky supervisors, etc that do "good enough" work instead of high quality work, and you got an IT Department that sucks.

Want a better IT department, first fire the managers and then hire competent ones, and then fire the IT staff and let the competent managers pick the competent IT staff.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>