I’m making a baby book for my son Henri featuring famous Henri’s through history.

I’m also building a zigbee free/busy eink display that only needs to powered once a year or so

Smoking is terrible in that it really messes with your brain, you intellectually know all the reasons why you should quit but it’s so easy to put it off. “I can quit whenever, I just don’t want to”. Until you try and get that gnawing yearning feeling.

It took me a solid year to not feel that way all the time. And another two to not feel that when having a coffee/glass of wine/standing next to someone else smoking.

13 years later I’m completely over it, to the point where I can barely tolerate being in the vicinity of someone smoking. And yet I often have dreams where I light a cigarette.

If you’re thinking of quitting, there is no better way than today. It’s likely going to be hard, but it’s one of the best things you can do to yourself. You already know that of course, but hopefully this helps.

Comments URL: https://news.ycombinator.com/item?id=46722463

Points: 11

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46517110

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46449164

Points: 8

# Comments: 1

The overall approach I now have for medium sized task is roughly:

- Ask the agent to research a particular area of the codebase that is relevant to the task at hand, listing all relevant/important files, functions, and putting all of this in a "research.md" markdown file.

- Clear the context window

- Ask the agent to put together a project plan, informed by the previously generated markdown file. Store that project plan in a new "project.md" markdown file. Depending on complexity I'll generally do multiple revs of this.

- Clear the context window

- Ask the agent to create a step by step implementation plan, leveraging the previously generated research & project files, put that in a plan.md file.

- Clear the context window

- While there are unfinished steps in plan.md:

-- While the current step needs more work

--- Ask the agent to work on the current step

--- Clear the context window

--- Ask the agent to review the changes

--- Clear the context window

-- Ask the agent to update the plan with their changes and make a commit

-- Clear the context window

I also recommend to have specialized sub agents for each of those phases (research, architecture, planning, implementation, review). Less so in terms of telling the agent what to do, but as a way to add guardrails and structure to the way they synthesize/serialize back to markdown.

Arguably there might be more curious tinkerers nowadays, but they might represent a smaller slice of the pie.

This being said, Sweden is a fun one: I was in Copenhagen for a few weeks and I thought it’d be fun to take the train to Malmo, do my long run, and then take the train back. All that to say, I’ve spent 3h30 in Sweden, 3h05 of which I was running.

Shanghai was an overnight layover.

The actually awful runs I’ve had are more of the "type 2 fun" kind (running in the desert, grueling trail runs), or the occasional hungover run before I quit drinking.

Thankfully the ablation took care of them and I haven’t had an episode in a few years.