jonathanvmv8f
Inside Job.
I didn’t really watch shows on Netflix and I couldn’t care less about people complaining about their shows being cancelled left and right. But Inside Job was recommended by my friend and I loved it. After finding out it was cancelled after 2 seasons, I finally understood the pain these people were feeling all along…
BTW it’s cake day for what was supposed to be a throwaway account
By the looks of the image, you opened this post on your laptop, opened the camera app of your phone, took a screenshot of the app and took ANOTHER screenshot of the app along with the preview of the previously taken screenshot and finally posted it.
I guess it’s your first day too
Asking as a newbie programmer: how do you suggest we write comments that explain the ‘why’ part of the code? I understand writing comments explaining the ‘what’ part makes them redundant, but I feel like writing it the former way isn’t adding much help either. I mean, if I created code for a clock, is writing “It helps tell what time it is” better than writing “It is a clock” ?
It would really help if someone could give a code snippet that clearly demonstrates how commenting the ‘correct’ way is clearly better than the way we are used to.
Been in this situation countless times. Everytime this happens I promise myself I will be grateful and enjoy the ability to breathe through both of my nostrils once it happens and yet I forget about it the next day
I like to think that he forgets, keeps trying and then makes a new post about it
