3 ms·

-- me: sits through yet another mandatory hours-long meeting where the loudest two developers one-up each other to find the best hypothetical solution to the mo

-- me: sits through yet another mandatory hours-long meeting where the loudest two developers one-up each other to find the best hypothetical solution to the most convoluted problem they can imagine as it relates to the urgent, critical problem we currently face whose simple, plain solution goes entirely ignored and where no decision is made. -- I have trouble laughing at what I know is supposed to be humor, because of how tragically true this is and how much this affects me on a regular basis. But I don't work for a startup! I thought it was supposed to be different in that world. Perhaps some problems are just universal.

iolothebard 11y ago
It's amazing how many of these apply to the company I just quit. I emailed it to their lead developer. Hilarious and depressing at the same time.
ratsmack 11y ago
How about the meeting where the non-problems and false concerns are beaten like a dead horse by people without the knowledge or skill to be in the discussion. But you have to just sit there with your face in your palm because if you say anything to try and correct the misdirection, you will be considered not a "team player".
- ryanmarsh 11y ago
  This is the default for Fortune 500 work. Case in point, grossly expensive COTS implemtation requiring 80 consultants to build ETL pipeline to handle roughly 5,000-10,000 transactions A DAY simple XML files to DB rows. Told client a few smart devs could build this in a few months. Got the ಠ_ಠ
  - deleted 11y ago
    [deleted]
- supjeff 11y ago
  If you're not the leader, you're waiting quietly for the leader to take action, but more often than not, the leader is enthralled by the exhilarating debate taking place before them. A non-technical leader takes it as an opportunity to learn, which is a great attitude to have, but the rest of us are dying. Other times they know they need to get things back on track, but they don't know how to stop the runaway train that is a developer ruminating on something that gets more convoluted with each syllable.

iolothebard 11y ago

It's amazing how many of these apply to the company I just quit. I emailed it to their lead developer. Hilarious and depressing at the same time.

ratsmack 11y ago

How about the meeting where the non-problems and false concerns are beaten like a dead horse by people without the knowledge or skill to be in the discussion. But you have to just sit there with your face in your palm because if you say anything to try and correct the misdirection, you will be considered not a "team player".

ryanmarsh 11y ago
This is the default for Fortune 500 work. Case in point, grossly expensive COTS implemtation requiring 80 consultants to build ETL pipeline to handle roughly 5,000-10,000 transactions A DAY simple XML files to DB rows. Told client a few smart devs could build this in a few months. Got the ಠ_ಠ
- deleted 11y ago
  [deleted]
supjeff 11y ago
If you're not the leader, you're waiting quietly for the leader to take action, but more often than not, the leader is enthralled by the exhilarating debate taking place before them. A non-technical leader takes it as an opportunity to learn, which is a great attitude to have, but the rest of us are dying. Other times they know they need to get things back on track, but they don't know how to stop the runaway train that is a developer ruminating on something that gets more convoluted with each syllable.