• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle






  • After many failed attempts at TDD, I realized/settled on test driven design, which is as simple as making sure what you’re writing can be tested. I don’t see writing the test first as a must, only good to have, but testable code is definitely a must.

    This approach is so much easier and useful in real situations, which is anything more complicated than foo/bar. Most of the time, just asking an engineer how they plan to test it will make all the difference. I don’t have to enforce my preference on anyone. I’m not restricting the team. I’m not creating a knowledge vacuum where only the seniors know how yo code and the juniors feel like they know nothing.

    Just think how you plan to test it, anyone can do that.



  • tvbusy@lemmy.dbzer0.comtoMemes@lemmy.mlfirefox
    link
    fedilink
    arrow-up
    24
    ·
    1 year ago

    I see it the other way around. I have a feeling that FireFox follows the specs while Chromium kind of has its own plan and directly introduce new behavior without much care for standards.

    Since Chromium based browsers have the majority of the market share, you have the feeling that FireFox is awkward/lag behind. Now look back at Opera when they still have their own engine and you will see that while they try to introduce new behaviors just like Chromium, their limited market share means that people don’t feel the need to make use of these “innovations”.