Preferences

z33k
Joined 153 karma

  1. 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".

  2. 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.
  3. 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

  4. Yesterday (March 5, 2025) there was a headline in the top Finnish newspaper: Shopping malls in Helsinki become a hive of homelessness <https://www.hs.fi/helsinki/art-2000011068519.html>

    When it gets cold, the homeless congregate in the warm interiors of malls. The guards on duty won’t let them sleep there, but they prefer it over being out in the cold.

  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.
  6. The fashionable thing for a while now has been to write your react webapp as a single app. Here is one example of a "fullstack" react template: https://create.t3.gg/
  7. 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.

  8. Only with hardware acceleration turned off. Which in my experience causes a stuttery and laggy experience which can hardly be described as "smooth".

    If you really want to use MacOS's smooth scrolling, use MOS (https://mos.caldis.me) and get a beefy Mac because the base models will stutter like I mentioned.

  9. 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.
  10. 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.

  11. Everyone hates hearing this one: Documentation, documentation, documentation. Programming is a social task. Therefore, everything else related to software development best practices branches off from that.
  12. 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.

  13. 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.
  14. You’re able to aggregate all logs from control plane (all events?), firewall/ ingress, Storage, Autoscaler , CNI, operating system, audit events?
  15. ”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.

  16. 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.
  17. 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.
  18. 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".
  19. You’re absolutely right. In fact, some billion dollar megacorps use fuses as a part of hardware DRM for this reason.
  20. Could you elaborate a bit on what you consider large size? Did you have issues with Vault specifically? In my experience Terraform is the troublesome Hashicorp tool, not Vault.
  21. 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.
  22. 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.
  23. It does imply, however, that citing figures like "$1.72 billion of on-chain transaction volume in the last 24h" in the context of web3's health is misleading or false.
  24. Multiple studies have consistently found the majority of crypto/ dex/ dapp TXs being done by bots.

    2019: https://anchainai.medium.com/our-ai-detects-your-ai-revealin...

    2022: https://twitter.com/messaricrypto/status/1599916553780137985

  25. The ability to easily see and clear the amount of SSD space that images are wasting on my system is probably supposed to attract me to the proprietary Docker desktop application.
  26. Indeed, wrapping basic docker commands in a script feels like wrapping git commands in a script. You’re probably better off learning the commands for this ubiquitous tool.
  27. Also, many commercial crops require to be pollinated by domestic bees that are forced to breed, shipped around and then worked to death. It's principally impossible to have a nutritionally complete vegan diet without forced pollination, but fodder crops do not exploit bees. As a result, human food crops kill five times as many bees as all livestock slaughter combined and directly support honey production (taking excess honey is necessary for colony health). Vegans should also call around and make sure that their seasonally changing food exporters don't rely on insects, terriers, sheep, ducks or organic fertilizers.
  28. 86%[0] of livestock feed is inedible by humans. They consume forage, food-waste and crop residues that could otherwise become an environmental burden. 13% of animal feed consists of potentially edible low-quality grains, which make up a third of global cereal (not total crop) production. All US beef cattle spend the majority of their life on pasture and upcycle protein even when grain-finished (0.6 to 1).

    [0]http://www.fao.org/ag/againfo/home/en/news_archive/2017_More...

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal