This is a good explanation of why you should limit your use of mocks. It also highlights some of the alternatives.
This is great news, more scientific papers from the past decades will be accessible to everyone.
We're collectively still failing at handling leap days properly it seems.
Looks like enough people complained that they had to change course. Good, until the next bad move...
A few points to take with a pinch of salt, especially regarding the proposed solutions. Still it makes a very good point that most transformation failures toward agile organizations are due to lack of trust and the swapping of one bureaucracy for another.
Good summary of all the "fake agile" practice one can see. Without enough trust it's not possible to put in place an agile organization.
The HDMI Forum is really an annoying body to say the least... they lack so much transparency.
A nice little review of our latest major releases. Looks like it's well accepted so far. Very glad!
To take with a pinch of salt since it has a couple of biases (most notably it focuses a lot on satisfaction) and the sample size is a bit small. A few interesting insights nonetheless. In particular it hints at autonomy, transparency, technical skills and vision as being the most important factors for satisfaction and success within teams. The applied project management method? Not so important it seems if the other factors are satisfied.
All good reasons to use Firefox! I'm always about the market share of engines where we need diversity, but more good points are brought up here. It's the only going the extra mile to respect your privacy while bringing innovative features too (tested the in browser translation recently and it's great).
Looks like a nice way to properly learn the web frontend basics.
Might be an interesting trick to reduce the computation and energy costs of large language models. Let's see if it gets replicated and generalized, this is a single short paper not peer reviewed anywhere as far as I can tell.
Interesting exploration of what could be done in a 3D engine using plane-based geometric algebra (PGA). This brings in nice properties that matrices don't have. And the performance impact is apparently not as bad as one could have suspected. I definitely look more into it.
Ever wondered how look-up tables are used for graphics? This is a good summary. Shows quite a few use cases which can come in handy.
Interesting take even though I'm not sure I buy it completely. This is an interesting pledge for aiming at power efficiency and squeezing performance out of software.
A bit of a long rant, still the core of the argument stays true. Apple will do everything in its power to keep their platform captive of their app store.
Good advice yes. Having a rough architecture document in a repository is more than welcome, it's needed to help on-boarding. This is unfortunately not the norm in FOSS projects.
Definitely this, mind the complexity you introduce in your code. Looking smart is not the goal here...
Interesting paper attempting to prove that hallucinations are unavoidable in those models. It is well balanced though, and explains why it's not necessarily a bad thing in theory. In my opinion, the problem is the marketing talk around those models making grand claims or denying the phenomenon.
A good exploration of the Fediverse to Bluesky bridging debate from the angle of consent and the GDPR. It's complicated and that shouldn't come as unexpected.