Interesting analysis around the current situation around web scraping and intellectual property. This moved to being mostly dealt with using contract law which makes it a terrible minefield. Lots of hypocrisy all around too which doesn't help. GPT and the likes will likely be the next area where cases will rise.

Nice introduction to domain repetitions. A fascinating concept (IMHO) very much used in procedurally generated content.

Lots of good advices for dealing with a conflict. Choosing the right words and the right time matter. Not easy to apply but worth trying.

A good reference on most of the branching patterns you can find. From this you can derive your project wide policy. Also it's spot on when it says that branching is easy but each time you branch you need to keep in mind how you're going to merge.

Nice little primer about Elixir and Phoenix. Be careful though, I spotted a couple of mistakes in the code examples. That still gives a good idea of advantages and limitations of this stack.

Good balanced view about Web Components. Interestingly it seems the adoption is already higher than I expected.

Good reminder of the benefits of having a model of your architecture and keeping it up to date. It's something too often forgotten in teams I think. Interesting to see C4 getting some traction, I think it strikes a good balance.

Looks like a very nice alternative to ngrok. It's free, doesn't require any particular command to download, just works through SSH.

Good reminder that we have no idea of the window size the user will have. It's in the context of web frontends here, but really it applies to desktop applications as well (we have a bit more control on the minimal size there but that's it).

Definitely this! There are awesome Free Software alternatives to Zoom. We need to get more people to use them

Now this could turn out to be interesting. To be confirmed when this get closer to production (if it does), especially on the power consumption side. This will be the important factor to make this viable I think.

If you want to know more about how to use mirror balls to create environment maps, this is a good resource.

This is clearly getting more mature. Even the list of issues presented here actually makes me want to try it more as to evaluate the exact impacts.

Looks like a handy tool for licenses compatibility checking.

To take with a pinch of salt, it conflates a few things in my opinion. Still it's a good reminder that eliminating complexity shouldn't be a goal. Managing said complexity and avoiding the undue one, this is what matters.

Very good points about cultural differences. Indeed some people directly ask and express their needs, others are more waiting and take into account everyone else's needs when asked. Both have pros and cons, it's important to know where you stand.

Interesting rewrite attempt. Gives nice information on the original code and the PSX architecture as well.

Please, even if you're not French go and sign this. It can't be allowed to pass, this would create a dangerous precedent.

Interesting advices. As usual with this kind of topics it's probably easier said than done though.

Good explanations around the (deserved) complaints against Zoom and their not that new user license.