Earlier quoted context omitted.
Oh ouch. That was not the intention but I can be socially awkward at times. Perhaps you can help me understand what I said that was wrong? Happy to adjust the way I communicate so long as I can express that it was writing out code that didn't work as opposed to architecture and/or technical communication.
For me, it has two problems. The tone has this anodyne corporate PR flavor: whiteboarding isn’t really collaborative (“our”), nor is it an “experience” in the way that, say, hang-gliding is. It’s also not particularly actionable. Obviously, it implies that you need to brush up on either a) algorithms, b) coding, or c) investigating a problem. However, you could just come out and say that. Some specific feedback on th…
But point taken and I’ll bias back in that direction. Without any irony, thanks for the feedback ;)