home.social

#softwareengineering — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #softwareengineering, aggregated by home.social.

  1. What would it take for your team to change an engineering process this afternoon?

    If AI agents can change code in minutes, why should changing the engineering processes take weeks?

    I'm not arguing against documented processes. Quite the opposite. I'm arguing against casting them in concrete.

    Some thoughts on agentic engineering and continuously evolving the engineering system:

    lnkd.in/p/eV3hbpAu

  2. If you fully outsource your work so that none of your team fully understand the codebase, it's a production risk.
    You need to have an internal up to date knowledge to handle outages and production incidents.
    Or, at minimum, you should ring fence the outsourced code so that its blast radius is a known minimised risk.

    Yes, by outsourcing, I include AI code generation.

  3. The power of relationships…

    80% of the jobs I’ve been offered in a 24-year career have come from companies where I already had an existing relationship with someone at that company…

    And they put in a good word for me…

    ✅ Your reputation as a professional software developer matters.
    ✅ Your reputation as a confident communicator matters.
    ✅ Your reputation as a team player matters.

    #developers #coding #softwaredevelopment #softwareengineering #wellbeing #mindset #mentalhealth

  4. Code review tip: read the tests first.

    They show what the author thinks the code does. The diff shows what it does.

    Bugs live in the gap.

    #SoftwareEngineering #CodeReview

  5. Don't let the same LLM write and review your code.

    → Claude analyzes your last 1,000 PRs to build a team style guide, then writes the code.
    → Gemini takes over code review and enforces the rules.

    The result? Fewer review nits. Zero "AI smell"

    🎥 Watch the full panel [transcript included] – infoq.com/presentations/panel-

    #SoftwareEngineering #AI #CodeReview #ClaudeAI #Gemini #DevWorkflow #LLMs

  6. The #technology industry doesn't have the equivalent of a Standard Of Care in, say, medicine, so we get dumb stuff like this (not introducing artificial jitter) happening over and over again, with not enough durable learning happening in professions like #softwareengineering

    #AI has the potential to help with that by copying known #bestpractices as a matter of due course

    #groundhogday
    sciencealert.com/power-grids-o

  7. The US tech industry faces a dual reality of widespread job cuts alongside intense competition for specialized artificial intelligence talent.

    AI startup Serval recently offered 30000 dollar hiring bonuses, referral incentives, and luxury vacations to fill engineering roles, competing against giants like OpenAI and Anthropic.

    Data from Payscale and Levels.fyi highlights rising wages and salary premiu…

    en.hacks.gr/pos-i-techniti-noi

    #ArtificialIntelligence #TechIndustry #SoftwareEngineering #Careers

  8. New post: Every link was a fix.

    I know, I'm becoming a stuck record on bugs AI found. This one gets a single paragraph on that, and the rest goes on how it happened.

    The *sshole bug lets a 257-byte password into an account that's meant to be locked (root, on the wrong Alpine box). Pull it apart and I couldn't find a careless piece anywhere.

    The `*` in the password field goes back to 3BSD in 1980 ("The devil himself"). In 2012 musl made crypt() return `*` on failure because callers were crashing. libxcrypt, which now sits under crypt() on most glibc distros, has long used `*0` for the same job, and that one character is most of why glibc distros aren't affected. In 2016 OpenSSH fixed a username timing leak by borrowing another account's salt. And Alpine, after shipping root with an empty password, went to `!` and later `*` so key logins would still work.

    Five links, five fixes. musl's guard spent ten years protecting the setting, which wasn't the string being compared. sshd's fix checks the stored field where it's used, which I'd call the lesson, as long as nobody turns it into "trust no one".

    The awkward bit: I'd have installed that 2016 fix almost straight away. My Renovate config soaks ordinary updates for three days and lets security advisories straight through. So the class of patch that opened this hole is the one I trust most, and fastest. Is day nought right? Still pondering.

    phpboyscout.uk/every-link-was-

  9. To write professional GitHub commits, learn to follow the unspoken rules of version control. hackernoon.com/how-to-write-pr

  10. This goes to show that if you write a really good spec, the coding part is pretty easy.

    Funny how what we already knew decades ago will now be becoming standard practice thanks to .

    It was about time.


    geekwire.com/2026/aws-gives-de

  11. Google highlighted how stale TODO comments, obsolete bug references, and outdated specs distract coding agents and send them on unrequested side-quests.

    The takeaway? Technical debt doesn't just slow down developers. It can derail AI agents, too.

    🔗 More details 👉 infoq.com/news/2026/11/google-

    #AI #CodingAgents #TechnicalDebt #SoftwareEngineering #Google #InfoQ

  12. AI makes you faster at writing code. But does it make you worse at debugging it?

    An Anthropic study tested developers learning a new library:
    • AI-assisted coders: 50%
    • Coding by hand: 67%

    The hardest hit? Debugging.

    Turns out, they didn't trade speed for learning - they traded learning for nothing.

    No trade-off. Just loss.

    🔗 Watch the full video (transcript included) – infoq.com/presentations/ai-sof

    #AI #SoftwareEngineering #Debugging #AICoding #DeveloperProductivity #Anthropic #InfoQ

  13. Our image editor asks a provider for at most 6 edit suggestions: maxItems: 6 in the JSON schema. Last Saturday it returned 8. Our validation rejected the list, and the user got a 502 instead of 6 good suggestions.

    So the schema only tells the provider what we want. Not every provider holds to it.

    It happened once. The fix was one function: keep the first 6, then validate.

    Where do you draw the line between trimming a bad response and failing it?

    #Programming #SoftwareEngineering

  14. "Like developers do not ask permission to write a forEach instead of a for-loop, they should not ask permission to keep the code clean. It is their job, and it is what is expected from them."

    drpicox.medium.com/how-i-fixed

  15. This is what I think the future will bring: Saas is not going to die anytime soon, but highly personalized software will be more common for those who are capable of building.

    I don't know whether building apps with AI will remain a trend for the foreseeable future, because I meet a lot of people who, when I tell them that I'm doing all this stuff or created all this stuff, their eyes glaze over and they just want a solution right out of the box.

    I conclude that not everybody enjoys building something from scratch.

    Just like how some people are happy to build static websites on their own, but others prefer something out of the box like Wordpress. (example: me; I could easily build a static website myself, it's just that these days my bandwidth is far too low to maintain one on my own).

    What do you think? What AI projects have you built, and do you think the age of personalized software has arrived, or is this just a temporary trend?

  16. A prototype can be built in an afternoon. Getting it into production is another story.

    Vibe coding makes writing software faster, but SOC compliance, legal reviews, security, and QA still take time.

    The new enterprise bottleneck isn't writing code - it's everything required to ship it safely.

    🎥 Watch the full panel [transcript included] – infoq.com/presentations/panel-

    #VibeCoding #SoftwareEngineering #EnterpriseTech #DevOps #InfoQ

Share on Mastodon

Enter the server where you have an account.