My first ban was 3 weeks ago after 5 months of usage.

And ban came after 6-8 hours of last session. My guess they didn’t like that I asked to verify RCE opus found, so he made workable exploit.

Everything else similar to your workflow, no token maxing and etc.

Then, just do not add text that adds no value. Less is more.

Documentation is first part people see when presented. I personally hate AI written text even though I do agentic engineering a lot as well. Any user facing documentation must be reviewed, if you snoozy by reading it - remove or rewrite.

I do not care about paragraph long comments in code, because I’m not gonna read them, but I still follow my internal guideline and cut all this verbosity to level where it readable using hooks and skills.

So basicly like you said if you care about product do not add placeholders. It’s take away first impression.

They all within same close tied frequency range, so it’s pretty easy. Though L1,L2,L5 need separate jammers if you only target GNSS

I surprised how many people don’t even read their own PR commits and diffs, like at basic level.

So many don’t even bother to tide-up fold their commits into single logical change, consider how many commit agent doing, seems logical to have folded commit history when you open PR.

Default commit and PR body text is word salad didn’t seems to bothered these people. Because if it did they already had hooks and skills to make it look tidy and lack of any AI attribution inserted.

I don’t even consider myself developer more like really weak devops guy, but I was already doing all of that.

I found both models produce word salad for PR bodies by default. Same thing with commits messages.

I had to create hooks that invoke skills when pushing new commit and open PR body text.

I made a skill which is maybe why GPT is doing okay but Claude seems to straight up ignore it (it invokes/reads it but doesn't follow the directions)

I found using just skill isnt enogh. You have to bounce its turn and inject skill text to actually follow instructions 100%.

Because even if you use PreToolUse hook and don't bounce it, it will never work since skill text is injected when along with text that already perpared to it need to be edited.

Not really. Co-signed is part of system promt that injected by harness.

lots of low end switches use RTL837x series as basis nowadays

its basically AISC plus microcontroller - https://svanheule.net/switches/rtl8370

I love https, but I also hate that its basically killed on-site caching and give CDNs more power as its only way to distribute content closer to user

First time, eh? I remeber namecheap had problems 10 years ago when they upgraded interface and something was wrong with dns srv records. So i had to move out to gandi at time