agilob to [email protected]English • 7 months agoThings to say when you're losing a technical argumentweb.archive.orgmessage-square23fedilinkarrow-up1136arrow-down13
arrow-up1133arrow-down1external-linkThings to say when you're losing a technical argumentweb.archive.orgagilob to [email protected]English • 7 months agomessage-square23fedilink
minus-square@xmunklink24•7 months agoThat 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.
minus-squareCarighan Maconarlinkfedilink14•edit-27 months ago“It’s* better** to do things*** by this approach.” Always throw a spanner in there with: *: [citation needed] **: According to who exactly? ***: Please specify exact use cases
minus-square@Socsalink3•7 months agoWith 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.
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.
“It’s* better** to do things*** by this approach.”
Always throw a spanner in there with:
*: [citation needed]
**: According to who exactly?
***: Please specify exact use cases
It’s more Pythonic.
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.