TL;DR

• Pull requests were designed for open source contributions from untrusted strangers. Applying them to trusted teams is a category error.
• Peer-reviewed research shows code review’s primary value is knowledge transfer, not bug detection. Less than 15% of review comments relate to actual bugs.
• Async PR workflows mean your code spends 86-99% of its lead time waiting. One organisation spent 130,000 hours in a single year waiting on PRs that received zero comments.
• DORA research across 36,000+ professionals shows trunk-based development correlates with dramatically higher software delivery performance, and faster code reviews alone improve performance by 50%.
• The alternative is T*D: Test-Driven Development (build quality in), Trunk-Based Development (integrate continuously), and Team-focused Development (review during creation, not after).
• The transition is gradual: optimise PRs first, adopt Ship/Show/Ask, then move to pairing and trunk-based development as trust and automation mature.-

In April 2000, Stack Overflow founder Joel Spolsky published an essay titled “Things You Should Never Do, Part I”. The occasion was Netscape's decision to rewrite the code of its then-browser from scratch instead of further developing the existing disciplin

Spolsky's thesis: This decision was the worst strategic mistake a software company could make. It was based on a fundamental misunderstanding of what programming work actually is. Programmers prefer to rewrite because reading foreign code is tedious and writing feels productive. But this impression is deceptive. The temptation to start over is one of the most expensive temptations in the industry.

More than 25 years later, this text has lost none of its relevance. On the contrary. With the advent of Large Language Models (LLM), the asymmetry between writing and reading has shifted to such an extent that the question becomes acute whether we are systematically underestimating the true senior discipline of software development. Typing is not what will keep teams breathless in the coming years. Reading is. In this article, I want to show why this is the case, where the asymmetry comes from, how it is exacerbated by generative AI, and how a casual accompanying skill must become an independent discipline.

Hello everyone

We released iceoryx2 v0.9 tonight. With the release, we are pushing more and more iceoryx2 into the embedded world. We have written a test runner that runs on std and no_std environments, stabilized the decentralized recovery, and added a ton of quality of life improvements.

• blog article: https://ekxide.io/blog/iceoryx2-0.9-release
• repo: https://github.com/eclipse-iceoryx/iceoryx2
• roadmap: https://github.com/eclipse-iceoryx/iceoryx2/blob/main/ROADMAP.md
• crates-io: https://crates.io/crates/iceoryx2
• docs-rs: https://docs.rs/iceoryx2/latest/iceoryx2

For those who haven’t heard of it yet: iceoryx2 is a zero-copy inter-process communication library.

The basic idea is: instead of serializing data, copying it through sockets, pipes, message queues, or some broker process, iceoryx2 lets processes communicate via shared memory. That makes it useful when you care about latency, throughput, or moving large amounts of data between processes without wasting CPU cycles on copies.

It supports C, C++, Python, Rust, and C#, and runs on Linux, macOS, Windows, FreeBSD, and QNX, with experimental support for Android and VxWorks.

It is not limited to plain pub/sub either. iceoryx2 supports publish-subscribe, events, request-response streams, and a blackboard pattern, which is basically a key-value repository directly in shared memory.

The architecture is fully decentralized: no central broker, no daemon that everything depends on, and no single process that becomes the obvious bottleneck or failure point.

Happy to answer questions about the release, the no_std work, or zero-copy IPC in general.

Good morning 👾

I'd like to fetch data via BLE (Python or Swift) from a cheap smart ring that can be reverse engineered or that is already RE'd. Pulse, oxygen levels, gyroscope, button would be very useful. I'd like to build a python or swift library.

Thank you for any input =)

cross-posted from: https://lemmy.ml/post/47339272

Finally I can stay forever on lemmy even not opening the browser! 😂

Thinking of using it as a mod tool to see new posts in communities I moderate.

Sharing it early, maybe get some ideas on how to make it better.

https://github.com/tracyspacy/lemmy-tray

Meme sin ánimo de ofender a nadie (es triste tener que aclarar eso en estos tiempos)

SAN FRANCISCO, CA - In the wake of a devastating supply chain attack in the npm registry that left millions of enterprise applications compromised and billions of user records exposed, developers across the JavaScript ecosystem expressed deep sorrow today, lamenting that such a crisis was completely unavoidable.

“It’s a shame, but what can you do? This is just the price of building modern web apps,” said Senior Frontend Engineer Mark Vance, echoing the sentiments of a community that completely relies on a 40-level-deep nested tree of unvetted packages maintained by pseudonymous strangers to capitalize a single string. “There’s absolutely no way to foresee or prevent someone from taking over a long-abandoned utility package and injecting a crypto-miner into every production build in the world. It’s just an act of nature.”

cross-posted from: https://piefed.social/c/webdev/p/2066757/oc-open-sourcing-my-full-implementation-of-material-design-3-based-theming

I recently realized that I've been tinkering on my main hobby project for a year now, and that it's not even remotely at a point where I'd be willing to publish it (either by actually launching it or by Open-sourcing and handing it off to someone else). But one of the features I built in recently, a fully customizable website theming function, seemed actually pretty solid and pleasant to use, so I'd like to share it within this separate project.

-> Here's the link to my live demo
-> Here's the link to my codeberg repo

If you have any questions, feel free to ask them here! I realize that documentation is not my strong suit haha
Any feedback or suggestions are appreciated as well :)

Every feedback for code or programming or recommendation of any locomotive or train is welcomed :)

In case you missed it, ChatGPT 5.1 had a tendency to talk about "goblins" in its responses. Supposedly this was a result of training a "nerdy" personality, but it bled into the model as a whole. Because the training run for the latest model already had this flaw, they had to add specific instructions to the system prompt for their Codex coding tool to avoid this behaviour.

Here's the full prompt from their github. In fact, they repeated the goblin instructions twice, cos you know that will definitely fix it. It's an interesting read if you consider each one of these instructions were meant to prevent some undesired behaviour: https://paste.sh/Iev3HtMe#JZ4dw_CkvJcpVmjjoy7WZnSn

More info here: https://news.northeastern.edu/2026/05/06/chatgpt-goblins-problem-ai-behavior/

OpenAI's own blog post casually explaining why they couldn't predict that their state of the art model would obsess about goblins: https://openai.com/index/where-the-goblins-came-from/