[–] 1 point 1 month ago (1 child)

What kind of criteria or tests are you imagining?

A certificate after a test would only show capability, not continued practice. So my confidence in it wouldn't be very high. Demonstrated practice seems more applicable than some cert some time ago. Some people chase certs to check boxes rather than prove or apply the practice.

  • source
  • [–] 2 points 1 month ago*

    I hope my drive-by PRs don't come off in the same way.

    For example, as the simplest no-description, no-comment example, when I see typos or wording errors in text on a random blog I check if there's a direct way to contribute - to GitHub edit and submit a PR, and when there is, I do that.

    There's nothing for me to say or describe, really, and it's not like I interacted with their project or community before or even plan to after. (Sometimes I do look into the issue tracker etc depending on the project or website. But that's beside the raised concern.)

    I see it more of a collective and open collaboration. But that's not necessarily visible on the receiving end.

  • source
  • [–] 5 points 1 month ago*

    I have a colleague where I get more confused when they explain things to me. I have others I can understand just fine, because their explanations make logical and structural sense.

    Reasonable questions about surrounding context and environment and common understanding aside, having to do questions to "fix" bad communication and explanations sucks.

  • source
  • [–] 7 points 1 month ago

    I think the title and this 30s framing sucks, but the other/later points they make are broadly good guidelines. A mindset of trying to understand context and environment surrounding the question or change at hand. It's certainly necessary to maintain and improve long running projects.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    As a software developer I've always been a product engineer as well. AI tools did not change that for me.

    Coding, reviewing, and ops is certainly not gone nor disappearing fast for me.

  • source
  •  

    Central to Copilot Studio’s innovation is its deep integration with .NET, including the use of .NET on WebAssembly (WASM).

    This post explores how Copilot Studio utilizes .NET, the benefits realized from platform upgrades, and the resulting performance, cost, and productivity improvements.

    Copilot Studio is a low-code experience for creating conversational and autonomous agents, but the runtime executing those agents is based on .NET.

     

    Four more days until dotnet 10 release. Are you excited?

    I am. There's always a ton of new things, some quite pleasant and exciting to use. C# extension usually have the biggest impact on me. This time, I'm excited for

    • Null-conditional assignment
    • Simple lambda parameters with modifiers
    • field backed properties

    Last week I tried/had to try RC2 and assess release notes for changes because [developing and] debugging Blazor WebAssembly in dotnet 9 is bothersome. I wasn't successful in making the switch, but I found a service worker registration bug fix noted with "should also be applied to dotnet 9 projects" which solved the biggest issue for now (deployed app not updating).

    I'm still concerned about the Blazor WebAssembly tech complexity and indirection (we're working on an offline-capable website/PWA), but I'm somewhat hopeful dotnet 10 will improve working with and on it a bit.

     

    Alternative press article: https://www.bleepingcomputer.com/news/security/self-spreading-glassworm-malware-hits-openvsx-vs-code-registries/

    Identified extensions are mainly on OpenVSX - an alternative VS Code Extension Marketplace.

    Update (Oct 19, 2025): A new infected extension detected in Microsoft's VSCode marketplace - still active.

    Bleepingcomputer:

    Microsoft has removed the malicious extension frrom its marketplace following the researchers' alert.

     

    Alternative press article: https://www.bleepingcomputer.com/news/security/self-spreading-glassworm-malware-hits-openvsx-vs-code-registries/

    Identified extensions are mainly on OpenVSX - an alternative VS Code Extension Marketplace.

    Update (Oct 19, 2025): A new infected extension detected in Microsoft's VSCode marketplace - still active.

    Bleepingcomputer:

    Microsoft has removed the malicious extension frrom its marketplace following the researchers' alert.

     

    […] We are announcing the .NET Security Group, a group of organizations that will collaborate on delivering security fixes to the broadest set of .NET users, simultaneously with Microsoft. We’re all better served by getting more deployments patched, quickly and predictably.

    We’re believers in the concept of upstream open source projects. That includes sharing vulnerability information with other organizations that distribute .NET. We’ve done that with a small set of companies since 2016, starting with Red Hat. Members receive source patches prior to public disclosure so that binary packages can be built, validated, and published at the same time as Microsoft. Membership of this group has been private, by invitation only, and grew to include Canonical, IBM, Red Hat, and Microsoft. That’s how the .NET Security Group started.

    We are expanding the program to enable organizations that ship their own distribution of .NET to have the same ability to better protect their users. By sharing information about vulnerabilities with trusted partners early, we hope to reduce the time between public disclosure of CVEs and when updates are available for distributions other than Microsoft’s. We believe this will help strengthen the security of the .NET ecosystem.

    […] Several Linux distributions do this, as do independent software vendors (across both Windows and Linux). In fact, we worked in collaboration with these same organizations to reduce the cost of building .NET, resulting in the dotnet/dotnet repo. We want it to be straightforward and low-cost to distribute security fixes to users.

    More recently, other organizations came to us asking if they could get access to patches for their End-of-Life servicing businesses. These requests made us realize that it was time to publicize the .NET Security Group and better define its goals. Program members need to be active participants in the .NET upstream project and publish builds for supported .NET versions. Doing that demonstrates a strong commitment to the ecosystem and earned credibility to all participants.

     

    This month you will find that these CVEs have been fixed:

    CVE # Title Applies to
    CVE-2025-55248 .NET Information Disclosure Vulnerability .NET 9.0, .NET 8.0
    CVE-2025-55315 .NET Security Feature Bypass Vulnerability .NET 9.0, .NET 8.0
    CVE-2025-55247 .NET Denial of Service Vulnerability .NET 9.0, .NET 8.0
    CVE-2025-21176 .NET Remote Code Execution Vulnerability .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1
     

    About Bun:

    Bun is a fast, incrementally adoptable all-in-one JavaScript, TypeScript & JSX toolkit. Use individual tools like bun test or bun install in Node.js projects, or adopt the complete stack with a fast JavaScript runtime, bundler, test runner, and package manager built in. Bun aims for 100% Node.js compatibility.

    1.3 release:

    The highlights:

    • Full‑stack dev server (with hot reloading, browser -> terminal console logs) built into Bun.serve()
    • Builtin MySQL client, alongside our existing Postgres and SQLite clients
    • Builtin Redis client
    • Better routing, cookies, WebSockets, and HTTP ergonomics
    • Isolated installs, catalogs, minimumRelease, and more for workspaces
    • Many, many Node.js compatibility improvements
    view more: ‹ prev next ›