[–] 8 points 2 months ago

So my main point is to stop asking whether and how code review in its current form can be saved, but to have an open conversation about what we are trying to achieve here and the costs and benefits of alternative models.

What would these other models be? The article assumes LLM-generated code leads to the loss of current review processes, which they call 'modern reviews'.

I feel like my team does and will continue to do reviews for the same reasons and with the same gains as before. LLM may generate code, but I expect my colleagues to take ownership of whatever they produce, to understand it, take responsibility, and describe it. (Which is an issue/gap for some, but that was an issue even before generating code.)

  • source
  • [–] 1 point 2 months ago

    In the .NET world, Entity Framework Core and Dapper are the industry standards. However, many less popular tools are also used in real-world projects. RepoDB and SqlSugar are among these ORMs.

    In this article, we'll look at them through the lens of PVS-Studio static analyzer. Instead of comparing API capabilities or performance, we'll check the projects' source code for potential bugs and suspicious constructs.

    Despite the substantial amount of code and extensive functionality of the projects, the analysis revealed only a few suspicious code fragments. This suggests that both projects are well written and maintained at a high standard.

  • source
  • [–] 12 points 2 months ago* (3 children)

    00:00 Intro
    00:48 Why write a compiler in JavaScript
    07:29 Why rewrite the compiler in Go
    14:49 LLMs for large migrations
    20:12 Why Javascript is so popular
    26:32 Why ever use Javascript on the backend
    32:59 What it takes to build a programming language
    37:06 Will there be fewer languages in 10 years
    42:57 Hands on engineering vs delegation
    49:14 Why fast tooling matters more now
    51:16 AI software engineering predictions
    58:52 The most technically challenging work
    01:02:04 Top book recommendation
    01:03:50 Advice for his younger self
    01:05:00 Outro

    Just summarizing the title teasers:

    10x faster by switching from JavaScript to Golang. Rust was not feasible because it does not have a GC/does not support circular dependencies, and they have many of those, and did not want a rewrite but a minimal effort switch.

    AI may produce a lot more code, but what code does "90% of code" refer to. AI is not capable of novel or complex stuff, you still need humans in the loop. Juniors remain significant to train them into seniors.

  • source
  • parent
  • context
  • [–] 4 points 2 months ago

    DDOS is most effective on expensive endpoints. A git clone isn't exactly cheap. Fetching is especially expensive if you vary the revisions you fetch.

    Does GitHub have an alternative here? A Git-compatible protocol with anonymous access that is DDoS-resilient?

  • source
  • parent
  • context
  • [–] 5 points 2 months ago (2 children)

    Our aim is to make public repositories accessible without authentication as much as possible. However, like much of the Internet, we continue to see significant increases in the volume of robot traffic recently which has increased the need for verification, for example CAPTCHAs.

    As I expected, it's about combating (excessive) bot traffic.

  • source
  • [–] 7 points 2 months ago

    “If you submit a PR, no hard feelings, we’re just going to go and represent it for you as issues and discussions.

    They're saying, "We're not feeling negatively, but we're closing your PR to turn it into an issue and discussion". I wonder if the one on the receiving end will have hard feelings.

  • source
  •  
    • GC: Garbage Collector manages the allocation and release of memory for your application
    • DATAS: Dynamic Adaptation To Application Sizes

    In .NET 9 we enabled DATAS by default. But .NET 9 is not an LTS release so for many people they will be getting DATAS for the first time when they upgrade to .NET 10. This was a tough decision because GC features are usually the kind that don’t require user intervention — but DATAS is a bit different. That’s why this post is titled “preparing for” instead of just “what’s new” 😊.

    I’ll talk about how we generally decide which performance features to add, why DATAS is so different from typical GC features, and the tuning changes introduced since my last DATAS blog post. I’ll also share two examples of how I tuned DATAS in first-party scenarios.

     

    Interop 2025 is a cross-browser effort to improve the interoperability of the web — to reach a state where each technology works exactly the same in every browser.

    The WPT Dashboard, wpt.fyi, displays results for the web-platform-tests, or WPT, which are a group of test suites for many web platform specifications.

    I linked to the stable view. Experimental has much higher scores. (Hopefully stable soon? :))

     

    Pijul is a free and open source (GPL2) distributed version control system. Its distinctive feature is to be based on a theory of patches, while still being fast and scalable. This makes it easy to learn and use, without any compromise on power or features.

    Why Pijul

    Pijul is the first distributed version control system to be based on a sound mathematical theory of changes. It is inspired by Darcs, but aims at solving the soundness and perfor>mance issues of Darcs.

    Pijul has a number of features that allow it to scale to very large repositories and fast-paced workflows. In particular, change commutation means that changes written independently can be applied in any order, without changing the result. This property simplifies workflows, allowing Pijul to:

    • clone sub-parts of repositories
    • solve conflicts reliably
    • easily combine different versions.

    The main difference between Pijul and Git (and related systems) is that Pijul stores changes (or patches), whereas Git deals only with snapshots (or versions).

     

    Pijul is a free and open source (GPL2) distributed version control system. Its distinctive feature is to be based on a theory of patches, while still being fast and scalable. This makes it easy to learn and use, without any compromise on power or features.

    Why Pijul

    Pijul is the first distributed version control system to be based on a sound mathematical theory of changes. It is inspired by Darcs, but aims at solving the soundness and perfor>mance issues of Darcs.

    Pijul has a number of features that allow it to scale to very large repositories and fast-paced workflows. In particular, change commutation means that changes written independently can be applied in any order, without changing the result. This property simplifies workflows, allowing Pijul to:

    • clone sub-parts of repositories
    • solve conflicts reliably
    • easily combine different versions.

    The main difference between Pijul and Git (and related systems) is that Pijul stores changes (or patches), whereas Git deals only with snapshots (or versions).

     

    Yesterday programming.dev was down for hours.

    I checked https://status.programming.dev/ and it is indeed a working status page, but with no monitors added.
    Which is already surprising.

    But even more confusing is the consequential claim of "All Systems Operational", even when the instance is down/unreachable.

    What's the state and plan for the status page?

     

    cross-posted from: https://programming.dev/post/36983916

    Freund wasn’t looking for a backdoor when he noticed SSH connections to his Debian testing system taking 500 milliseconds longer than usual. As a database engineer benchmarking PostgreSQL performance, he initially dismissed the anomaly. But the engineer’s curiosity persisted.

    The backdoor’s technical sophistication was breathtaking. Hidden across multiple stages, from modified build scripts that only activated under specific conditions to obfuscated binary payloads concealed in test files, the attack hijacked SSH authentication through an intricate chain of library dependencies. When triggered, it would grant the attacker complete remote access to any targeted system, bypassing all authentication and leaving no trace in logs.

    The backdoored versions 5.6.0 and 5.6.1 had been released in February and March 2024, infiltrating development versions of Fedora, Debian, openSUSE, and Arch Linux. Ubuntu’s upcoming 24.04 LTS release, which would have deployed to millions of production systems, was mere weeks away.

    The technical backdoor was merely the final act of a three-year psychological operation that began not with code, but with studying a vulnerable human being.

     

    Freund wasn’t looking for a backdoor when he noticed SSH connections to his Debian testing system taking 500 milliseconds longer than usual. As a database engineer benchmarking PostgreSQL performance, he initially dismissed the anomaly. But the engineer’s curiosity persisted.

    The backdoor’s technical sophistication was breathtaking. Hidden across multiple stages, from modified build scripts that only activated under specific conditions to obfuscated binary payloads concealed in test files, the attack hijacked SSH authentication through an intricate chain of library dependencies. When triggered, it would grant the attacker complete remote access to any targeted system, bypassing all authentication and leaving no trace in logs.

    The backdoored versions 5.6.0 and 5.6.1 had been released in February and March 2024, infiltrating development versions of Fedora, Debian, openSUSE, and Arch Linux. Ubuntu’s upcoming 24.04 LTS release, which would have deployed to millions of production systems, was mere weeks away.

    The technical backdoor was merely the final act of a three-year psychological operation that began not with code, but with studying a vulnerable human being.

    view more: ‹ prev next ›