• 5 Posts
  • 205 Comments
Joined 2 years ago
cake
Cake day: August 10th, 2023

help-circle


  • This is just one of the comments on the Revolt E2EE issue, I guess the author felt so proud of their opinion to make it into a blog post, I wouldn’t say anything if they at least revisited the whole discussion and tried to make a reasonable summary.
    The argument provided in the article against features is simply “too hard to develop, too hard to maintain, nobody cares enough”.
    If nobody cared, nobody would go on Matrix, if everything that was hard to develop were just dropped before even trying, we would have stopped at the hello world (not implying I’m not a lazy developer, but I surely don’t want to imply that there aren’t brilliant people out there who can undertake scarily big tasks).
    Giving another feature as a sort of replacement: federated identities, is not a replacement at all, it’s a completely different scope. I just can’t empathise with the point that they try to make







  • when during job interview the recruiter ask if you code on the weekend

    I think it’s more to see if you’re actually passionate about what you do and you don’t “just” do it for work, which definitely is a bit of a twisted view, when on average you’ll already be spending 40 hours a week doing that, but I think people tend to make this sort of evaluation, because people who love programming so much to also do it on their free time will usually be better, since they simply have more experience than those who only do what they’re assigned to do





  • You can’t rely on their goodwill, you either make it enforceable with a license, or you just treat it as a something that you don’t expect to make money from.

    The comparison to artists doesn’t really hold, because they won’t start a work for someone without them asking, then showing off their creation and hoping that the involuntary “client” will pay for it once it’s already been done.
    While programmers can be commissioned to make some piece of software, that will most likely end up as proprietary, unless stated otherwise in the contract between the two parties, akin to a commissioned piece of art, hardly any client will be ok or even proactively ask you to release the work under a CC license.

    Companies especially are more revenue than image driven (or solely tbh), so they won’t “waste” any money where they can avoid it, if Amazon finds a nice service they can host and tweak on their AWS that promises to be useful and make them lots of money, they will just go for it and stay within the lines of what the license allows, which often is “too open” for its own good (think MIT), so the project won’t see nothing like a contribution back, let alone money.
    The illuminated companies that can (more like want to) afford to contribute in any way to software they rely on are few and far apart and it takes them to realize how much of an impact the project they’re using makes on their business, which is often difficult to put into tangible numbers, we see that happening mostly with the biggest projects, think Blender, Linux, etc. The poor library developer will most likely never see a dime coming from the thousands of employers whose developers will pull in their dependency for their product