|
Sundance Kid wrote: But salaried employee I can't make more $$ out of this.
Ok.
Sundance Kid wrote: Just more stress..
Why? Do it as it suits you best and have a good laugh at them when they come crying. Rinse and repeat until they finally learn it.
You are doing something wrong if you let them stress you. Just handwave the results back to them and let them stress themselves.
Always be careful what you ask for. You might get it. 
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Quote: when they come crying
I agree, but they usually blame the delivery team(s). It's a weird scenario here.
But long story short our Sol Arch helped business for years (as a dev). He is not deving anymore, but now business expects all of us to keep "helping" aka doing their work as the SA did for years.
The SA actually almost "run" the business. Now business is clueless...
I don't stress anymore about this. Used to... but not
|
|
|
|
|
Sundance Kid wrote: Now business is clueless...
A constant of nature, obviously.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Sundance Kid wrote: Business can't decide.
In my experience it is usually less that the business can't decide and more that the business doesn't know. They think they want the program to do what they call "X" but in reality it is more "Y".
The job of a good BA/BRM/PM/etc. is figuring out what "Y" actually is.
Sundance Kid wrote: then they change their minds.
This is what I hate about 'agile' development. The business side tries to use it as an excuse to not think out their actual requirements.
Sundance Kid wrote: they give 1 liner specs
Your BA/BRM/PM/etc. is failing the development team. This should not be an acceptable response to any spec request. As far as pet peeves, this goes right up on there with "Doesn't work" for details in a bug report.
|
|
|
|
|
Quote: The job of a good BA/BRM/PM/etc. is figuring out what "Y" actually is.
That is the problem here.. not good BA/Product Owners etc. 
|
|
|
|
|
Well, you could have the alternative. No BA and the developer is expected to work directly with the customers and product owners to perform all of the BA/PM/Architect/Designer/Dev/Tester roles.
On the plus side, it has really rounded out my skill set and expanded my options in the job market.
The bad part is that I don't officially have any of those those titles so HR types don't care what I actually know.
|
|
|
|
|
If I had to work directly with customers I would run away... far far away.
This is too much work for 1 person/dev. You would never deliver anything. And we have many customers (> 10 on 1 "product").
|
|
|
|
|
Spot on - I've suffered through too many one-liner "specs", along with CXO's and senior management changing their minds more often in a day then they change their underwear in a month.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."
-- Marcus Brigstocke, British Comedian
|
|
|
|
|
There are apps for anything, and they are all invariably useless except for a handful of them, which are ugly. I prefer working in other fields.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
"All of the above" 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
