Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@yehaaw but... I thought I posted it under a correct category this time 😔
(yes, mayo is super popular in russia) -
This is a great metaphor also because it fully explains why mayonnaise still isn't objectively bad.
If I ate at a Michelin star restaurant twice a day, I wouldn't want to use mayonnaise, because the chefs are great and so are the ingredients and they can make excellent food that would be ruined with mayo. In reality though, those restaurants are ridiculously expensive, and even if I did have that kind of money I would probably still eat mediocre food made from simple ingredients on most days because there are lots of things that I would prefer to spend the money on. Most meals are simply not worth the cost of a Michelin star chef and top quality ingredients. -
Most situations where you need new software also involve a lot of other costs. The clients (and could-have-been clients) I've had so far could not have paid for a better developer. Writing tests takes up roughly a third of my working hours and pretty much the only bugs that still occur would also occur in idiomatic code because they arise from flawed workflow designs and not incorrect code. Knowing all this, it's hard to imagine that employing someone who doesn't need tests would be cheaper.
-
@TrevorTheRat No, he just likes CSS... like a LOT. Wants everyone to invent their own declarative language for their own domain (like CSS is for web apps), and maintain/update that, instead of using imperative languages and having to test everything constantly.
I think one reason for this line of thinking might be that as far as designing UIs is concerned, automated testing is pretty much a moot point. -
@IntrusionCM homemade mayonnaise is a proper declarative TDD, store mayonnaise is whatever regular people write and call “tests”
-
@hardCoding you’re factually wrong. I don’t want anyone to do anything. I just have a mental model that allows building apps 3x faster and with 5x less bugs. You can use it or you may choose not to, both variants do make me money.
-
@kiki yeah yeah, that's why you are posting insulting rants about "test boys", right? Because you don't care what anyone does, or whatever.
If you like what you are doing and don't care what anyone else is doing, then act like it bro. -
@hardCoding if your life decisions can be influenced by some rando ranting on the internet, I have bad news for you
-
@kiki You still can't accept the fact that I like mayo. It definitely doesn't belong in a Michelin star restaurant, but it's great for eg. salads.
-
@kiki Of course you can cook delicious meals without mayo. The opposite of this statement would be that all delicious food is either expensive or contains mayo, which is ridiculous. But there are some things that work better with it.
-
@kiki I'm not a coverage nut, I write unit tests for very abstract functions that lend themselves to testing.
-
@AlmondSauce Tests for the public interface are called e2e tests. Unit tests are highly dependent on the structure of the program and the emphasis is on granularity so they often (although not always) imply a single implementation and have to be rewritten when the implementation changes to accommodate unrelated changes in functionality.
-
@lbfalvy I'm talking about the public interface of a class, not the interface of a public API or whatever else (which would be an e2e test.) The former you *definitely* test via unit tests. They would only need rewriting if the public contract of that class changes, which should be rarely or never if your application is well designed.
Such immense satisfaction when. You have been telling the other team that the problem is on their end and prov...
Oh yeah, the app does nothing and yet it's still 14mb in size. Like bruh, 'The app does nothing', nothing as i...
The Michelin star chef says to a fast-food line cook:
— In my restaurant, we don't use mayonnaise. Better even, I don't need mayonnaise, so as my fellow Michelin star chefs.
— You are idiot. We use mayonnaise and the burgers taste like crap without it.
— Perhaps it's because your recipes are trash and your products are made from waste materials?
— Look. I consulted with my fellow cooks from KFC, McDonald's, Burger King — all huge, billion-dollar companies, and they too are using mayonnaise. The whole world uses it. If you don't use mayonnaise, you can't cook tasty. End of discussion.
That's how I feel when someone defends unit tests. Matter of fact, I can't stand _both_ tests and mayonnaise. Coincidence?
random
🤔