• 0 Posts
  • 77 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
    10
    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?










  • Well yes and no. Market cap is the total value of all shares for the particular stock combined (not including those held by the company itself). The value of each individual share is determined on the market. No-one directly “owns” this value, since the whole point of stocks is to distribute ownership, so no-one including Apple as an entity “owns” their market cap entirely. If that were the case, there would be no trading, and ergo no value to the shares, and the entire idea of a market cap no longer applies.

    Individually though, the value of shares is of course very real. If you own shares and the stock is liquid (as in: there are people willing to buy), you can sell those shares for real money whenever you wish, at the current market price. Unless you want to sell a substantial amount, in which case you may run into trouble finding buyers and / or create significant downward pressure on the price.