|
|
A reflection on the importance of asking the suitable questions in software program growth. Everybody laughed. I felt disgrace. But I also didn’t get an answer from my mocking peers as a result of they couldn’t understand it either, however didn’t want to accept it. Today, years later, I understand why but don’t totally grasp it. I’m not a biologist or anything related. What my instructor said to me and the group after I asked that query is what I remembered a minute in the past: "There aren't any silly questions, only stupid people who don't ask." And she proceeded to elucidate why. I like to ask questions before and after implementing a function to make them complete and avoid having to implement these when something goes improper. So let’s discuss that. How asking questions and documenting them can make your function complete. And sure, I simply tied a private story to an engineering article on how the thought of asking questions can be transposed throughout multiple areas of a characteristic implementation.
Here is my blog post :: BloodVitals device |
|
發表於