• 0 Posts
  • 28 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
    5 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.







  • I see this point a lot and I don’t get it at all. You can do something awesome, free and open-source but use tools that aren’t, especially when we’re talking about community building. Sure, you can do your outreach exclusively on Mastodon or Farcaster, but the most eyes just happen to be on closed platforms, so it’d just be self-sabotage. Doing the only thing that makes sense doesn’t make you a hypocrite.