Most software engineers are facing an identity crisis bordering on depression.
As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.
The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.
The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.
This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
@plannotator is great, but as an nvim tryhard, I wish there was a keyboard centric way to navigate. tbh an nvim plugin would be my ideal interface. Is anyone building this?
@badlogicgames Features include:
- /pin [label] to pin the last assistant message
- in /tree, pin/unpin messages with shift+P
- in /tree, filter pinned messages with ctrl+P
- in /tree, preview full messages with ctrl+V
- almost guaranteed bugs in future pi updates because of the hacks to /tree
Inspired by this, I had @badlogicgames's pi create a pinned messages extension. Then I committed terrible code crimes and shoved it into the /tree UI.
I present pi-pinned-messages
https://t.co/UZyoWdzd4v
I want the following in Codex, Cursor, and OpenCode...
1. Pinned Messages: Let me pin assistant messages to the sidebar for things I want to keep track of but am not ready to address yet. Render as a checklist & jump navigation.
2. Notes: Give me a scratchpad for thoughts while working.
@thomaspaulmann@byronrode@xeophon@raycast it’s not uncommon for my AI chats to error and need a retry. I’d like local dictation so I don’t have to worry about yapping for 2 minutes straight and then see I had a network error.
@peduarte@raycast This discourse must be frustrating when you finally get your hard work in users’ hands. Angry nerds will be loud, but I’m sure your metrics will show very few beta users switch back to v1.
@zeddotdev Started using terminal threads today and it unlocked a whole new workflow (multi workspaces and worktrees). It's awesome. Now... if we can get a hook so terminal agents (pi) can add a badge when it's done 🔥
@zeddotdev Please tell me this will be available to more than just CC. I use pi and so much of my workflow isn’t supported by ACP so I just use the terminal.
@peduarte I saw this and thought, "Oh I'll replace the stock calculator in my control center with Raycast's and never use stock again!" ...Was bummed to see it's not a control option.
@badlogicgames Opus is so bad about committing and pushing, I had to (ask pi to) make an extension to catch when it tries to do it and get permission first.