HN user

mdrachuk

123 karma
Posts19
Comments56
View on HN

It’s all good until your production agents deployment has a single 9 uptime. I use Claude Code as my main coding harness daily but making customers reliant on Anthropic software is a big no-no. Quality engineering is just not their thing.

From the tweet:

New in Claude Code: Remote Control. Kick off a task in your terminal and pick it up from your phone while you take a walk or join a meeting. Claude keeps running on your machine, and you can control the session from the Claude app or http://claude.ai/code

Why I code as a CTO 9 months ago

Your job at the top is, more than anything else, pushing down a healthy culture. The CTOs role leading the tech folk to support business goals, which culture a part of. The healthy part is a subjective thing.

You can see this in practice when you use Claude Code, which is pay-per-token. Our heaviest users are using $50/month of tokens. That’s a lot of tokens.

How is your usage so low! Every time i do anything with claude code i spend couple of bucks, for a day of coding it's about $20. Is there a way to save on tokens on a mid-sized Python project or people are just using it less?

I’ve never thought like this, but I definitely acted like this. Feels like these two approaches are both part of human nature. From what I understand before agriculture people actually considered themselves as animals, being part of the bigger system.

Everyone is a creature of habit. So new tools should be tenfold better to kick the habit. Is ripgrep so good? Doubt it, although it’s definitely better.

So it’s actually a smart switch statement.

Seems like it doesn’t create instances when you’re doing

  Node(children=[Leaf(value="("), Node(), Leaf(value=")")])
instead:

1. Node means "is instance of Node".

2. Everything in between () is "has an attribute with value".

3. List means "the attribute should be treated as a tuple of".. etc..

Very confusing, this definitely needs another syntax, because both newcomers and experienced devs will be prone to read it as plain `==`, since that's how enums and primitives will be working.

This syntax goes against Zen: It’s implicit -- when using match case expressions don't mean what they regularly mean. It’s complicated -- basically it’s another language (like regex) which is injected into Python.

I’m a big believer in this feature, it just needs some other syntax. Using {} instead of () makes it a lot better. Now no way to confuse it with simple equality.

  match node:
    case Node{children=[{Leaf{value="(", Node{}, ...}}

1. The fact that the humidity is often too low where I am at. I got a humidifier. Before using this thing I had dry nostrils, but never paid attention to it. Now it’s better.

2. The way cooking affects pm2.5. I don’t have great ventilation in the kitchen, so I started ventilating via windows for a better air quality at home. I do not feel effects of this though.

3. How fast the CO2 levels are rising with closed windows. Since my childhood it was regular in my family to sleep with windows closed, and ventilate maybe couple of times per day. And in the summer time the windows were closed when the air was cooled with a conditioner.

It turns out, that in an hour with closed windows the CO2 level is already higher than what is considered healthy. Nowadays it seems like I can say when room needs ventilation without a sensor, just cause I feel the air is not "nutritious" enough. I do feel worse (tired, slight headache) when not ventilating.