I see some folks are taking issue with the word "literalism." The the term "New Literalism" is coined in the linked article[0] as such:
"When I say literalism, I don't mean realistic or plainly literal. I mean literalist, as when we say something is on the nose or heavy-handed, that it hammers away at us or beats a dead horse. As these phrases imply, to re-state the screamingly obvious does a kind of violence to art. "A point is still a point!""
For working on a single project, I have a text document open where I’m working on future prompts. For working on tasks in a team setting, with prs and reviews, i built a tui that manages multiple tmux sessions. It creates a worktree for each task. It has status indicators for each session, hotkeys to quickly cycle through them, hotkeys to pull, annotate and paste pr comments, pull, annotate and paste linear tasks and comments, hotkeys to launch external tools and to jump directly to the pr url, and any time there’s a period when all the dots are busy i just start a new task. It’s a bit manic, but it’s manageable because it’s all in one terminal window. It’s also for AI as it existed 3 months ago, work slowed down and i haven’t tried to apply loops or whatever the latest crazy thing is.
Built my own tui tool. It groups repos into projects and manages a task list for each repo. Creating a new task creates a new worktree, the task view contains two tmux sessions, one of which is a claude or codex session, the other a terminal. I have status dots for the current state of claude/codex and the current state of the pr if it exists. And i have a flow to review and annotate pr feedback and auto paste it back into my llm session with the instructions to address it and push. I have a task switcher which incorporates the status colors so i can tend to the red tasks, wait on the yellow ones, merge the green ones and close out the purple ones. Each task has a status that includes the last thing i typed to the llm. I also have hotkeys to launch cursor, embedded lazygjt, tower, or jump to the pr in the browser. I integrated linear and can create a task from the linear ticket and pull the ticket and all the comments into the context. People keep telling me i should add audio alerts, but i never have to step away. If everything is yellow i just start a new task.
I've seen this first hand and yes, it's not sinister, getting dozens of services coordinated and permissioned under a single, easy to use, system is too much cognitive load for the team that inevitably gets tasked to do these things. Think about Privileged Access Management or Active Directory, but an 8 year old has to get it to work with a stay at home mom's 5 year old android device, and the PM's working on it can't think through second order effects (or even first order effects sometimes). And of course anything that negatively affects metrics will get rolled back (that part might be sinister).
That was it! Theres a little Add a Control prompt at the bottom after the long press and I found the bell. Thank you. Huge oversight from the dev team, dang.
I feel like people are either arguing in bad faith, or we’re trying to talk to fish about the water. Its so obvious to me that people are going to get their identities stolen and the internet is going to get so much worse that I can’t understand how someone would think otherwise.
TIL I don't know how to “unmute” my device anymore. My new-ish iPhone doesn't have a physical switch on the side and I can’t find it in the settings in the pulldown menu.
This doesn't dignify a reply, but the parent comment was about avoiding data loss because of crashes, and the saving is just good hygiene if you’re making frequent commits, formatting on save, etc. one less thing to think about, one less mistake made.
Yeah no. The reason we don't write code in config files is that, if we did, in order to know what you are deploying you have to run the code in your head. Not just this code, the code that Steve wrote six months ago before people noticed he was grossly incompetent and fired. Also worth mentioning, I can run this code in my head. The author can run this code in their head, but not everyone can. And finally, if the author thinks copy pasting yaml files cause bugs, wait till the llms start copy pasting the for loops.
Do you think it's weird that ethnic groups separated by thousands of years of evolution came up with completely different gods and forms of worship? If there was an omniscient being don't you think it would make itself known in a little more universal fashion? And isn't it strange that the institutions built around our current iteration of God are soft power structures that wield huge amounts of influence both financially and politically?
Do any of these vibe coding tools write out the prompts as specs and then keep the specs up to date as you continue prompting? Seems like specs == formal prompts.
My parents didn't get me a nintendo when I was a child. My socialization also suffered, but I ended up with a job making AAA games and they did not so I consider it a fair trade now that I'm older.
If you're validating parameters that originate from your program (messages, user input, events, etc), ASSERT and ASSERT often. If you're handling parameters that originate from somewhere else (response from server, request from client, loading a file, etc) - you model every possible version of the data and handle all valid and invalid states.
Why? When you or your coworkers are adding code, the stricter you make your code, the fewer permutations you have to test, the fewer bugs you will have. But, you can't enforce an invariant on a data source that you don't control.
Except you can’t transport it. We built a giant cave for it in the desert and everybody agreed that the material was too dangerous to drive past people’s homes so we just leave it sitting around on site hoping a natural disaster doesn’t wash it away. I’m pro nuclear but we need to be honest with ourselves.
Then in the code there’s a bug that over/under reports those clicks (because ui is not procedural code that lends itself to straightforward metrics) and i think this could explain Spotify’s product decisions.
"When I say literalism, I don't mean realistic or plainly literal. I mean literalist, as when we say something is on the nose or heavy-handed, that it hammers away at us or beats a dead horse. As these phrases imply, to re-state the screamingly obvious does a kind of violence to art. "A point is still a point!""
Hope this is helpful.
[0]https://www.newyorker.com/culture/critics-notebook/the-new-l...