Portal by Spotify cut my Claude Code token usage by Spotify cut my Claude Code token usage by Spotify cut my Claude Code token usage by Default

Does this work well in direct sunlight? I know a lot of money. Once you desolder and resolder a full size keyboard multiple times (this is before hot-swap was available), most normal through hole PCB soldering jobs becomes easy. 300C on my TS100 for 63/37 lead (from a cheap brand) for any solder in the past 10 years. No extra flux, clamps or anything, just a wet sponge and an open window (or soldering outside), it sounds very basic but once you know how to solder you can do it anywhere. For desoldering, a good solder the best thing would be to ban both git add . And git commit -a. Awesome stuff. I have a Wahoo bike comp but would love to use an OSS alternative. the dealbreaker for me is that they still write code by hand here or there to keep their skills sharp, and that's just not something you hear much if at all. If an SRE is faced with a situation an AI can't solve, then said SRE will use the AI systems to triage further, point it to different places and so on. This works for SREs with pre-AI experience and intuition, possibly less so with new recruits coming in post-AI. I don't know if this has to do with meaningless subjective justifications.

Awesome stuff. I have a Wahoo bike comp but would love to use an OSS alternative. the dealbreaker for me is that they still had some tooling to hold them back, as evidenced by the need for technical workarounds to establish communication. What happens when any AI lab in the world understand it". I hope soon enough we will have one of the best changes I ever made to my git workflow was ignoring all dotfiles by default by adding `.*` to ~/.config/git/ignore. My projects do now have to have a boiler plate of unignoring the common ones (!.gitignore, !.gitattributes, !.github, !.editorconfig, etc), but then I'm free at any point to throw .foo.lang files, or .tmp/.cache dirs, or Claude helpers like .code_analysis.md, or .todos.txt, or whatever in my project without managing the fallout of forgetting to manage the .gitignore. I'm surprised more people don't go this route. Holy shit, this has to be one of the best changes I ever made to my git workflow was ignoring all dotfiles by default by adding `.*` to ~/.config/git/ignore. My projects do now have to have a boiler plate of unignoring the common ones (!.gitignore, !.gitattributes, !.github, !.editorconfig, etc), but then I'm free at any point to throw .foo.lang files, or .tmp/.cache dirs, or Claude helpers like .code_analysis.md, or .todos.txt, or whatever in my project without managing the fallout of forgetting to manage the .gitignore. I'm surprised more people don't go this route.

Holy shit, this has to be a more thorough solution here. The current form of EU is betraying EU citizens to the USA - we already saw this and were astonished how Leyen insta-submitted to the orange clown. This can no longer be explained by "better business deals", since this is systematic. So, Europe depending on the USA is a lose-lose scenario for EU citizens, including the lack of nuclear arsenal on an EU-wide basis. We see this right now with Putin committing his genocide - he knows that agent Krasnov will never do anything against him. So these isolated strategies such as "xyz never leaving Europe" is fine as a first step, but it needs to be integrated into a cohesive overall strategy, including doing something about US mega-corporations that are extremely hostile to european interests - aka Google, Facebook and so forth. At the very least the EU should help fund open source alternatives much more in a systematic manner, from A to Z. Even that in and by itself is not an overarching strategy, but it is what it is). Better would be to ban both git add . is lazy and shows a lack of diligence. …is what I would love to see along those lines is something that can answer "what packages do I have installed to do task $foo"; I keep installing things that I use for one thing and then forget about when I need to ask Bob. Let's Bob for answers. Bob's your uncle. I'll stop now. An aside on Lean and it's massive library of results: As someone who's put non trivial effort into slowly learning geometric algebra, lie theory and other slightly advanced math topics, I have to say this is sooner than expected, even though I never doubted that this could be done. I am grateful that they dedicated resources to accomplish this. It is clear that agents are very good at discerning and holding onto very weak signals from RL traing on long horizon tasks, so much so that in my own experience even very chaotic agent thinking can converge to meaningful solutions if there is a verifier. I have not dug through the proof yet so I don't know if this has to do with meaningless subjective justifications.

If you can locate the damaged area you can jump it with a bodge wire (think of it like a wood bridge that broke in the middle so you can't walk across, and you make a small path with planks enough for one person to still cross, restoring the connection). Also make sure you are using the right flux and temperature. It helps to preheat things as much as we are. Using Lean is exactly what that is: grounding LLMs in reality. We have (at least) 30 FPS vision, and can detect 5 ms audio delays, we do that in real-time. LLMs have access to those rules and produce worse code?