I made no assumptions about you - I simply commented on the post replying to your comment which I liked and simply wanted to follow the point of view :)
The crowd around this pot shows how superficial is knowledge about claude code. It gets releases each day and most of this is already built in the vanilla version. Not to mention subagent working in work trees, memory.md, plan on which you can comment directly from the interface, subagents launched in research phase, but also some basic mcp's like LSP/IDE integration, and context7 to not to be stuck in the knowledge cutoff/past.
When you go to YouTube and search for stuff like "7 levels of claude code" this post would be maybe 3-4.
Oh, one more thing - quality is not consistent, so be ready for 2-3 rounds of "are you happy with the code you wrote" and defining audit skills crafted for your application domain - like for example RODO/Compliance audit etc.
Also if you are using language with more than 24 letters - like you know, most of the world... You can't do {left alt}+n in teams while {right alt}+n works perfectly fine, and I haven't found a way to disable this awful behavior.
Like mate - I'm on Mac, I use CMD+n for new tabs, not windows-like shortcuts...
I second this suggestion. This might sound obvious but during my therapy my psychologist asked me to do this, but in a non-personal/non-threatening way for the relation. Just by telling them that I'm working through my issues and I'd like to get an honest (best would be written/no-interaction type) feedback - what makes them uncomfortable etc.
This helped me a lot - to see how different the transmission was on the receiving end from my intentions.
While these optimizations are solid improvements, I was hoping to see more advanced techniques beyond the standard bulk insert and deferred constraint patterns. These are well-established PostgreSQL best practices - would love to see how pgstream handles more complex scenarios like parallel workers with partition-aware loading, or custom compression strategies for specific data types.
You should check new features - like asking questions as a listener.
I don't use it a lot, but it's useful when you want to have an engaging audio interface to long (50p+) reports, which you wouldn't normally read because it's not your area of expertise or you don't have time, but you can listen while doing some cardio or chores.
OTOH for example the default quota of 55PB (yes, go check it) for your daily limit of data extraction from GBQ is funny, until you make a costly mistake, or some forked process turns zombie.
This is predatory practice, that I can't set up MONEY limits for cloud services.