I was told to write my idea into an article to share internally with engineers. Then someone internally reached out to post it on our company tech blog. Then it got published on the tech blog. So I guess that’s something?
Comment on Things to say when you're losing a technical argument
SpaceNoodle@lemmy.world 11 months ago
I like your idea. Why don’t you write up a white paper and we’ll review it at the next staff meeting?
I think I might have said this verbatim
idunnololz@lemmy.world 11 months ago
xmunk@sh.itjust.works 11 months ago
That one feels too cruel. If you said that to some junior dev they’d likely do it… and probably in their free time.
That said with fellow senior devs if someone suggests something completely off the wall I will occasionally respond with, essentially, prove it first.
Carighan@lemmy.world 11 months ago
“It’s* better** to do things*** by this approach.”
Always throw a spanner in their legs with:
*: Who exactly?
**: [citation needed]
***: Please specify exact use cases
SpaceNoodle@lemmy.world 11 months ago
It’s more Pythonic.
Socsa@sh.itjust.works 11 months ago
With a senior engineer it’s perfectly reasonable to just say “ok, implement it and let me know how it works.”
Like the whole point is that they should be relatively independent and capable of taking ideas from paper to product.