• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle


  • I’m a software engineer. Most things should not be patentable.

    Look and feel? No. Basic architecture? No. Given the same set of problems, engineers are very likely to come up with similar solutions.

    I once designed an extremely complicated framework for TV apps. My boss at one point was impressed because he sat in on a “lecture” I was giving to a new teammate describing the architecture and why the complexity was needed. My boss got eager and asked if it was something we could patent. I said no.

    About a year later, a coworker sent me an article from Netflix describing an extremely similar solution to what I had devised, from around the same time.

    Same problem, pursued completely independently, with very similar solutions.

    I believe that anti theft laws are sufficient for protecting proprietary algorithms/protocols, which does need to be protected. But ideas shouldn’t be patentable.

    I.E., gestures to navigate? No. Bezzles on smart screens? No. Backwards engineering your 5G protocol to be used with unapproved devices? Should be protected, but I don’t think patents should be the vehicle. Backwards engineering your own 5G protocol that’s very similar? Ehhhh debatable



  • I find the “clean history” argument so flawed.

    Sure, if you’re they type to micro commit, you can squash your branch and clean it up before merging. We don’t need a dozen “fixed tests” commits for context.

    But in practice, I have seen multiple teams with the policy of squash merging every branch with 0 exceptions. Even going so far as squash merging development branches to master, which then lumps 20 different changes into a single commit. Sure, you can always be a git archeologist, check out specific revisions, see the original commits, and dig down the history over and over, to get the original context of the specific change you’re looking into. But that’s way fucking more overhead than just looking at an unmanipulated history and seeing the parallel work going on, and get a clue on context at a glance at the network graph.




  • Before the paranoid think it’s invasive, it’s used mainly to tell the website what your browsers capabilities are, so that features work and render properly. And by “tell the website”, I mean they generally serve the same “code” to everyone, and your browser just uses different parts of it.

    It’s not as big of a deal now, but browsers used to render things very differently and had unique style features. Safari is still a big offender of this.

    The above Google search features probably means the developers being Google, probably just thoroughly tested the more niche features on Chrome. And probably at some point, other browsers like Safari shit the bed (common) because they used features that Safari didn’t support at the time, and decided to just disable them for Safari.