Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment reminds me of a true story (Score 1) 551

Once upon a time, there was a project that had been underway for 19 months, but had not yet delivered anything to the users. Management was concerned, and was considering drastic measures such as pulling the plug and starting over with a new project team. At this point, management brought in a trusted developer I'll call DT to help analyze the project's status.

After a series of meetings with different project team members, DT gained an understanding that some software components had already been developed and tested, and it should be possible for the team to deliver a workable system within a few months. Seeing this, management relented and decided to give the project team a bit more time to deliver something.

A few weeks later, at a weekly meeting, one of the team members mentioned they were considering using message queues, but he was leaning against using them. In agreement, DT said that using message queues to handle communications between components of the app looked like overengineering. At this point, a developer sitting across the table went ballistic and started spouting semi-comprehensible technobabble about why message queues were needed and how, at a previous workplace, nobody ever would have said this was overengineering.

To be continued?

Perhaps DT's criticism of the message queue approach makes him a duct tape developer in this case.

Slashdot Top Deals

The hardest part of climbing the ladder of success is getting through the crowd at the bottom.

Working...