I continue to experiment with #AI in the context of #softwareengineering. I’m fortunate that my team supports me in exploring different ways to improve our daily work. This week, I designed a team of #autonomousagents to implement features, from design to implementation.
softwareengineering
What I’ve been reading (and listening to) this week ending 18 January 2026 https://jchyip.medium.com/what-ive-been-reading-and-listening-to-this-week-ending-18-january-2026-a3d228ed216f #Misinformation #SoftwareEngineering #Economics #AI #Management
#oop #programming #GUI #commonLisp #McCLIM #softwareEngineering
Article in which I show simple multiple inheritance and method qualifiers in ANSI common lisp's common lisp object system, then show how the McCLIM implementation of the common lisp interface manager 2 specification turns the objects I was working with into rich general user interfaces with a minimal declarative effort presupposing that I was presenting lisp objects.
Rich interfaces pervade lisp's history.
https://screwlisp.small-web.org/clim/basic-principle/
#lispyGopherClimate Sunday morning in Europe with #lisp # live @kentpitman
Going over proto #emacs, #cref, #lispm #computerScience #softwareEngineering #GUI history ! Ask questions in #lisp on #irc now please !
https://toobnix.org/w/gXLXQqxf5MYg1NDF2Ua6oA 15 minutes to live.
Edited 304d ago
Programming properly should be regarded as an activity by which the programmers form or achieve a certain kind of insight, a theory, of the matters at hand. This suggestion is in contrast to what appears to be a more common notion, that programming should be regarded as a production of a program and certain other texts.
A computer program is not source code. It is the combination of source code, related documents, and the mental understanding developed by the people who work with the code and documents regularly. In other words a computer program is a relational structure that necessarily includes human beings.
The output of a generative AI model alone cannot be a computer program in this sense no matter how closely that output resembles the source code part of some future possible computer program. That the output could be developed into a computer program over time, given the appropriate resources to do so, does not make it equivalent to a computer program.
#AI #GenAI #GenerativeAI #LLM #Copilot #AgenticCoding #dev #tech #SoftwareDevelopment #SoftwareEngineering #programming #coding
Edited 1y ago
What I’ve been reading (, watching, and listening to) this week ending 3 May 2026 https://jchyip.medium.com/what-ive-been-reading-watching-and-listening-to-this-week-ending-3-may-2026-ccff2e9a2a0e #science #innovation #ai #economics #politics #SoftwareEngineering
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.
Edited 1y ago
Programmers and software developers lost the plot on naming their tools
https://larr.net/p/namings.html
#Programming #SoftwareEngineering
https://larr.net/p/namings.html
#Programming #SoftwareEngineering
https://communitymedia.video/w/c2D8hXG2zixrjz6jyX96N9
#python #commonLisp #softwareEngineering #programming
Lisp industry adopted modern condition handling adapted to python introduced by @kentpitman .
An incredibly important realisation of dynamic #typeTheory with modern industry adoption. (Except conditions are more general than type checking and errors). See the peertube description for a longer spiel I will not reproduce here.
45 minute video, I snipped the after-discussion from the livestream.
#Perl: older than some #programming careers, younger at heart than you think.
It’s evolved a lot since 1999 — modern features, cleaner syntax — yet it still runs code you wrote decades ago.
(And if you’re wondering: #Perl6 was renamed Raku in 2019 — it’s a sister language, not a successor.)
Curious? Returning after a long break? @shiar’s cheat sheet is a perfect quick‑scan: https://sheet.shiar.nl/perl
#coding #SoftwareDevelopment #SoftwareEngineering #RakuLang #Perl5
Edited 361d ago
@yantar92 #interview on the #lispyGopherClimate Sunday-Morning-in-Europe
So please #AMA in this thread, where "me" in this case is Ihor and "anything" is "questions about orgmode <dev>"
Tuesday-night-in-Americas was Charlie Holland (KMP, Ramin, mdh, sacha, ..) on "emacs minibuffer style" incremental completing read and lisp https://toobnix.org/w/imfwummHKcycJoujnGVjgy
Last week was bagder of Curl (feat KMP, Ramin, the moo crowd) https://toobnix.org/w/rPKt4GRBwLeWzF3VcMFWNo
#lisp #dev #softwareEngineering #emacs #orgmode #pleaseBoost
Tomorrow, "Tuesday evening in the Americas" #lispyGopherClimate #podcast will feature @chiply and we will be talking about fancy #emacs #autocomplete, its #lisp diaspora (#McCLIM completions!), antecedents and... Future.
Thoughts (and prayers) here please. #AMA (about the topic. Me mainly being https://www.chiply.dev/post-vompeccc-spot in this case.).
Edit: Aside, it probably does to mention for context that the following Sunday will be @yantar92 on #orgmode .
Edited 127d ago
My personal experience as the sometime operator of a 1980s Xerox photocopier
https://screwlisp.small-web.org/lispgames/wicked-problems/
Notes about #usability #design from Winograd and Adler's Usability ( #bookstodon ) relevant to my #NicCLIM #commonLisp #gamedev .
Introduces design's wicked problems and the implications for what design even is, conveyed by the book via a series of c. 80s case studies.
What I’ve been reading this week ending 29 March 2026 https://jchyip.medium.com/what-ive-been-reading-this-week-ending-29-march-2026-b64266d11621 #management #ai #economics #SoftwareEngineering
What I’ve been reading (and watching) week ending 26 July 2026 https://jchyip.medium.com/what-ive-been-reading-and-watching-week-ending-26-july-2026-9c11a433eabc #politics #AI #SystemsThinking #economics #Lean #SoftwareEngineering
What I’ve been reading (watching, and listening to) this week ending 25 January 2026 https://jchyip.medium.com/what-ive-been-reading-watching-and-listening-to-this-week-ending-25-january-2026-9c368055fb96
#Lean #Depression #SoftwareEngineering #Politics #Economics #AI #Science #ProductManagement
What I’ve been reading (and watching) this week ending 15 February 2026 https://medium.com/@jchyip/what-ive-been-reading-and-watching-this-week-ending-15-february-2026-a677a7e43d8d #Lean #Leadership #Politics #Management #AI #SoftwareEngineering
Hello Fedi
what software or service do you use to create software architecture diagrams? you know, those rectangle and arrows in UML.
I don't need sophisticated features, whatever that does the job and makes it faster than using a pen and paper.
boosts are welcome ❤️
#fediask #softwareengineering #java
what software or service do you use to create software architecture diagrams? you know, those rectangle and arrows in UML.
I don't need sophisticated features, whatever that does the job and makes it faster than using a pen and paper.
boosts are welcome ❤️
#fediask #softwareengineering #java
https://screwlisp.small-web.org/conditions/partial-gopher-client/
#commonLisp #conditionHandling implemented as a #gopher protocol using #emacs #slime as the client.
This is even better than it sounds.
The condition handling system (nonfatal generalization of exception handling using lisp's local restarts/continuations) is unexplored and seen as opaque.
Using this tiny but esoteric example the available non-lexical computed restarts of an interactive condition are simply /browsable/.
Edited 200d ago
It's Sunday morning in Europe! #archive 8UTC Sunday as always #lispyGopherClimate #podcast since 2022.
https://toobnix.org/w/pU6zu95YDdyGKqsxxRf3Vg #peertube live
#RSS (recent times) https://toobnix.org/feeds/videos.xml?accountId=580185
@vnikolov 's Quality Without A Name toot #AI
As much as I can remember about the #lisp community #architecture and Christopher Alexander https://www.dreamsongs.com/Files/PatternsOfSoftware.pdf https://alexandria.common-lisp.dev/
My NicCLIM #IDE demo and the #DL book I am #writing - loose bibliography and sketch of chapters
Edited 101d ago
#itchio #programming style #devlog #conditionHandling #commonLisp #reliability #softwareEngineering
Finally pretty happy with my "programming ls" example. This is a good programming with conditions first blush, I think.
Programming with signals and restarts that a run-time handler-bind hooks into gives a program, such as my %%ls here, *forward compatibility* not just *backwards compatibility* - which I explore as a property of ansi common lisp itself.
Thoughts!
What I’ve been reading (and watching) week ending 9 August https://jchyip.medium.com/what-ive-been-reading-and-watching-week-ending-9-august-1ab6b2dde859 #AI #DistributedSystems #science #engineering #SoftwareEngineering #cybersecurity #ProductManagement
I recently reread Fred Brooks's 1986 classic No Silver Bullet, which you can find here: https://www.cs.unc.edu/techreports/86-020.pdf . I think it is useful to re-consider Brooks's distinction between the essential complexity versus the accidental complexity of software development in light of the recent mania behind using LLMs for coding. Which of these types of complexity does LLM use address? Does it introduce more of either class of complexity?
In light of what I've seen, LLM use seems to provide the illusion of addressing both kinds of complexity in the short-term while it increases essential complexity in the long-term. It may or may not reduce some accidental complexity; the verdict is still out, as far as I can tell. Judging from the recent leak of the Claude Code front end source code, LLMs seem to introduce an enormous amount of new accidental complexity.
To the extent that LLMs are in the category of what Brooks calls automatic programming, this quote he shares from David Parnas is important:
Taken together, all this seems to suggest that LLM use in coding is a net negative, and if the above is to be believed it will result in worse outcomes, not better, over the long haul. Definitely re-read Brooks and see if you agree.
#AI #GenAI #GenerativeAI #AgenticAI #LLMs #ClaudeCode #software #tech #dev #SoftwareEngineering #SoftwareDevelopment
In light of what I've seen, LLM use seems to provide the illusion of addressing both kinds of complexity in the short-term while it increases essential complexity in the long-term. It may or may not reduce some accidental complexity; the verdict is still out, as far as I can tell. Judging from the recent leak of the Claude Code front end source code, LLMs seem to introduce an enormous amount of new accidental complexity.
To the extent that LLMs are in the category of what Brooks calls automatic programming, this quote he shares from David Parnas is important:
Automatic programming always has been a euphemism for programming with a higher-level language than was presently available to the programmer.
Taken together, all this seems to suggest that LLM use in coding is a net negative, and if the above is to be believed it will result in worse outcomes, not better, over the long haul. Definitely re-read Brooks and see if you agree.
#AI #GenAI #GenerativeAI #AgenticAI #LLMs #ClaudeCode #software #tech #dev #SoftwareEngineering #SoftwareDevelopment
I realized that if I was writing a program and it didn't always work, I had a choice: I could either fix it, or call it AI.
#AI #GenAI #GenerativeAI #AgenticAI #LLMs #Claude #ClaudeCode #ChatGPT #tech #dev #software #SoftwareDevelopment #SoftwareEngineering