cows_are_underrated

joined 1 year ago
[–] cows_are_underrated@feddit.org 2 points 11 hours ago

I may not be able to talk about Linux for a solid two hours, but I can definitely talk for two hours about my music taste, communism or warframe depending on what they want to hear the least.

[–] cows_are_underrated@feddit.org 5 points 13 hours ago

Testing means, that you dont trust your coding abilities. Dont be a pussy and dont test your code /s

[–] cows_are_underrated@feddit.org 1 points 15 hours ago

From what I understand the difference between how I code and what has Ben described as TDD in this thread is, that I set up everything first and then try to think of ways people could break the code and then test these vases/try to prevent them.

[–] cows_are_underrated@feddit.org 1 points 23 hours ago

I usually do it thenother way around

That one is always nice when you actually do the cleanup and then have much less files to care about.

[–] cows_are_underrated@feddit.org 2 points 1 day ago (2 children)

Yeah of course I Am testing. I Am usually just not writing very extensive tests. I try to break it as much as possible with as little effort and try then to prevent it from breaking.

[–] cows_are_underrated@feddit.org 0 points 1 day ago (4 children)

Ah thanks. That sounds like not that bad of an idea, but for the scale that my projects are at thus is quite an overkill. I usually try if it works in The best case sz scenario and then try to deliberately break it by calling certain functions with garbage as parameters.

[–] cows_are_underrated@feddit.org 0 points 1 day ago (6 children)
 

Its definitely a bad idea writing new code that builds up on your old code, that has not been tested properly, because you quickly have to start debugging multiple layer is code at once.