There is this thing in Psychology called Absence Bias, where events that are not happening, are not recalled. Hence they seem to have probability zero in hindsight. If the product is free of bugs, you might think there weren’t any, to begin with, or there won’t be any bugs in near future, and you would be wrong.
Though I was never a big fan until now, I have taken a lot of interest in Dilbert recently. Maybe it has to do with my transition into the working world from the university. Anyway. Scott Adams, the creator of Dilbert shows how he creates Dilbert, and it’s quite amusing.
This is the summary of the second chapter from “The Pragmatic Programmer”, which dives into the design philosophy of a pragmatic programmer. For the rest of the chapters, see this post.
This is the summary of the first chapter from “The Pragmatic Programmer”, which dives into the philosophy of a pragmatic programmer. For the rest of the chapters, see this post.
In a traditional client-server programming paradigm, request-response model is pretty common. Whenever client needs resource, it sends a request to the server. Server responds a response with the requested resource to the client. However, this assumes that the client is always the initiator. What if the server has some data to send to the client?