Mastodon: @sean@dice.camp

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

help-circle










  • If you have seniority and they are a junior, some juniors do respond well to a senior having more knowledge about the codebase. With them, it can be beneficial to use a tone like “We have library X that seems like it could do a lot of the functionality here, unless you already took a look?” I know it’s like 90% of the same but I know people who will just be shellshocked and just blindly say “yes” to any question you ask them, and I don’t want a blind “yes” I wanna know the truth :) it also lets then explain why they didn’t use it if they have a legit reason because hey, maybe I’m the one who needs to be caught up




  • AGPL? Google has a ban on all AGPL software. Sounds like if you write AGPL software, corporations won’t steal it.

    Code licensed under the GNU Affero General Public License (AGPL) MUST NOT be used at Google.

    The license places restrictions on software used over a network which are extremely difficult for Google to comply with. Using AGPL software requires that anything it links to must also be licensed under the AGPL. Even if you think you aren’t linking to anything important, it still presents a huge risk to Google because of how integrated much of our code is. The risks heavily outweigh the benefits.

    Any FLOSS license that makes a corporation shit its pants like this is good enough to start from IMO.

    https://opensource.google/documentation/reference/using/agpl-policy