With plain bins, you don't get the "this tool can only be stored there" lemma that changes how you think when you have a lot of tools. If a tool has only one place to go: 1) either it's there or it's used on a work surface, 2) it goes back there and not in a possibly-related dump (does this special double-sided tape go with all the tapes or with the leatherworking supplies?)

For other Gridfinity content:

  - Generate a specific bin for your tool: https://www.tooltrace.ai/
  - Generic bin generator: https://gridfinity.perplexinglabs.com/pr/gridfinity-rebuilt/0/0
  - Hub for links: https://gridfinity.xyz/

What I infer from Anthropic post is that they will estimate the energy price as if they weren't using it and pay the difference if their use upped the price.

You'd need that kind of sharp rules to compete against unhinged (or drunken) AI drivers and that's unfortunate. But at the same time, letting people DoS maintainers' time at essential no cost is not an option either.

It sets up a Windows machine in Docker where you can install your apps, then you'll get .desktop applications that starts the program in the VM and use RDP to only show the app window – it feels nearly native. I've even bought an Office 2024 license to improve some VBA Excel macros for a client.

However I agree with other comments that the author's baseline of 380ms is suspicious. I get 150ms (full config, 6 plugins) vs 50ms with no config and plugins.

Look at Souper Cubes (or any silicon knockoff) for the molds.

I have broad market ETFs and would like to avoid the transactions fee of de-investing everything. Also I'd like to have market exposure, just not as correlated with AI ups-and-downs.

Do you have a plan to protect your investments if/when the AI craze calms down?

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

Points: 2

# Comments: 1

I'd say HN had a big part in shaping and honing my critical thinking.

  - telling clients that the proof-of-concept is non-conclusive so it's either bag it or try something different
  - spending innovation tokens in something else than a new frontend framework and/or backend language
  - understanding that project management methods are tools (not rites) and if your daily standup is 45min then there's a problem

Soothing experience :)

(Side ask to people using Jujutsu: isn't it a use case where jujutsu shines?)

- breaking through the analysis paralysis by creating the skeleton of a feature that I then rework (UI work is a good example)

- aggressive dev tooling for productivity on early stage projects, where the CI/CD pipeline is lacking and/or tools are clumsy. (Related XKCD: https://xkcd.com/1205/)

Otherwise, I find most of my time is understanding the client requirements and making sure they don't want conflicting features – both of which are difficult to speedup with AI. Coding is actually the easy part and even if it was sped up 100x a consistent end-to-end improvement of 2x would be a big win (see Amdahl's law).