• 0 Posts
  • 27 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.networktoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    35
    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.






  • But you just completely ignored everything I said in that comment.

    Mathematically, that is precisely how O notation works, only (as I’ve mentioned) we don’t use it like that to get meaningful results. Plus, when looking at time, we can actually use O notation like normal, since computers can indeed calculate something for infinity.

    Still, you’re wrong saying that isn’t how it works in general, which is really easy to see if you look at the actual definition of O(g(n)).

    Oh, and your computer crashing is a thing that could happen, sure, but that actually isn’t taken into account for runtime analysis, because it only happens with a certain chance. If it would happen after precisely three days every time, then you’d be correct and all algorithms would indeed have an upper bound for time too. However it doesn’t, so we can’t define that upper bound as there will always be calculations breaking it.



  • That’s a point I didn’t actually think about, touché. Let’s go through this then:

    Before Covid (in my country at least), there was this massive push for more homes, because the interest rates were so low. Everyone was building a house, because it was so very cheap (in interest at least, not necessarily in costs). At that point, wise developers might have decided to not take on any big new projects, focusing on finishing their current ones instead of trying to ride out this bubble.

    Then Covid hit and the supply chains broke down. That was sudden and couldn’t be expected, I’ll give you that. But now, four years later, the main reason (in my opinion) for the low occupancy is the newfound interest for WFH, also resulting from Covid. Who needs an expensive condo in a crowded city if you can have a cheap flat in a small town instead?

    So in this case, I’ll (partially) retract my prior opinion and instead state that while a crash could’ve been seen somewhere on the horizon, Covid with all its consequences certainly couldn’t have been foreseen.

    I’m not familiar with the housing prices in Toronto compared to smaller cities in Canada, but perhaps those developers need to bite the bullet and lower their asking prices, because I’d imagine selling for less is still better than holding onto dead weight, praying for demand to go up again.