The Discipline of Code: Engineering Backlash Meets Tiling Terminals
As engineers push back against the tide of LLM-generated complexity, terminal minimalism and voluntary protocol conventions find fresh momentum across the network.
A sharp skepticism toward conversational code generation broke across developer circles today, as the industry rush toward prompt-driven development met resistance from systems engineers weary of runaway complexity and opaque abstractions.
The critique was articulated by systems engineer Nour, who questioned the long-term viability of delegating software comprehension to statistical language models: Waste of time hearing a Viber scream.
Reflecting on the accumulation of uninspected dependencies and imprecise specifications, Nour warned: The amount of insanity about adding more complexity, not reading or even understanding what a software you build does, using English as a language, not being explicit, building shit load of crappy apps, ... is beyond me.
The danger, Nour observed, is a generational loss of technical mastery: If everyone moved to building on top of vibe coded libraries and OSes we are fucked in the motherboard because nobody knows shit about that spaghetti generated by LLMs trained on stackoverflow tutorials.
(Nour).
Yet across the network, developers building focused consumer utilities demonstrated a pragmatic alternative. Rather than leaning on sprawling web frameworks, engineer notmandatory noted that automated assistants could help assemble lightweight terminal user interfaces: This is the way… I've been playing with the ratatui (rust) and the 🤖s have built me some nice little TUIs for data entry and display.
(notmandatory).
The pursuit of keyboard-driven precision was echoed by IT veteran Derek Ross, who documented his transition from decades of conventional graphical environments to Omarchy, an Arch-based Linux desktop built on the Hyprland tiling window manager. Recalling the initial friction, Ross wrote: There was no dock. My windows refused to be dragged. Everything tiled itself whether I asked permission or not. My first honest thought: this is broken. My second, more honest thought: this is a different paradigm, and the problem is my muscle memory, so I had better learn it.
After twenty years of administrative computing, Ross found that abandoning floating desktop clutter unlocked a faster workflow: Stop arranging windows. Start assigning workspaces.
Within days, the muscle memory shifted: Twenty years of dragging windows, retired in a week. I still catch myself reaching for a dock that is not there. Then I hit Super + 2 and stop missing it.
(Derek Ross).
At the protocol level, architectural clarity required solving cross-application coordination rather than multiplying features. Protocol developer lostcause outlined a framework for Nostr Community Conventions (NCCs), designed to bridge the gap between core NIP protocol specifications and isolated application silos: Two applications can both use valid Nostr events, valid signatures and valid relays, yet still be unable to understand each other because they chose different ways to represent the same higher-level idea.
Rather than overburdening base relays with bespoke governance, NCCs propose an optional layer of shared conventions: A NIP describes part of the Nostr protocol or a broadly reusable protocol extension. An NCC describes how applications can compose existing pieces into a higher-level convention.
(lostcause). Meanwhile, independent desktop tooling gained speed as reya rolled out an updated preview of Signed: I've pushed a new release for Signed, still very early but I've laid out a solid plan and direction, so development progress will speed up a lot.
(reya).
