Tags: web-review, distributed, biology, physics, learning, security, architecture, business, project-management, science, encodings, tdd, simulation, hacking, complexity, neural-networks, tools, copilot, system, criticism, programming, quality, scrum, collaborative, webgpu, networking, unicode, tech, linux, bias, pattern, management, research, gpu, data-oriented, c++, problem-solving, ar, algorithm, economics, rust, machine-learning, tor, agile, performance, ai, estimates, gpt, reliability, ecology, tests, refactoring, kanban, organization, game, android, forecasting, multithreading, culture, engineering, design, safety, mobile, energy, qt
Let’s go for my web review for the week 2025-21.
Tags: tech, c++, qt
Nice little interview showing what’s brewing in the Qt project and how the relationship with KDE is important.
Tags: tech, linux, android, ar, mobile
This is a funny setup. It’s not very expensive either.
https://holdtherobot.com/blog/2025/05/11/linux-on-android-with-ar-glasses/
Tags: tech, algorithm, complexity, research
Interesting new proof on the relationships between P and PSPACE. Let’s see where this leads.
https://www.quantamagazine.org/for-algorithms-a-little-memory-outweighs-a-lot-of-time-20250521/
Tags: tech, ai, machine-learning, gpt, energy, ecology, economics
That’s a good overview of the energy demand, it doesn’t account for all the resources needed of course. Now of course like most articles and studies on the topic, it’s very inaccurate because of the opacity from the major providers in that space. The only thing we know is that the numbers here are likely conservative and the real impact higher. Mass use of those models inferences is already becoming a problem, and it’s bound to get worse.
https://www.technologyreview.com/2025/05/20/1116327/ai-energy-usage-climate-footprint-big-tech/
Tags: tech, ai, machine-learning, gpt, bias
Those hosted models really exhibit weird biases… The control of the context is really key.
https://www.dbreunig.com/2025/05/21/chatgpt-heard-about-eagles-fans.html
Tags: tech, ai, machine-learning, neural-networks, science, research
Or how the current neural networks obsession is poisoning scientific fields. There was already a reproducibility crisis going on and it looks like it’s been getting worse. The incentives are clearly wrong and that shows.
https://www.understandingai.org/p/i-got-fooled-by-ai-for-science-hypeheres
Tags: tech, ai, machine-learning, copilot, learning, programming, quality
Somehow not surprising… There’s an area where it works OK. That said, I think we don’t have the right UX to exploit it safely and productively. The right practices still need to be found. This isn’t helped by all the hype and crazy announcements.
https://albertofortin.com/writing/coding-with-ai
Tags: tech, ai, machine-learning, gpt, copilot, quality, learning, hacking, culture, criticism
This is a good rant, I liked it. Lots of very good points in there of course. Again: the area where it’s useful is very narrow. I also nails down the consequences of a profession going full in with those tools.
https://deplet.ing/the-copilot-delusion/
Tags: tech, ai, machine-learning, gpt, engineering, quality, architecture, problem-solving
You can’t be in the backseat when using those tools. Otherwise you might feel productive by cranking out code but it can’t do the essential tasks for you (most notably actual problem solving or architecture thinking). The quality would clearly suffer.
Tags: tech, ai, machine-learning, gpt, reliability, business
If the funding dries up… we’ll have another AI winter on our hands indeed.
https://www.datagubbe.se/winter/
Tags: tech, networking, tor
Feels a bit like bad coordination on the Tor project side this one.
https://daniel.haxx.se/blog/2025/05/16/leeks-and-leaks/
Tags: tech, networking, tools, security
Seriously… Developers should be ashamed to produce such invasive tools.
Tags: tech, encodings, unicode, programming, security
Unicode in source code can come with unwanted consequences. Tooling might be required.
https://daniel.haxx.se/blog/2025/05/16/detecting-malicious-unicode/
Tags: tech, programming, multithreading
Nice approach, especially useful if you need to split work to distribute it to threads.
https://lemire.me/blog/2025/05/22/dividing-an-array-into-fair-sized-chunks/
Tags: tech, data-oriented, architecture, c++, performance
Or how it’s possible to expose an object-oriented like API for a data oriented framework without sacrificing on performances.
https://bannalia.blogspot.com/2015/09/c-encapsulation-for-data-oriented.html
Tags: tech, c++, programming
Friendly reminder that in C++ that case evolved quite a bit all the way to C++23. Please use the more recent constructs in new code. This definitely leads to better patterns.
https://lemire.me/blog/2025/05/18/returning-several-values-from-a-function-in-c-c23-edition/
Tags: tech, rust, reliability, safety
I find the title misleading. Still, this is a good exploration of how to treat unwrap() and expect() in Rust code.
https://burntsushi.net/unwrap/
Tags: tech, rust, programming
Another trick in Rust to avoid unwrap() calls. The let-else option is indeed particularly elegant.
https://corrode.dev/blog/rust-option-handling-best-practices/
Tags: tech, architecture, rust, programming, pattern
Apparently this needs pointing out but there’s more than async/await out there. Sometimes what you want is a simple event loop. Here illustrated in the Rust ecosystem.
Tags: tech, webgpu, gpu, physics, biology, simulation
Nice in depth article on how to run particle simulations using WebGPU. This one has a very life like rendering.
https://lisyarus.github.io/blog/posts/particle-life-simulation-in-browser-using-webgpu.html
Tags: tech, programming, game
There are options indeed. Some of them can be maybe surprising. It of course depends the type of game you’re making.
https://noelberry.ca/posts/making_games_in_2025/
Tags: tech, game, programming, design
This is indeed an excellent way to understand all the roles and the work behind creating a game.
https://lizengland.com/blog/the-door-problem/
Tags: tech, tests, performance, complexity, system
Or why it’s hard to truly evaluate performance in complex systems. We often test things in the optimistic case.
https://brooker.co.za/blog/2025/05/20/icpe.html
Tags: tech, distributed, design, pattern
Good explanation of an important design pattern as soon as you have remote calls.
https://martinfowler.com/bliki/CircuitBreaker.html
Tags: tech, architecture, collaborative, organization
Another way to approach Architecture Decision Records. A different format to try to foster a more collaborative approach.
https://www.workingsoftware.dev/introducing-the-software-architecture-decision-canvas/
Tags: tech, programming, refactoring
Good reminder that refactoring isn’t necessarily the end of a cycle. It can also be before you add a feature.
https://martinfowler.com/articles/preparatory-refactoring-example.html
Tags: tech, tests, tdd
A quick summary of the different properties you want in tests. In practice you’ll likely have to find a tradeoff among them.
Tags: tech, tests, tdd
This explains quite well how TDD is made of several cycles of different length.
https://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html
Tags: tech, agile, management
Rituals are definitely important… if you understand why you’re going through them. If you just “go through the moves” they’re failing.
https://agileweboperations.com/2014/07/10/3-reasons-why-your-team-needs-rituals/
Tags: tech, estimates, project-management
Don’t throw estimates out of the window. Keep in mind that the more precise they are the more expensive they become.
https://www.mountaingoatsoftware.com/blog/paying-the-cost-for-more-precise-estimates
Tags: tech, agile, forecasting, estimates, business
Interesting point of view. I’m not sure I fully agree with the classification but it gives something to mull over. For sure the less reliable your estimates the more padding is needed to have some predictability.
https://www.jamesshore.com/v2/blog/2014/agile-and-predictability#_949792
Tags: tech, agile, scrum, kanban, estimates, forecasting
This is indeed two sides of the same coin. A good reminder that you need to pick the right approach depending on the context.
https://blog.gdinwiddie.com/2014/12/10/relationship-of-cycle-time-and-velocity/
Bye for now!