[XenophileJKO]

Actually please write an article about how you are currently using it then. I've been actively using it and working with sub-agents. I feel like there are very little resources out there on more complex Claude Code setups.

I would love to see other setups, like what MCP, hooks, sub-agents, commands, etc.

[AndyNemmity]

.

[ToJans]

Wow, that is a huge instruction set.

I've created a (way smaller) "/hire" command that does something similar, but I should probably turn it into an agent as well, as the commao is only creating agents, and I still need to do further adaptation with individual promoting and edits

It's these little, but crucial insights that make all the difference, so thank you!

I have the exact same feeling about losing time, for me it's starting to turn into an addiction,

I'm buiding a new side product, and the sense of urgency combined with the available capability makes it hard for me to stop working.

Progress is going so fast that it feels like the competition might catch up any time now.

I now restrained myself upfront with predefined timing windows for work, so the I manage to keep my sanity & social life from disappearing...

"What a great time to be alive"

[poisonborz]

The situation is of your own making. You can change/get out any time.

[derektank]

>Apologies, I'm not an article writer. I focus all my time on improving my own setup.

Maybe that's why the guides you see appear a bit out of date? Writing, all kinds of communicating, takes time, both in organizing and compiling your thoughts

[weitendorf]

We’ve been building in this direction for a bit over a year now. I don’t see your contact info but please reach out over email if you’re interested in checking out our approach and maybe working with us!

[AndyNemmity]

.

[weitendorf]

It’s not the specific agent config or anything like that I’m after, just the genuine interest+enthusiasm in an area we’re actively working on. The central premise to what we’re building is our system for reusable and composable AI workflows.

Shit’s moving fast and the math works out such that it’s probably better to just find someone at the bleeding edge and offer to pay them really generously to work with us than to recruit for this work normally. If you change your mind you can find my email on my profile!

Edit for more context: We’ve basically had the same thing as Claude’s slash commands (we call them workflows) since November, but then we switched gears and made our cloud IDE/agent sandbox and other components of our infrastructure layer the top priority.

That’s working and the timing is amazing since we should be able to just glue all these new cli (sub) agents in between our workflows and agent infrastructure. I suspect someone who understands terminal agents well could do it about 4x faster than me.

[AndyNemmity]

.

[XenophileJKO]

Hmm.. I work at LinkedIn.. and I didn't get the magic invite. :(

[gexla]

I think the basic issue for me is that people put this stuff out as if it's some big discovery, and yet my own usage is way different and serves me just fine thank you. These have the feel of a developer who has just discovered development and then want to tell you about all the best tools. But it's not really about showing you the best tools, is it? Rather, it's about riding the hype train and creating slop for more eyeballs.

[weitendorf]

Respectfully, I think you are being reflexively contrarian or overindexing on the vibe coding hype train. The way vibe coding UX works is basically just having LLMs guess what they need to do to complete a task and then sending it off to do it and try to fix anything that doesn't go according to plan along the way. Nothing big there.

I had started working on an AI devtool product a few months before Cursor took off, I didn't even know about them when I first started, and I hated that such a dumb UX was setting the narrative in this space. LLMs had essentially no ability to decompose and plan tasks at the time, and they weren't fucking sandboxing it!

Terminal agents are actually moving towards the UX I've been building/anticipating for. In March of 2024 I was playing around with GPT4 and saw it oneshot a microservice I asked it to make. I was so excited about the implications of where this stuff could go that I quit my job at google just to start building in this space.

Without getting into all the details, I am pretty convinced there must be some particular way of arranging infrastructure primitives and AI-coding tools in a way that properly decomposes and executes arbitrarily large or complicated tasks (limited only by available time and resources). Claude code is IMO getting closer to that by the week. No iterative change is crazy science or anything but there are some genuinely novel and exciting patterns for computing things underway.

[bathtub365]

When someone has a YouTube channel about programming with a certain level of polish they are not trying to be a professional programmer, they are trying to be a professional YouTuber.