▲ 3 r/cmux

Is Cmux resource-hungry, or am I doing something wrong

Hi Everyone,

I have been using cmux for quite some time, but lately (I am using version 0.64.20) my CPU is constantly around 100% and cmux is using my battery as a thirsty person drinks a fresh bottle of water... mylaptop battery life is just gone.

I have 6 projects and 2 of them have active Claude Code terminals...

It feels like a bit resource hungrier than I would like...

reddit.com
u/nicoracarlo — 13 days ago

A Love Letter to all of us who are struggling

Browsing this amazing place, I see that lot of us are struggling, one way or another. We are all different, we perceive the world differently and our challenges sometimes don't match. It's ok, we are on a spectrum after all.

I am reaching my 50s and I realised I am an Aspie only very late in life. Yet, understanding why I was different opened my eyes and made my world better. I struggle recognising people's emotions, I misread subtle signals (forget it, I misread any signal that's not spelled out) and I don't really understand my own emotions. It's a maze. I learned to mask the hard way, because I was told so many times I was "wrong" that the only way was to wear a cape, like Batman.

However, I want to send this "Love Letter" to all of you who are struggling right now. Those whose life is at such lows that you don't see the sky any longer. There is hope. There is always hope.
Inside each of us there is a hidden treasure, a rough gem that neurotypical normally don't. For some of us is an analytical mind, for others is the ability to be a grey rock. Whatever it is, if you can't see it in yourself, you haven't looked deep enough or long enough. Or, like me, you did not realise what was absolutely normal for you, was special for someone else.

Experience taught me that mirrors lie. They don't show our bodies as they are, but how we want to perceive them. Our gaze falls on the things we don't like and we miss the gems. In the same way our own perception of ourselves can show us the things we don't know how to do, but fail to see what we can do. I misread situations every day, I speak so bluntly that my words are chipped knives that often land in the back of people I love, yet there are things that are not so bad. In moments of crisis I'm calm, I can spot a narcissist a mile away...

What I am trying to tell you is that you can turn your world around if you surround yourself with the right people, if you pursue your obsessions, if you share your weirdness with those who will enjoy them. The search for those people is long and perilous, a lot of times we will find alone, and sometimes the search will be so tiring we will be tempted to give in.

Don't. Don't give in, keep looking for the weird inside yourself, ask people to show you who they see in you, and keep your hopes up. Don't conform to norms, it's a slippery slope to losing yourself.

This subreddit is an invaluable place to find weirdos like me, and many others who stroll around for a kind word.

The world loves you because you are different, and maybe life gave you a different mental structure because we are meant to be different because uniformity lead to extinction.

You can find your slice of happiness, and I truly hope you do.

reddit.com
u/nicoracarlo — 23 days ago

A Love Letter to all of us who are struggling

Browsing this amazing place, I see that lot of us are struggling, one way or another. We are all different, we perceive the world differently and our challenges sometimes don't match. It's ok, we are on a spectrum after all.

I am reaching my 50s and I realised I am an Aspie only very late in life. Yet, understanding why I was different opened my eyes and made my world better. I struggle recognising people's emotions, I misread subtle signals (forget it, I misread any signal that's not spelled out) and I don't really understand my own emotions. It's a maze. I learned to mask the hard way, because I was told so many times I was "wrong" that the only way was to wear a cape, like Batman.

However, I want to send this "Love Letter" to all of you who are struggling right now. Those whose life is at such lows that you don't see the sky any longer. There is hope. There is always hope.
Inside each of us there is a hidden treasure, a rough gem that neurotypical normally don't. For some of us is an analytical mind, for others is the ability to be a grey rock. Whatever it is, if you can't see it in yourself, you haven't looked deep enough or long enough. Or, like me, you did not realise what was absolutely normal for you, was special for someone else.

Experience taught me that mirrors lie. They don't show our bodies as they are, but how we want to perceive them. Our gaze falls on the things we don't like and we miss the gems. In the same way our own perception of ourselves can show us the things we don't know how to do, but fail to see what we can do. I misread situations every day, I speak so bluntly that my words are chipped knives that often land in the back of people I love, yet there are things that are not so bad. In moments of crisis I'm calm, I can spot a narcissist a mile away...

What I am trying to tell you is that you can turn your world around if you surround yourself with the right people, if you pursue your obsessions, if you share your weirdness with those who will enjoy them. The search for those people is long and perilous, a lot of times we will find alone, and sometimes the search will be so tiring we will be tempted to give in.

Don't. Don't give in, keep looking for the weird inside yourself, ask people to show you who they see in you, and keep your hopes up. Don't conform to norms, it's a slippery slope to losing yourself.

This subreddit is an invaluable place to find weirdos like me, and many others who stroll around for a kind word.

The world loves you because you are different, and maybe life gave you a different mental structure because we are meant to be different because uniformity lead to extinction.

You can find your slice of happiness, and I truly hope you do.

reddit.com
u/nicoracarlo — 23 days ago

RPG: quality VS speed/cost

Hello everyone,

I am a forever TTRPG GM and a software architect/developer. In the past weeks I have been toying with the idea of a RPG AI Assistant to run long-term campaigns. And when I talk about long-term campaigns I consider plots, arcs, locations, scenes, factions and all the bells and whistles you can find in a well-written traditional TTRPG campaign.

Now, in software development it is said you have three variables: speed, low cost and quality. You can have two, not three.

So, I have been toying with a system that handles various agents (a gm, a plotter, a memory retriever and many others) and run some interesting tests. So far, so good.

The challenge is simple: each "round" costs around 5-8 cents ($0.05). While this may not seem much, this is the pure cost of AI calls, meaning that if I were to let other people use this, a single round would cost between $0.15 and $0.30.

My question is: when is quality and game experience too expensive? I don't like playing quick games as I don't like when I have no purpose in a game, but would others?

Ciao

reddit.com
u/nicoracarlo — 2 months ago

How to avoid AI-coding burnout

Hello everyone,

As many of you, for one reason or another, I am using AI for coding (willingly or unwillingly is another discussion). The goal placed on the developers is "being faster" or "being more productive" and everything that comes with this wave of "AI is magic" (true or not).

I noticed that I use AI in two ways, and one of them has massive implications in my mental health, nervousness and sense of dread. Let me start from this one, as it is treacherous.

This is a deep-dive on how I personally (big emphasis here) cope with the added stress of handling two group of children: managers with expectation of grandeur from one side and AI from the other. I hope you find it interesting and/or useful.

Too many parallel tasks, too big, all at once

I found that this is the fastest path to burnout, and I can split it in a couple of ways

  • multiple projects at the same time
  • multiple agents per project
  • big changes per agent

These three things are all cause of problems that lead to one of the symptoms of me going completely crazy, and in the end making me slower instead of faster.

When you juggle multiple projects at the same time, my challenge is the context switching. I ask my brain to move from one logic to another, from one context to another, constantly back and forth. This is mentally taxing and if I do it for too long, I end up in the evening with my brain fried. Every time I move between an app for lawyers to an ERP and maybe a personal TTRPG planner, every step requires re-focussing my attention.

Then there is handling multiple agents for the same project. This is a different type of context switching, a bit easier to manage but requires different steps. When I edit multiple parts of the same project, I generally use git worktrees to ensure I work in isolation. This either means running multiple instances of my project at the same time or stopping one worktree and starting the other. The number of times I got frustrated because a fix was not working, just to realise I was testing the wrong worktree is non-zero 😄

Last, but not least, it is asking an agent to create something too big or that goes outside my sphere of knowledge. This is what brings up my sense of dread, which is the worst state of mind I can find myself in. I have a lot of experience, with almost 30 years of technology/development under my belt, but "I know I don't know" and there are things I have to implement that are simply not in my bag of expertise. AI coding "can" be great for it, because it helps me learn a lot and a lot quicker than before; however, allowing the AI to propose a large chunk of code that includes things outside my knowledge makes my anxiety spike. I fear what will be generated will take a long time to understand, verify, and debug. And when things go south (and if the feature is too big it often does) I tend to reach the end of the day willing to throw my computer out of the window screaming.

Not all is doom and gloom, though, on the contrary. I can leverage my experience to spin agents that do what I need, faster than I would, maintaining the logic of my code. There are a few things I do that help me making the most out of expertise and AI-assisted coding I want to share with you, and I would be thrilled to see if you do things differently, so to try your approach. Please bear in mind that all these work for me, and YMMV.

How do I survive AI coding without burning out and being faster?

There are a couple of things I employ to ensure AI is an advantage and not a burden

1. Targeted tasks

This one is simple. I treat LLM as junior developers. I don't tell them to create an entire application. Hey, I don't even ask them to create an entire feature. What they do is like a small PR. This ease the spec creation, validation, lowers implementation time, limits the possible places in which AI can hallucinate and makes my validation faster.

2. Specs before everything else

Without specs, I don't do anything, no matter how easy a task may be. I use Claude Code and the Superpowers plugin. I found it incredibly helpful for many reasons. First of all it asks a lot of questions, and usually those questions surfaces things I didn't think about. Then I read the specs to ensure my requirements are correctly captured (and yes, I do read them as the more work upfront, the less debug and swearing). Lastly it creates an implementation plan I can verify, and this gives me the possibility to spot logical/code issue before they are written and allows me to learn when I implement things I am not familiar with.

3. Limit parallel working

Either one agent per 2 projects or 2 agents per one project at the same time. From time to time I push to 3. This allows me to select which context switching I can handle: different projects or different tasks for the same project. I find it easier this way.

4. Staggered analysis/implementation/debugging

As I focus on specs a lot, and the mental load for specs, implementation, debug is different, I try to avoid doing two specs at the same time, or two debugging at the same time. This allows me to ease the context switching, as different types of tasks are easier for my brain to handle than multiple tasks of the same time where I find asking myself "Was this the implementation of the new relationship or the one about the new langgraph?"

5. No git commits until I validate

This is very personal and I noticed many people disagree with me. I instruct my agents not to commit to git until I can test it. The reason for this is simple: uncommitted changes are easier to spot and to understand. It's like having to validate a PR: easy to see what was changed, easy to spot mistakes, easy to fix. Once I can look at the changes and test them, I commit. Please consider this works well with #1, as nobody wants to merge a PR with 50 edited files, thousands of lines of code changed and so on...

6. Strong boundaries on my architecture and style

Last but not least, I have a specific architecture in my projects. It is clear and precise, and I need the generated code to respect it. The more the AI respects it, the easier it is for me to validate everything quicker, and also easier for the AI to write less code and reuse what's already available. Alas, making sure the AI respects the architecture is still a WIP, but I am getting there.

Our role is changing, adapting to the incoming wave is critical

In my view, there is no future in which we won't have to use AI to create code. Our role is changing fast, and it is moving us from being developers to being more architects and orchestrator. I don't think we can accept any different future, also because some clients (or employers) are riding the AI-wave so furiously that they believe in unicorns (I don't).

What we MUST do is to protect our sanity to avoid a bout of madness, because trying to do 20 in the same time we did 10 a year ago is a pressure nobody can cope with. I hope me vomiting out the mechanisms I use is going to help others in my position.

Ciao

reddit.com
u/nicoracarlo — 3 months ago
▲ 29 r/rpg

How do you prep for investigative campaigns?

Hello Everyone,

I have been a GM for a LOOONG time, but I am always searching for new ideas on how to better (and quicker) prepare for my games. I run investigative games in a sandbox with some plot sprinkled in.

Currently I use this method:

>(Npc/Location/Faction)-[:CONTAINS_CLUE]->(Clue)-[:LEADS_TO]->(Npc/Location/Faction/Event)

This allows me to prepare a few clues the player characters can find along the way that allows them to decide if to pursue the plot or to go somewhere else. Generally I have a couple of possible alleyways for them to follow, and for each three clues.

Has anyone else designed a way to keep track of their clues in different ways in order to give the player characters the freedom to pursue what they like, keeping the core idea behind your games?

Curious to see if someone has a smarter way of doing this

EDIT: THANKS to all your amazing comments, they have given me so many interesting insights and ideas and I have already started merging them in my process!

reddit.com
u/nicoracarlo — 3 months ago
▲ 4 r/AIClaudeCode+1 crossposts

Hi Everyone,

This post is a personal reflection on Superpowers, so maybe some of you might find it interesting.

A few caveat here:

  • I use typescript and husky to lint before any commit
  • My codebase is rather large (5k tests)
  • I use the Superpowers plugin focus on a limited scope (a small feature, or a bug fix) and I do not ask it to generate an entire codebase in one go

If you are not in the same ballpark figure, this may not help you as it helped me.

So, my only particular step is a prompt I run after the spec has been written and before the implementation plan and I instruct CC/Superpowers to

  • Not run `pnpm test` before the full code has been written
  • Not commit anything to git until I can test it at the end of the implementation

What are the real advantages here?

  1. the implementation is faster, as my tests are heavy
  2. I don't run the husky linting every time CC commits a change
  3. (but this is personal) it is much easier for me to evaluate uncommitted changes

So, the speed (and token savings) stems from the fact that I don't want CC to test every 10 lines of code. CC will write the tests, but will run the tests only once everything else is in place. In a 10 tasks plan I save 9 test runs and 9 additional linting (in my case this is around 20 minutes).

Please note YMMV depending on your codebase, the number of tests you have, your personal preferences, but it helped me quite a lot.

Hope it helps

EDIT: clarifying one message

reddit.com
u/nicoracarlo — 4 months ago