jmoiron plays the blues
@jmoiron.bsky.social replied: A vital skill that good software engineers develop over time is knowing when a pattern is real and affords you leverage to make material organizational improvements and when a pattern is weak or coincidental and extracting it just makes things worse.
LLMs are really poor at this...
@jmoiron.bsky.social replied: I'd like to explore why this happens in a bit more detail, and maybe I will if I get back to that post, but at its core, it comes down to an LLMs "preference" for generation over consolidation compounding over time.
Which isn't surprising. They are generative models.
@jmoiron.bsky.social replied: But LLM code generation is kind of the inverse of that old 3 step owl drawing process. It starts by producing you a nearly finished Owl, and then you spend the rest of your time struggling to get it to fix one thing without breaking another.
@jmoiron.bsky.social replied: It's well known that programmers all think they're at least 2-5x better than they are, that's why our estimates are always crap.
But using an LLM you really can produce some decent software in a proverbial weekend. I "wrote" my own Kanban board over the course of ~3 days this we...
@jmoiron.bsky.social replied: A lot of people are rightfully asking, "If LLMs make software development so much faster, where's all the great software?"
I think the answer is that LLMs are a 10x improvement on building software but only ~1.5x on maintaining it, and most software development is maintenance.
@jmoiron.bsky.social replied: I have a half-written post about how LLMs are great producers and good summarizers, but they've are poor organizers. This might be a reflection on ourselves, given how they're trained.
This can all feel contradictory initially.
@jmoiron.bsky.social Another example of what I wrote about in "Wirth's Revenge."
Your first prompt for an unfamiliar problem should be "explain 3 ways to solve this problem."
People imagine these simple data manipulations are easy for LLMs, but they lack the fine motor skills to do this type of wor...
jmoiron/giverny main 1638302 · fix crazy big <p> margins in descriptions
jmoiron/giverny main 699db7a · add basic support for comments on cards
jmoiron/giverny main 6933660 · fix bug where drag-clicking from inside a modal and mousedown outside a modal would close the modal
jmoiron/giverny main dcd395d · fix bug where newly created cards cannot be dragged
jmoiron/giverny main 8107331 · sync new checklist events correctly to other clients
jmoiron/giverny main 6e90505 · make color updates on labels not require save and sync it across users
jmoiron/giverny main b79226d · unify color pickers for labels and cards, first label sets card color, better random label color selection
jmoiron/giverny main 601202e · fix card view for non-editor anons and users
jmoiron/giverny main d5c74ec · start anon public board viewing
jmoiron/giverny main 9b0562e · update screenshots
jmoiron/giverny main dfd07ac · fix card modal x in wrong spot, fix nginx contrib
jmoiron/giverny main 2fcd4e0 · fix an error in systemd file
jmoiron/giverny main 54240a4 · add contribs for systemd and nginx
jmoiron/giverny main 7a3cfd3 · Update README.md
jmoiron/giverny main e80a3f9 · update readme a bit, add screenshots
jmoiron/giverny main 5481b20 · add support for file attachments to cards, make image rendering in description not destroy the layout
jmoiron/giverny main fa64b6a · fix a little visual bug when selecting card colors for cards that have checklists
jmoiron/giverny main 733ed68 · show checklist status in kanban cards, some unification of card rendering