How to Write with an LLM(sockpuppet.org)
696 points by joeriddles | 396 comments
Blog post on sockpuppet.org offering two rules for using LLMs to streamline and improve writing without making it bland.
696 points by joeriddles | 396 comments
Blog post on sockpuppet.org offering two rules for using LLMs to streamline and improve writing without making it bland.
394 points by rdslw | 247 comments
A blog post arguing developers want a good Markdown viewer, discussing how LLM agents have revived TUI tooling and an Emacs-like trend in software.
290 points by fratellobigio | 437 comments
Blog post on sockpuppet.org musing on how AI is reshaping what an operating system is, and announcing the author is leaving Fly.io to work with Kurt on a new project.
1162 points by mrkurt | 416 comments
Blog post by Thomas Ptacek about testifying in an Illinois court case over whether public bodies can withhold database schemas from FOIA requests, and pending legislation.
28 points by surprisetalk | 6 comments
407 points by domenicd | 385 comments
Domenic Denicola's blog post arguing that building native Windows desktop apps today is a confusing mess, explaining why developers turn to Electron.
24 points by speckx | 35 comments
Blog post arguing that text user interfaces (TUIs) are an underappreciated third way of using Linux, between the command line and graphical desktops.
686 points by Kerrick | 629 comments
Blog post arguing that frontend teams should stop rewriting apps in new frameworks and instead learn their current tools deeply, since frameworks churn every few years.
519 points by ssaboum | 261 comments
Blog post by Olivier Girardot arguing that good software should know when to stop adding features, opening with a hypothetical surprising change to the ls command.
323 points by matthewsinclair | 214 comments
Blog post by Matthew Sinclair arguing that LLM-powered programming tools act like a mech suit amplifying developers rather than replacing them.
363 points by edent | 461 comments
Ryan Barrett's blog post arguing the Twitter API is effectively unmaintained, citing the decline of Twitter employee posts on the developer forum.