#Tag
Is there anything that #generativeAI can do to _assist_ in code reviews rather than _do them instead_. Most of the benefits suggested seem to be better done with a formatter, a linter or a AI pairing buddy.
The main surviving benefit seems to be summarizing massive PRs (which seems to be managing the symptom of a deeper problem) rather than an improvement.
What are people doing with AI that does help?
Thinking about the DORA 2025_state_of_ai_assisted_software_development report.
Dora is owned by Google cloud and therefore has a financial incentive to be "Pro" AI to support Gemini etc.
It also, historically depends on developers self reporting if they think they are more effective (which has been shown to not necessarily correlate with actual improved effectiveness).
Is DORA a trustworthy commentator on this?
#ai #generativeAI #devops #softwaredevelopment #softwareengineering
In software development, „fast or good“ is a false dichotomy. There is a path that gets you both:
Simplicity.
In software development, „fast or good“ is a false dichotomy. There is a path that gets you both:
Simplicity.
This is beautiful; pure poetry: https://obsidian.md/blog/less-is-safer/
(Obsidian’s dependency-management philosophy.)
I have a suggestion: If you have a project or repo that's getting popular, stop writing features for a few months and implement this instead.
If you're a senior-level developer and wondering how to continue to rise the ranks without switching into management (a completely different skill set!), the terms to look for are "staff" and/or "principal" engineer.
I didn't know this until ~4 years ago, so maybe it's news to you, too!
#SoftwareEngineering#CareerGrowth #StaffEngineer
https://topspicy.social/@alda/115197562688337784
If you're a senior-level developer and wondering how to continue to rise the ranks without switching into management (a completely different skill set!), the terms to look for are "staff" and/or "principal" engineer.
I didn't know this until ~4 years ago, so maybe it's news to you, too!
#SoftwareEngineering#CareerGrowth #StaffEngineer
https://topspicy.social/@alda/115197562688337784
✨📄 New blog post: An Interview with Felienne Hermans 📄✨
We caught up with keynote speaker @Felienne to chat about her journey into #programming and #Python’s influence along the way, creating Hedy, challenges & hopes for the Python ecosystem, and what she’s most looking forward to at #PyConUK2025 🐍✨
📖 Read the interview here: https://2025.pyconuk.org/2025/08/keynote-speaker-interview-felienne/
A huge thank you to Felienne for taking the time to share your thoughts with us 💜
✨📄 New blog post: An Interview with Felienne Hermans 📄✨
We caught up with keynote speaker @Felienne to chat about her journey into #programming and #Python’s influence along the way, creating Hedy, challenges & hopes for the Python ecosystem, and what she’s most looking forward to at #PyConUK2025 🐍✨
📖 Read the interview here: https://2025.pyconuk.org/2025/08/keynote-speaker-interview-felienne/
A huge thank you to Felienne for taking the time to share your thoughts with us 💜
8pm Tuesday Boston time
#lispyGopherClimate#commonLisp #astrophysics #supercomputing#softwareEngineering #archive , https://communitymedia.video/w/9kysH4ZwVuP4J4erZozqFT we will have (now done) a live interview with
https://as.tufts.edu/physics/people/faculty/ken-olum
about the recent largest-ever cosmic string simulation also introducing their new spacetime-volume pseudo-parallel simulation technique, relating to gravitational backreaction.
People sometimes ask, "who uses common lisp today".
Olum learned #lisp from John McCarthy.
"The very thing that makes AI coding tools accessible to non-engineers - their ability to handle complexity on your behalf - can actually impede learning. When code just "appears" without you understanding the underlying principles ...
This creates a dependency where you need to keep going back to AI to fix issues, rather than developing the expertise to handle them yourself."
#AddyOsmani, 2024
https://addyo.substack.com/p/the-70-problem-hard-truths-about
I am recruiting a postdoctoral researcher to work at Polytechnic Institute of Paris for 30 months, in the fields of #SoftwareEngineering and #Cybersecurity The recruited person will work on leveraging @swheritage as a knowledge base to improve the state of the art of (binary) software composition analysis (SCA), to detect the presence and details of #OpenSource software shipped within IT products. See https://institutminestelecom.recruitee.com/l/en/o/post-doctorante-ou-post-doctorant-en-genie-logiciel-et-cybersecurite-cdd-de-30-mois-2-5 for details and application instructions. #getfedihired
I am recruiting a postdoctoral researcher to work at Polytechnic Institute of Paris for 30 months, in the fields of #SoftwareEngineering and #Cybersecurity The recruited person will work on leveraging @swheritage as a knowledge base to improve the state of the art of (binary) software composition analysis (SCA), to detect the presence and details of #OpenSource software shipped within IT products. See https://institutminestelecom.recruitee.com/l/en/o/post-doctorante-ou-post-doctorant-en-genie-logiciel-et-cybersecurite-cdd-de-30-mois-2-5 for details and application instructions. #getfedihired
Great talk by @hynek , definitely worth watching: https://www.youtube.com/watch?v=IhNSINolcSM Really enjoyed it.
#python#PyconUK2025 #architecture #development #softwareengineering #software
Great talk by @hynek , definitely worth watching: https://www.youtube.com/watch?v=IhNSINolcSM Really enjoyed it.
#python#PyconUK2025 #architecture #development #softwareengineering #software
One reason I think that complex #AI software projects are never going to happen is that the code it generates has no intent behind it.
Senior software devs spend an extraordinarily large amount of time reading existing code and asking not just HOW they work, but WHY they were written that way. Reading long-maintained, complex source code is more than mere reading comprehension; it’s LITERARY CRITIQUE. You’re constantly trying to understand the thought process and motivation of whoever wrote that code, in the hopes of gaining insight into their frame of mind.
Well, AI code has no motivation, thought process, nor frame of mind. While the code it generates MIGHT work correctly (a big assumption) at the point it was extruded, there is no plausible way of maintaining that code, and at some point of complexity (sooner than you think!) maintainability becomes critical.
#softwareEngineering#softwareDevelopment
…
AI will never be a replacement for expertise. It does not compensate for a lack of skill. It offers nothing to replace an understanding of the fundamental principles of the craft. It will not turn a junior engineer into a senior one.
And it will not create a complex product, at least not one that won’t crumble the moment you have to maintain it.
A space for Bonfire maintainers and contributors to communicate
