HN user

z33k

154 karma
Posts3
Comments49
View on HN

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.

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

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.

4 years ago I was 100kg @ 185cm. Never touched PEDs. All it took was being in the gym going all out for around 2 hours, 6 days a week. My body fat was 13% consistently. I tried going below 13% until it started to affect my strength.

The rest of my life also revolved around recovery and nutrition because very quickly I realized that I needed to make extraordinary efforts to allow my body to recover from the regimen. I slept 10+ hours and ate around 3300 cals daily (TDEE was massive).

Being on antidepressants at the time made eating these amounts much easier, as it seemed to turn off something in my brain responsible for me feeling satiated.

I started gym after being diagnosed with the psych issues. I really put 110% effort into it and got… big stretch marks because my muscles grew so fast. I don’t think what I was doing was ”healthy” as much as it was ”I am super depressed and heavy barbell squats is my coping mechanism”.

I just wanted to say, you don’t need PEDs to get ”scary” jacked. But you probably need to be crazy like me.

SSH Remoting 2 years ago

For what it's worth; Visual Studio Code and VSCode are not the same. VSCode is MIT licensed: https://github.com/microsoft/vscode/blob/main/LICENSE.txt

From vscodium.com:

Microsoft’s vscode source code is open source (MIT-licensed), but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license

The VSCodium project exists so that you don’t have to download+build from source. [VSCodium] includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.

MyBB PHP forums have a web interface through which one can download the database as a single .sql file. It will most likely be a mess, depending on the addons that were installed on the forum.

You’re able to aggregate all logs from control plane (all events?), firewall/ ingress, Storage, Autoscaler , CNI, operating system, audit events?

”If you don’t love your logging system, proactively fix that problem.”

Really, you have a ”one-system” where you can see _ALL_ the logs? I don’t believe that. This whole software thing is abstractions everywhere, and we are probably using some abstraction somewhere that isn’t compatible with this fabled ”one-system”.

Often the most debugging takes place on the least observable systems.

Interesting- my first time reading about Kamal. I personally used watchtower (https://github.com/containrrr/watchtower) to check for and deploy container updates from the GitHub Container Registry and push new images there from Actions. I also used OpenTofu to automate the VPS provisioning in GH Actions. It would be interesting to read about self-hosted/ free monitoring & analytics solutions for this stack.

This is why we need labor unions. The power dynamics are almost universally stacked in favor of the employer. Unions can equalize this to an extent. You will still be disposable, but at least you will get better terms if you end up getting disposed of.

I think you're right. In fact, that's the stack I would recommend right now to a new (web) app developer. Write your own Dockerfile, some terraform to spin up a docker host on DO, and a bit of GH Actions yml to pass secrets, build dockerfile, upload to container registry, terraform apply. It's a fun weekend project. It's interesting how many ways there are to "build your own PaaS".

Great point. In my opinion it is possible and maybe even ideal to do both: make it easy for anyone to run their own service while also running your own service so that users have the option to not have to manage the data, patching and ops side.

I have a lot of ear protrusion, which is even more notable due to my large ears. Having seen old pictures of my great grandfather last weekend, it seems clear whose genes for large protruded ears I inherited.