Feels surprisingly accessible. Makes me want to play with meshstatic now.

This is a good look at the reasons behind throttling. If you accept a less naive model than "preventing abuse", you can build a better throttling strategy.

I felt that a bit the past couple of years when looking how the ecosystem evolved. The situation seems concerning to me.

A bit focused on web frontend, but that applies equally to other stacks. There are many reasons to make UIs accessible.

Interesting trick. Good way to frame decision making when needed.

OK, this is a serious and long paper. It shows quite well how over reliance on ChatGPT during the learning phase on some topics impacts people. It's mesurable both from their behavior and through EEG. Of course, it'd require more such studies with larger groups. Still those early signs are concerning.

This is definitely a paradox in community dynamics.

Interesting findings about procrastination. Some effects were expected, others less so. The actions to avoid it in teams should be well known now.

Maybe it's just me but I find that fascinating.

Interesting comparison of different definitions for software complexity (which is an ambiguous term to say the least). It leads to nice consequences when team dynamics are considered.

Wondering how to implement your own inference engine? Here is a nice simple blueprint to get started.

Interesting research. Down the line it could help better fine tune models and side step some of the attention system limitations. Of course it comes with its own downsides, more research is necessary.

This is in my opinion one of the most difficult tasks when rendering with the GPU. Texts are really hard to get right.

A very important tool to have around and know how to use. This is a neat introduction.

It is indeed much easier nowadays to preserve produced content. We have so many open and simple formats to choose from. It's not always been like this.

Juggling different roles isn't easy. It's indeed even harder when friendships are involved. Know which hat you're wearing at all times.

Nice little post helping advocate for the use of Architectural Decision Records.

Early days for that service. Let's hope it improves infrastructure wise.

A good example of how you can get bitten by cache coherency algorithms in the CPU.

A nice followup which acts as a TL;DR for the previous piece which was fairly long indeed.