• 0 Posts
  • 41 Comments
Joined 11 months ago
cake
Cake day: August 18th, 2023

help-circle

  • efstajas@lemmy.worldtoProgrammer Humor@programming.devCoomitter be like
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Honestly, I’ve worked with a few teams that use conventional commits, some even enforcing it through CI, and I don’t think I’ve ever thought “damn, I’m glad we’re doing this”. Granted, all the teams I’ve been on were working on user facing products with rolling release where main always = prod, and there was zero need for auto-generating changelogs, or analyzing the git history in any way. In my experience, trying to roughly follow 1 feature / change per PR and then just squash-merging PRs to main is really just … totally fine, if that’s what you’re doing.

    I guess what I’m trying to say is that while conv commits are neat and all, the overhead really isn’t really always worth it. If you’re developing an SDK or OSS package and you need changelogs, sure. Other than that, really, what’s the point?



  • So you’re talking about SaaS / business tooling then? Again though, that’s just one of many segments of software, which was my point.

    Also, even in that market it’s just not true to say that there’s no incentive for it to work well. If some new business tool gets deployed and the workforce has problems with it to the point of measurable inefficiency, of course that can lead to a different tool being chosen. It’s even pretty common practice for large companies to reach out to previous users of a given product through consultancy networks or whatever to assess viability before committing to anything.





  • There’s no reason your clients can’t have public, world routeable IPs as well as security.

    There are a lot of valid reasons, other than security, for why you wouldn’t want that though. You don’t necessarily want to allow any client’s activity to be traceable on an individual level, nor do you want to allow people to do things like count the number of clients at a particular location. Information like that is just unnecessary to expose, even if hiding it doesn’t make anything more secure per se.




  • efstajas@lemmy.worldtoLinux@lemmy.ml“Systemd is the future”
    link
    fedilink
    arrow-up
    24
    arrow-down
    2
    ·
    edit-2
    10 days ago

    Oof, that quote is the exact brand of nerd bullshit that makes my blood boil. “Sure, it may be horribly designed, complicated, hard to understand, unnecessarily dangerous and / or extremely misleading, but you have nOT rEAd ThE dOCUmeNtATiON, therefore it’s your fault and I’m immune to your criticism”. Except this instance is even worse than that, because the documentation for that command sounds just as innocent as the command itself. But I guess obviously something called “tmpfiles” is responsible for your home folder, how couldn’t you know that?


  • That happens literally every night though and wind also doesn’t blow 100% of the time.

    Very true, but the fact that wind blows often and there’s also varying amounts of direct sunlight during the day already massively decreases the amount of storage required for a grid. You don’t need the capacity to cover 100% of energy usage, sustained, like you suggested earlier. Especially as grids become (geographically) larger and smarter — we need wind and sun somewhere to cover energy needed elsewhere — it doesn’t have to be localized. Plus solar output obviously peaks during the day, when demand is also highest.

    Renewables make up a trivial* amount

    The percentage is absolutely not trivial today. Especially considering there are multiple large grids today that can easily sustain 50%+ renewable energy over sustained periods. And 30% by 2030 is a lot, though of course it could be a lot better.

    and as we phase out fossil fuels, the requirement for energy storage is going up drastically.

    Yes, no-one is arguing otherwise.