The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Thursday: 12:00PM - Team building luncheon. Meal and drinks provided by company. EVERYBODY requi.....
Friday: 7:00AM - "What can we do to improve productivity meeting?" All...
Friday: 1:00PM - Emergency meeting to determine who will be working this weekend to catch up. All......
Friday: 3:00PM - "So-and-so's going away party." Must attend!
I might be exaggerating a touch, but some days I spent as much as 7-8 hours in meetings which had little or no bearing on my assignment. Typical week averaged about 20-25 hours in meetings, usually during prime productive time.
Their idea was that "inclusion" was important and "everybody's ideas" were welcome (but they didn't really want to hear them.)
Could be worse. Meetings halt progress but don't bear anti-progress. Doing something exactly the way the customer (in my case, the product management department in the same company) wants only to find that I have to redo the whole backend because they didn't tell me of a "tiny" feature they totally need in advance, that's anti-progress. I'd rather sit in countless useless meetings than either create a patchwork solution I don't understand myself or redo the thing from scratch time upon time.
I take it upon myself to ask those detailed questions up front - and keep asking them until I get an answer in writing. Then I at least have CYA'd myself. It also helps if the developer knows the industry really well, because then you can tell the customer that they didn't think of this feature or that consequence. I understand that not all developers have the luxury of being experts in some random other field, but it does help.
Keep all things a simple as possible, but no simpler. -said someone, somewhere
Hey, thanks, you actually help me feeling better about this nonsense, I'm not a lone! Did you also have situations where you get a "spec" which is a prosaic description of what they want to be able to do, reply with a stiff spec of what you're going to build, they say "Yup, that's exactly what I want", you build it and back comes "but I can't do X" with X being explicitly forbidden by the spec they agreed to?
Last Visit: 5-Dec-19 11:52 Last Update: 5-Dec-19 11:52