A lot of people treat altcoin risk like it starts when price drops. I think it usually starts earlier, when you buy something without knowing what would make you exit. If the plan is only "hold until it pumps", every update becomes emotional. A partnership rumor feels bullish. A team delay becomes "still early". A big unlock becomes "priced in". The thesis keeps changing because there was never a real one. The simplest filter I like is asking 3 things before buying. What would prove this idea wrong? What would make me sell even if price is up? What would make me hold even if price is down? If those answers are vague, the position is probably too big or too narrative driven. Not saying every coin needs a 20 page thesis. But if you cannot name the exit conditions, you are not really investing. You are just waiting for the market to decide for you. submitted by /u/CODE_HEIST [link] [Kommentare]
xxsml turns your ugliest URLs into short, branded links — with a QR code and real click data on every one.
PuzzleMoE: Efficient Compression of Large Mixture-of-Experts Models via Sparse Expert Merging and Bit-packed inference
A purported jab of Sony’s physical media phase-out blows up on GitHub itself.
Tarot.Free: Ziehen Sie Ihre Karten für eine kostenlose Tarotlesung - Tageskarte, ja oder nein, Vergangenheit-Gegenwart-Zukunft und Celtic Cross-Spreads, plus eine komplette 78-Karten-Enzyklopädie. Keine Werbung, kein Fang.
A web interactive for generating and exploring quasiperiodic tiling patterns - aatishb/patterncollider
A next-generation test runner for Rust.
There has been a lot said about error handling in rust. There are many different opinions about how to structure your errors, when to use panics, and the role of proc-macros in error handling. Most of the discussion around rust error handling makes the assumption that when an error occurs you either pass the error up to the caller or you try to completely recover and continue on. While this describes many situations, it fails to address all of them. I want to take a different look at error handling and how it can be approached. This is not meant to replace the mainstream miasma of error propogation, it is merely meant to add a new tool in your toolbelt.
