This is the best summary I could come up with:

Even though the research commissioned by consultancy Engprax could be seen as a thinly veiled plug for Impact Engineering methodology, it feeds into the suspicion that the Agile Manifesto might not be all it’s cracked up to be.

One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed.

“Our research has shown that what matters when it comes to delivering high-quality software on time and within budget is a robust requirements engineering process and having the psychological safety to discuss and solve problems when they emerge, whilst taking steps to prevent developer burnout.”

A neverending stream of patches indicates that quality might not be what it once was, and code turning up in an unfinished or ill-considered state have all been attributed to Agile practices.

One Agile developer criticized the daily stand-up element, describing it to The Register as “a feast of regurgitation.”

In highlighting the need to understand the requirements before development begins, the research charts a path between Agile purists and Waterfall advocates.

The original article contains 501 words, the summary contains 175 words. Saved 65%. I’m a bot and I’m open source!

This is the best summary I could come up with:

AMD’s HIP Ray-Tracing library “HIP RT” has been one of the few projects under the GPUOpen umbrella that starts off as closed-source software but then is eventually open-sourced… That happened now with the HIP ray-tracing code becoming publicly available.

AMD announced their ray-tracing library code for easily writing RT applications using HIP is now fully open-source.

The open-source code is published on GitHub under an MIT license.

The GitHub repository currently contains a single commit, adding all the HIP RT 2.3 source files to the repository.

This is newer than the HIP RT 2.2 release from December that is currently advertised via the GPUOpen website.

It’s nice seeing this HP RT code finally open-sourced.

The original article contains 121 words, the summary contains 114 words. Saved 6%. I’m a bot and I’m open source!

This is the best summary I could come up with:

While pushed along by NVIDIA, the VK_NV_raw_access_chains extension was co-authored by Valve’s Hans-Kristian Arntzen.

Arntzen is known for his work on VKD3D-Proton as part of Steam Play and indeed this extension should help out there.

The VK_NV_raw_access_chains extemsion should allow for more efficient shaders compiled from HLSL sources.

This enables SPIR-V producers to efficiently implement interfaces similar to Direct3D structured buffers and byte address buffers, allowing shaders compiled from an HLSL source to generate more efficient code."

Yesterday the Vulkan driver beta page was updated to 550.40.53 for Linux and 551.70 for Windows.

With those new NVIDIA Vulkan betas is support for the NV_raw_access_chains extension as well as NV_low_latency2 and EXT_surface_maintenance1.

The original article contains 176 words, the summary contains 111 words. Saved 37%. I’m a bot and I’m open source!

This is the best summary I could come up with:

While there have been efforts by AMD over the years to make it easier to port codebases targeting NVIDIA’s CUDA API to run atop HIP/ROCm, it still requires work on the part of developers.

The tooling has improved such as with HIPIFY to help in auto-generating but it isn’t any simple, instant, and guaranteed solution – especially if striving for optimal performance.

In practice for many real-world workloads, it’s a solution for end-users to run CUDA-enabled software without any developer intervention.

Here is more information on this “skunkworks” project that is now available as open-source along with some of my own testing and performance benchmarks of this CUDA implementation built for Radeon GPUs.

For reasons unknown to me, AMD decided this year to discontinue funding the effort and not release it as any software product.

Andrzej Janik reached out and provided access to the new ZLUDA implementation for AMD ROCm to allow me to test it out and benchmark it in advance of today’s planned public announcement.

The original article contains 617 words, the summary contains 167 words. Saved 73%. I’m a bot and I’m open source!

This is the best summary I could come up with:

On Thursday, Internet pioneer Vint Cerf announced that Dr. David L. Mills, the inventor of Network Time Protocol (NTP), died peacefully at age 85 on January 17, 2024.

The announcement came in a post on the Internet Society mailing list after Cerf was informed of David’s death by Mills’ daughter, Leigh.

In a digital environment where computers and servers are located all over the world, each with its own internal clock, there’s a significant need for a standardized and accurate timekeeping system.

In the 1970s, during his tenure at COMSAT and involvement with ARPANET (the precursor to the Internet), Mills first identified the need for synchronized time across computer networks.

As detailed in an excellent 2022 New Yorker profile by Nate Hopper, Mills faced significant challenges in maintaining and evolving the protocol, especially as the Internet grew in scale and complexity.

His work highlighted the often under-appreciated role of key open source software developers (a topic explored quite well in a 2020 xkcd comic).

The original article contains 472 words, the summary contains 164 words. Saved 65%. I’m a bot and I’m open source!

This is the best summary I could come up with:

For large organizations, it tends to be a complex and costly proposition, given the small number of COBOL experts in the world.

When the Commonwealth Bank of Australia replaced its core COBOL platform in 2012, it took five years and cost over $700 million.

Running locally in an on-premises configuration or in the cloud as a managed service, Code Assistant is powered by a code-generating model, CodeNet, that can understand not only COBOL and Java but around 80 different programming languages.

A recent Stanford study finds that software engineers who use code-generating AI systems similar to it are more likely to cause vulnerabilities in the apps they develop.

“Like any AI system, there might be unique usage patterns of an enterprise’s COBOL application that Code Assistant for IBM Z may not have mastered yet,” Puri said.

IBM sees a future in broader code-generating AI tools, as well — intent on competing with apps like GitHub Copilot and Amazon CodeWhisperer.

The original article contains 734 words, the summary contains 159 words. Saved 78%. I’m a bot and I’m open source!