Feedback as a Service

Photo by Possessed Photography on Unsplash
Photo by Brett Jordan on Unsplash
  1. the client sends the SYN message to the server;
  2. the server replies to the client with the SYN+ACK message;
  3. the client replies with an ACK message.
  • developer A: “hey, I’ve developed this piece of code [pointing to the screen], check it out later in the repo
  • developer B: “ok, later I will have a look
  • there are no details;
  • there is no feedback (just a passive reply).
  • developer A: “hey, I have developed the feature [insert here details about the completed task] and I’ve just pushed it into the branch [specify the branch name] of the repo [specify the repo name]. When can you have a look at it?”;
  • developer B: “Fab! I’m working on my last two daily tasks, I’ll read your code as soon as I finish them”;
  • developer A: “Thank you, could you please give me a feedback about [insert here something specific] of my code?”;
  • developer B: “Sure, I’m writing here on my notes the details so that I do not forget!”.
  • developer A has given a lot of details, forcing developer B to consider the request as important (so important that it’s necessary to write down the details…);
  • developer A is asking for a specific feedback, so developer B now has a moral duty (give back something valuable to developer A).
Photo by Wes Hicks on Unsplash

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store