@liamvhogan software development does have collaborative practices like pair programming and code review which would relate more to working with an editor
Posts
-
‘Explain it to a rubber duck’, is a piece of advice that I understand computer people use to break down complex problems, which is a cargo-cult version of a writer working with an editor, who unlike the duck, can respond and give good advice -
‘Explain it to a rubber duck’, is a piece of advice that I understand computer people use to break down complex problems, which is a cargo-cult version of a writer working with an editor, who unlike the duck, can respond and give good advice@liamvhogan that's explicitly not what rubber-ducking is, though. the origin was a (possibly apocryphal) team where colleagues would interrupt you at your desk to ask for help and spend five minutes explaining why they're stuck, and in the course of framing an explanation they see how to proceed and leave without requiring any response. someone figured it'd be cheaper to recruit a golden retriever who can listen patiently and not respond for a much lower hourly rate. from there they iterated to rubber ducks
so the whole point is you're solving a problem by framing it as a question or explanation and not requiring anyone else's input
-
I tell manufacturers that I will review *anything* with a USB-C port.@Edent does the USB-C port have to be connected to anything