• 0 Posts
  • 15 Comments
Joined 5 months ago
cake
Cake day: October 17th, 2025

help-circle


  • Maybe my LLM detector needs an update, but only the headline triggered it. The article did the opposite for me.

    Anyway, the author checks out, old github profile etc. Works in high frequency trading, which I despise because I think it is make-do work, moving money around a millisecond before anyone else has a chance, a huge technical effort with zero benefit to society compared to slower trading. I’ll file it together with adtech and bitcoin. But. The article is not about that. And I know that working in high frequency trading sure makes you qualified to talk C++ or FPGAs or anything close-to-the-metal. So, author background checks out. Verdict: not slop.




  • Yes but despite the footguns, C (not C++) is a relatively small language, not too hard to learn. And it’s the glue between kernel, system libraries, and all other languages. You don’t want to write big applications in it any more, but it’s still useful to know when you interface with existing stuff.


  • Depends. I would flag it in a code review on our product, and same for most TODO comments. It’s bad practice to leave them for your team to deal with, or even for yourself two years later.

    But for explorative coding (mostly just one person, things like game development or creative coding, or before finishing your branch) I think dead code warnings do more damage than they help. They make you look at things not worth looking at right now, until you figured out what you want to build. Like unused structs or imports just because you commented out some line to test something. I didn’t turn all annoyances off, but I feel I should. I have a hard time just ignoring them. I think it’s better to enable them later when the code is stabilizing, to clean up experiments that didn’t work out. When I just ignore them I also ignore a more important warnings, and waste time wondering why my stuff isn’t working while the compiler is actually telling me why.

    Also, in Rust many clippy defaults are too pedantic IMO, so I turn them off for good. Here is what I currently use:

    [lints.rust]  
    dead_code = "allow"  
    
    [lints.clippy]  
    new_without_default = "allow"  
    match_like_matches_macro = "allow"  
    manual_range_patterns = "allow"  
    comparison_chain = "allow"  
    collapsible_if = "allow"  
    collapsible_else_if = "allow"  
    let_and_return = "allow"  
    identity_op = "allow"  # I'll multiply by one whenever I like!  
    # Just disable all style hints?  
    # style = "allow"  
    








  • That’s a good article. Here is a related deep dive: Pineapples! (PDF)

    Because the pineapple leaves close their stomata during the day they don’t have the benefits of evaporative cooling! Plants heat up and unless there is a breeze to move the heat out of the field they are prone to plant damage, fruit sunburn and “cooking” or “boiling”. Growth slows when temperatures exceed 36°C and stops at about 40°C.