z33k

Good luck migrating the ”forge” part with the ”git” part. Your github org settings, pull requests, rulesets, CI/CD pipelines, containers, copilot... The lock-in always comes from the ”forge” part, never the ”git” part.

The pyrovalerones are basically the fentanyl of meth. More potent, shorter lasting, more dangerous.

What's wrong with OpenTofu and cloudinit?

Amiibo and Skylanders detect the pieces with NFC. Wiring up the whole board/ terrain with NFC readers would probably be difficult, though.

As someone who went to work for a commercial software consultancy company early in my career, I am looking to follow in your footsteps. In consultancy, projects are over for me when my work is done. Rarely do I get to see the results. I want to work at a product company next.

You need to use the features that Claude Code gives you in order to be successful with it. Your build and tests should be in a Stop hook that prevent Claude from stopping if the build or tests fail. Combining this with a Stop hook that bails out if the first hook failed n times already prevents infinite loops.

With anything above a toy project, you need to be really good with context window management. Usually this means using subagents and scoping prompts correctly by placing the CLAUDE.md files next to the relevant code. Your main conversation's context window usage should pretty much never be above 50%. Use the /clear command between unrelated tasks. Consider if recurring sequences of tool calls could be unified into a single skill.

Instead of sending instructions to the agent straight away, try planning with it and prompting it to ask your questions about your plan. The planning phase is a good place to give Claude more space to think with "think > think hard > ultrathink". If you are still struggling with the agent not complying, try adding emplasis with "YOU MUST" or "IMPORTANT".

I'm not an astronomer, but my intuition is this: When the source of the light is moving towards the observer, each successive photon emission happens from a position closer to the observer than the previous photon. Hence, from the observer's perspective, the time between photons is reduced, meaning more photons are observed in a given time, and the brightness is increased. When we observe a galaxy that is rotating opposite to us, not only is the source of the light moving closer to us, but we are also moving closer to it.

This idea you’ve presented is immediately visible all around when you know to look for it.

The failure case I see most often is when this thinking is applied to some kind of a wicked problem.

1. The problem is not understood until after the formulation of a solution.

2.Wicked problems have no stopping rule.

3. Solutions to wicked problems are not right or wrong.

4. Every wicked problem is essentially novel and unique.

5. Every solution to a wicked problem is a "one shot operation".

6. Wicked problems have no given alternative solutions.

Source: Dialogue Mapping: Building Shared Understanding of Wicked Problems 2006 Jeffrey Conklin ISBN: 978-0-470-01768-5

How come a fully typed ORM is the devil, if we agree we want a typesafe codebase for our mixed experience dev team? I have had positive experiences with Prisma. It just works.

Worse than not trying is trying and experiencing burnout and/or destitution.

When you fail, it can be due to many things. Not everything in the world is controllable. This is one of the reasons why expecting zero ”What ifs” at the end of your post-mortem is unreasonable.

It's fine in my experience. I use Synergy 1 and I turn off smooth scrolling on my laptops and desktops. I find it more distracting that some apps support smooth scrolling and some don't, so I just turn it off altogether. Together with AutoHotkey on Windows and (Built-in) Applescript and Rectangle on MacOS, one is able to have similar keybinds on both operating systems.