• 1 Post
  • 32 Comments
Joined 2 years ago
cake
Cake day: January 6th, 2024

help-circle
  • There are two different things mentioned here, which I feel I need to clarify:

    First, what you said about merging / creating a PR with broken tests. Absolutely you shouldn’t do that, because you should only merge once the feature is finished. If a test doesn’t work, then either it’s testing for the wrong aspect and should be rewritten, or the functionality doesn’t work 100% yet, so the feature isn’t ready to get merged. Even if you’re waiting for some other feature to get ready, because you need to integrate it or something, you’re still waiting, so the feature isn’t ready.

    At the same time, the OP’s point about tests being supposed to fail at first isn’t too far off the mark either, because that’s precisely how TDD works. If you’re applying that philosophy (which I personally condone), then that’s exactly what you do: Write the test first, checking for expected behaviour (which is taken from the specification), which will obviously fail, and only then write the code implementing that behaviour.

    But, even then, that failing test should be contained to e.g. the feature branch you’re working on, never going in a PR while it’s still failing.

    Once that feature has been merged, then yes, the test should never fail again, because that indicates a new change having sabotaged some area of that feature. Even if the new feature is considered “essential” or “high priority” while the old feature is not, ignoring the failure is one of the easiest ways to build up technical debt, so you should damn well fix that now.







  • Kayana@ttrpg.networkto196@lemmy.blahaj.zoneFreADoM
    link
    fedilink
    arrow-up
    2
    ·
    6 months ago

    Mine’s a bit closer to your proportions, although I’m not sure if Google can accurately predict the effects climbing a steep hill up and down will have on cycling and walking. The weird thing is the public transport. It must not know about all available lines, because that should be more like 90 minutes.








  • Kayana@ttrpg.networktoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    1
    ·
    11 months ago

    Because you don’t need to have significant experience or rent a VPS in order to do that, and I can respect that. We don’t need to force FOSS developers to become proficient in everything.

    What needs to happen is some kind of tool (ideally FOSS) that lets you spin up an actual forum with the same difficulty to set it up as Discord.



  • Huh, TIL.

    Regarding your edit, that amount wasn’t the cumulated cost of whatever Limewire were distributing, that would be idiotic indeed; rather the RIAA tried to call for a ruling that somehow those guys were causing $150,000 in damages - per instance. Now the article unfortunately doesn’t state how they possibly tried to justify that number, and I can’t be bothered to research that myself. Another thing that would interest me is how the plaintiff expected them to pay with almost every dollar on Earth.

    So while I don’t think this had anything to do with “lost sales”, I do agree with the possible fines and damage calculations not being fit for any sort of realistic purpose at all.





  • Kayana@ttrpg.networktoich_iel@feddit.deich_iel
    link
    fedilink
    Deutsch
    arrow-up
    5
    ·
    edit-2
    1 year ago

    Mein Straßenverkehrsamt tendiert dazu, bei Leuten mit nur einem Namen in ihrem (bspw. indischen) Pass einfach den Namen als Vor- und Nachnamen zu nehmen, sodass bei ihnen dann <Name> <Name> auf dem Führerschein steht… Nur, weil die deutsche Bürokratie nicht mit nur einem Namen klarkommt.