ltlian183616dOne of my worst habits I have trouble shaking is looking them in the eye and going "Yeah, I know" for that stuff.
This isn't useful information to us. What's your point.
I feel like there's a place for that stuff, just maybe not when they did it to you ;)
I worked at a place where product development team really hated any feedback ... no matter how it occurred.
Then they'd put out some stuff that only they understood it got to the point where and customers and everyone were all 'wtf does this even do?' because that team had walled themselves off in clown world where they had no idea what was going on...
PaperTrail751516d> When new employees start shouting out suggestions of what feature we should do
My favorites are "If they had designed the app correctly the first time .." or "This is so stupid, they should have used <insert technology that did not exist when app was written>"
My response is usually "Look who just volunteered to fix that code. Thank you."
Amazingly, those individuals either stopped making those comments (at least in front of me) or stepped up and made the changes. Rarely did anyone step up and fix the code.
"It's easier to curse the darkness than it is to change the light bulb."
linuxxx15388316dThe stupid stuff I agree with but suggestions/opinions... why not? I'm a relatively new junior (cybersecurity) and everyone is encouraged to give opinions and suggestions about anything.
> Holy cow, at that point it is time for:
Yea, one dev from an Oracle shop made the mistake..
Paul: "If you were using Oracle, you wouldn't have that problem."
Mark: "We're not using Oracle and we're never going to use Oracle. How would using Oracle fix this?"
Paul: "Um..uh..um...Oracle supports multiple triggers on tables"
Mark: "How does that work?"
Paul: "I don't know, I'm not a DBA. That's how we made it work at my last job."
Mark: "Dude, shut the fuck up. I never, ever want to hear Oracle come out of your pie hole."
Yes, it got very hostile at times. Those two never got along and offered me great entertainment. No 'baseball bat' entertainment, but fascinating presentations of multiple "alpha male"s in the work place.
@PaperTrail That's horrible.
Like things get wonky sometimes and on occasion there are legitimate bad choices.
But I find when things are wonky it's more often about the history of something than just one "hey if you just used X" kinda situation.
Go back in time and insert X and maybe that problem is or isn't still there ... but maybe not. Who knows.
Then there are the situations like:
"OMG why is it this way? This looks like some ad hoc recipe saving app!?!? We're in accounting."
"Well that's because the company started with a recipe saving app..."
"Oh ... well then ... makes sense."
Had a tech lead who was always in design meetings giving his yay or nay to whatever design came by. Never thought much of it at the time but afterwards I realized he's not a designer. The designers have trained for years to do what they do, so why is he the judge/jury/executioner when it comes to design?
vortex487516d@justamuslimguy experienced both cases, where tech lead makes product and design decisions, and when designer makes design, and product makes product decisoins and the tech lead becomes their little puppy with no control over the technological aspect, doing idiotic stuff, cuz thats what the product wants.. and product isnt aware of implications of his requests, not aware of making a plan for architecture of big features.. just do this.. then that.. designer doesn't understand that u make a theme and then reuse it.. just invents new buttons every 2 weeks for fun.. and the code is a fucking disaster.
IMO, a tech lead should make the final decisions on the sub components that together make up the whole solution.
HOWEVER, the tech lead should have the experience and understanding, of all the fields he takes charge over.
I dont expect designer or product to know how code works, (i Wish!).. i do however expect a GOOD tech leads to understand some basic ui/ux best practices.
vortex487516d@N00bPancakes yeah i know what u mean, there is a place for honest feedback, also fresh eyes are always good. But this was not even said to me, just next to me.. like u know how it is, dev team busts their ass, grinding everyday for years, sprint after sprint.. then some fresh boi with 2 days in the business starts telling during lunch time how this and that is wrong and all the great ideas he has, makes the devs look bad, i find it very disrespectful. If that page is so slow, it might be because this code is old legacy that we need to deal with everyday and cant get rid of.. like we know its slow.. if we didnt implement that "brilliant feature", it's not cause we are stupid, it's cause there are priorities and we implemented 100000 other features in the meantime..
Aghh.. at least i can let it out here
Yeah that's a ... bad choice as far as the dev goes.
It always amazes me how many folks who are devs, who you would think bust their ass on things and get flippant / crappy feedback .... are happy to do it to other devs.
Like bro why you do that to your own kind!?!?! (⊙︿⊙)
Demolishun792316dI wonder if this is how some app developers view comments on their products.
There is a big difference between "this feature would be cool/better" and "you people don't know what you are doing". I kinda gather it comes across as the latter.
vintprox109015d@linuxxx kudos for notice!
Genuinely accepting feedback is a part of any successful campaign. When product department goes all black and barricaded, it's worthless! @vortex