161–170 of 329 posts
Yeah. I also floss every day, clean up the kitchen as I cook, keep off-site backups of my personal data, call my mother regularly to thank her for raising me, read the terms and conditions to online services, keep an up-to-date to-do list, and change all my passwords once a month.
sure you do
Yeah. I also floss every day, clean up the kitchen as I cook, keep off-site backups of my personal data, call my mother regularly to thank her for raising me, read the terms and conditions to online services, keep an up-to-date to-do list, and change all my passwords once a month.
Yeah and some people are mediocre at their craft.
I give priority to end to end working of the software stack.
I always makes sure there that test suite should be executed in parallel threads.
I make sure that tests are written before I merge my code in the master branch.
Once I am a bit more comfortable with the code and have a better understanding of what I need, I will start writing some tests. I usually don't write too many early on, this way I don't have to go back halfway through development and change all my tests. Only when I'm confident enough with the code do I start writing extensive tests and try to cover all cases.
Earlier quoted context omitted.
To each their own. I have seen many times all the unit tests pass, but the application is broken. It really depends on the situation. There is no silver bullet when it comes to testing.
Yeah that's why "every" open source project you trust has a shitload of unit test. For amateurs, no tests, pros write test always.
Earlier quoted context omitted.
I see you're aiming for the sainthood too. You don't also happen to help elderly women across the road, let everyone else out at a junction and never fail to say 'please' and 'thank-you'?
At the risk of being serious for a moment, saying "please" and "thank you" are two of the lowest effort, highest reward, and plainly decent things you can do as a human.
...some of us "other kind" of people actually consider excessive politeness as offensive because it wastes time and pollutes conversations and after a certain we'll start actually being offensive with people like you, and you'll just stare amazed at how horrible people we can be! When in fact we're just snapping unable to put with more verbal abuse coming in terms of "please" and and "t you" from people like you.
For outright new code (think new objects, new API, and so on), I tend not to write the tests first because they become a cognitive load that affects my early design choices. In other words, I am now writing code to make the tests pass, and have to exert effort not to do that.
Yeah. I also floss every day, clean up the kitchen as I cook, keep off-site backups of my personal data, call my mother regularly to thank her for raising me, read the terms and conditions to online services, keep an up-to-date to-do list, and change all my passwords once a month.
> read the terms and conditions to online services sure you do
Yes. I like BDD, it helps me focus on the goal. I feel that it lets me find the right approach faster. Also, helps avoid distractions and optimizing things too early. Related: „Write tests. Not too many. Mostly integration.”, httsps://kentcdodds.com/blog/write-tests/