mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

#softwaredevelopment

41 posts39 participants0 posts today
Zuri (he/him) 🕐 CET<p>This year's <a href="https://mastodon.online/tags/StateOfHTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateOfHTML</span></a> feature score:<br>270 points</p><p>What's yours?</p><p>Find out: <a href="https://survey.devographics.com/en-US/survey/state-of-html/2025" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">survey.devographics.com/en-US/</span><span class="invisible">survey/state-of-html/2025</span></a></p><p><a href="https://mastodon.online/tags/StateOfHTML2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateOfHTML2025</span></a> <a href="https://mastodon.online/tags/StateOfHTMLSurvey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateOfHTMLSurvey</span></a> <a href="https://mastodon.online/tags/StateOfHTML2025Survey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateOfHTML2025Survey</span></a> <a href="https://mastodon.online/tags/StateOfHTMLSurvey2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateOfHTMLSurvey2025</span></a> <a href="https://mastodon.online/tags/StateofSurvey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateofSurvey</span></a> <a href="https://mastodon.online/tags/StateofSurveys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StateofSurveys</span></a> <a href="https://mastodon.online/tags/amCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amCoding</span></a> <a href="https://mastodon.online/tags/amProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amProgramming</span></a> <a href="https://mastodon.online/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.online/tags/webDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDevelopment</span></a> <a href="https://mastodon.online/tags/softwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareDevelopment</span></a> <a href="https://mastodon.online/tags/softwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareEngineering</span></a></p>
glyn<p>Do you write code that runs on Linux and macOS? If so, what does your development environment look like? Please boost for visibility.</p><p><a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> <a href="https://fosstodon.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a></p>
Zuri (he/him) 🕐 CET<p>source control main branch progression FOMO</p><p><a href="https://mastodon.online/tags/amCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amCoding</span></a> <a href="https://mastodon.online/tags/amProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amProgramming</span></a> <a href="https://mastodon.online/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.online/tags/webDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDevelopment</span></a> <a href="https://mastodon.online/tags/softwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareDevelopment</span></a> <a href="https://mastodon.online/tags/softwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareEngineering</span></a> <a href="https://mastodon.online/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> <a href="https://mastodon.online/tags/vcs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vcs</span></a></p>
Miguel Afonso Caetano<p>Do AI models help produce verified bug fixes?</p><p>"Abstract: Among areas of software engineering where AI techniques — particularly, Large Language Models — seem poised to yield dramatic improvements, an attractive candidate is Automatic Program Repair (APR), the production of satisfactory corrections to software bugs. Does this expectation materialize in practice? How do we find out, making sure that proposed corrections actually work? If programmers have access to LLMs, how do they actually use them to complement their own skills? </p><p>To answer these questions, we took advantage of the availability of a program-proving environment, which formally determines the correctness of proposed fixes, to conduct a study of program debugging with two randomly assigned groups of programmers, one with access to LLMs and the other without, both validating their answers through the proof tools. The methodology relied on a division into general research questions (Goals in the GoalQuery-Metric approach), specific elements admitting specific answers (Queries), and measurements supporting these answers (Metrics). While applied so far to a limited sample size, the results are a first step towards delineating a proper role for AI and LLMs in providing guaranteed-correct fixes to program bugs. </p><p>These results caused surprise as compared to what one might expect from the use of AI for debugging and APR. The contributions also include: a detailed methodology for experiments in the use of LLMs for debugging, which other projects can reuse; a finegrain analysis of programmer behavior, made possible by the use of full-session recording; a definition of patterns of use of LLMs, with 7 distinct categories; and validated advice for getting the best of LLMs for debugging and Automatic Program Repair"</p><p><a href="https://www.arxiv.org/abs/2507.15822" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">arxiv.org/abs/2507.15822</span><span class="invisible"></span></a></p><p><a href="https://tldr.nettime.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://tldr.nettime.org/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeAI</span></a> <a href="https://tldr.nettime.org/tags/LLMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLMs</span></a> <a href="https://tldr.nettime.org/tags/Debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debugging</span></a> <a href="https://tldr.nettime.org/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://tldr.nettime.org/tags/APR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APR</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://tldr.nettime.org/tags/SoftwareBugs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareBugs</span></a></p>
brozu ▪️<p>Chiunque abbia realizzato qualche prodotto software complesso (e non mi riferisco quindi alla solita landing page o sito web) sa benissimo che l’<a href="https://mastodon.uno/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> va usata con coscienza, altrimenti si perde più tempo a sistemare i casini per poi ritrovarsi un prodotto architetturalmente imbarazzante.</p><p><a href="https://mastodon.uno/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwaredevelopment</span></a></p>
Benjamin Han<p>Interesting tidbits from <a href="https://sigmoid.social/tags/Anthropic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Anthropic</span></a>’s blog on how they use Claude Code:<br><a href="https://www.anthropic.com/news/how-anthropic-teams-use-claude-code" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">anthropic.com/news/how-anthrop</span><span class="invisible">ic-teams-use-claude-code</span></a></p><p>Top tip from Data Science and ML Engineering teams: treat it like a *slot machine*. Save your state before letting Claude work, let it run for 30 minutes, then either accept the result or start fresh…</p><p>Top tip from Product Engineering teams: treat it as an *iterative partner*, not a one-shot solution…</p><p><a href="https://sigmoid.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://sigmoid.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://sigmoid.social/tags/genAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>genAI</span></a> <a href="https://sigmoid.social/tags/agentic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>agentic</span></a> <a href="https://sigmoid.social/tags/agents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>agents</span></a> <a href="https://sigmoid.social/tags/softwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareDevelopment</span></a></p>

"[W]hat we are doing is shepherding AI, limiting it to certain contexts. We are learning where it’s best to call it, how is best to feed it. And what to do with the output. So is it looks very much like an editorial process, an editorial workflow where you provide some initial input, maybe some some idea on what content to produce, then you review it. There’s always that quality assurance, quality control side, the supervision.

AI is not really autonomous. It relies a lot on us. And I feel like sometimes there are days where, when coding through AIs or doing some assisted writing, I’m spending more time helping out the AI doing the actual task that I’m asking the AI to do. But I take this as a learning process. I read this article the other day, Nobody knows how to build with AI yet. And it was a developer saying that they haven’t quite figured out how to best work with AI. There were lots of comments around the fact that you have to spend lots of time, you have to learn how to talk to it, and when the model changes, you have to also maybe change something you’re doing. You have to learn how to optimize your time. But your presence is always mandatory.”

passo.uno/webinar-ai-tech-writ

passo.uno · Webinar: What's Wrong with AI Generated DocsToday I discussed how tech writers can use AI at work with Tom Johnson and Scott Abel. It all started from my post What’s wrong with AI-generated docs, though we didn’t just focus on the negatives; in fact, we ended up acknowledging that, while AI has limitations, it’s also the most powerful productivity tool at our disposal. Here are some of the things I said during the webinar, transcribed and edited for clarity.

Putting together a talk proposal for our local Cybersecurity conference: Open Source and CVEs: the Forever War

Really good discussion on an aspect of this with team-mates: dependency updates. Ignoring updates avoids all pain related to changes -right up until the day a critical CVE is discovered and you have to do an update from five versions behind: all the upgrade pain hits on a critical timeline

This is technical debt which is easy to build up but quietly builds up until you hit that massive compound repayment.

Our term "credit card technical debt". You need to pay it off every month or have credit card class interest.

Which makes for a really good concept "you SHALL allocate effort into updating your dependencies to their latest releases" -including all compatibility issues. Process-wise, first day of the month is the best time to maintain the habit.