• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



  • Good enough? I mean it’s allowed. But it’s only good enough if a licensee decides your their goal is to make using the code they changed or added as hard as possible.

    Usually, the code was obtained through a VCS like GitHub or Gitlab and could easily be re-contributed with comments and documentation in an easy-to-process manner (like a merge or pull request). I’d argue not completing the loop the same way the code was obtained is hostile. A code equivalent of taking the time (or not) to put their shopping carts in the designated spots.

    Imagine the owner (original source code) making the source code available only via zip file, with no code comments or READMEs or developer documentation. When the tables are turned - very few would actually use the product or software.

    It’s a spirit vs. letter of the law thing. Unfortunately we don’t exist in a social construct that rewards good faith actors over bad ones at the moment.


  • As someone who worked at a business that transitioned to AGPL from a more permissive license, this is exactly right. Our software was almost always used in a SaaS setting, and so GPL provided little to no protection.

    To take it further, even under the AGPL, businesses can simply zip up their code and send it to the AGPL’ed software owner, so companies are free to be as hostile as possible (and some are) while staying within the legal framework of the license.





  • I don’t think it will be that cut and dry.

    A huge number of tech companies are still and/or will always be fully remote.

    Over time, the big pay checks that Meta and Google and Apple are offering will be overshadowed by the possibilities of remote work done right (as opposed to simply working as you are in the office but from home).

    There are lots of smart, talented folks out there willing to take a pay cut to gain back the time that office culture can waste, commuting first of all.

    Sure there are challenges to the sense of togetherness that can help build great teams, but plenty of remote-only organizations make the time and space to foster that appropriately.

    Ultimately, I think we’ll find that the eventual competitors to the MAANG-like behemoths emerge out of smart, well designed, remote-first organizations. Though I think Netflix is largely remote - at least for the engineers I know who work there.






  • The only way to ensure privacy is something like PGP. Encrypt before you send. Heck you could even encrypt before you put the contents into a message body.

    With self hosted, the messages themselves aren’t encrypted at rest and they are clear text between hops even if those hops support TLS in transit.

    Ultimately the right answer for you will hinge on what your definition and level of privacy is.


  • I second this.

    It’s going to be hard. If the recruiter/TA Specialist is good at their job they’ll try to get you to give a “ballpark.” They’ll do anything to try to figure out the lowest offer they can make.

    Do not give in.

    Hold firm and ask what their offer is and go from there.

    In one case their offer was double what I was expecting. It changed my life.

    In other, their offer was just slightly under what I was expecting and I got what I hoped for with little effort and only a single back and forth.

    There is one exception here: if they really want you and you are ABSOLUTELY sure you’re out of their salary band for the position, you can wield your salary demands like a sword. I recently used my expected salary (which I knew the company wouldn’t match) to negotiate a 4-day work week at their full time pay, with an extra week of vacation tacked on for good measure. Win win.