• 1 Post
  • 38 Comments
Joined 3 months ago
cake
Cake day: April 20th, 2026

help-circle



  • I guess, this is different from automating a part of your workflow every so often, in that you don’t yet know the surrounding context. It is the point to just dick around with some new context for a bit.

    And if you get bored of it, i.e. you’ve learned enough about the new context, then you can just archive the repo and move on, because you don’t actually need it as a solution.




  • As a developer, you hold the copyright to your code. When you make it open-source, you grant a license to use the code and the resulting program under certain terms.

    This is a contract. If you copy my code without following these terms, then that’s theft.

    The Internet Archive’s use complies with these terms for all open-source licenses. These AI companies do not. In particular, here’s a quote from the MIT license, which you will find in a similar wording in all open-source licenses:

    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

    https://mit-license.org/

    In effect, what this means, is that when you copy my code, I demand that you also copy the license text along with it, so that anyone else looking at this code knows the permissions I grant and the terms I require.

    And now guess what these AI companies are doing. They copy my code and reproduce substantial portions upon a user asking, yet they do not include my license terms. They violate the contract under which they obtained my source code.

    I suspect you don’t realize how shit that is, because source code is so abstract.
    It’s like spending hundreds of hours painting a great artwork and then deciding that everyone should be able to give a copy to everyone they know, under the simple condition that they inform those people that they have this right as well.
    And then comes along a company and sells my artwork for money, without informing their customers that they can pass it on for free. That’s, plain and simple, a criminal operation.


  • I think, something to be aware of is that it’s not just shade. It’s not just cooler below the tree. Trees also store and evaporate water, which cools the whole area. This summarizes the cooling effect quite well:

    Tree implementation reduces peak monthly temperatures to below 26 °C in 83% of the cities. Trees can lower pedestrian-level temperatures by up to 12 °C through large radiation blockage and transpiration.

    https://www.nature.com/articles/s43247-024-01908-4

    And well, ultimately if we accept that climate change is a thing, planting trees now is the cheapest investment we can make to combat the heatwaves in 10+ years from now.
    It will reduce heat deaths. It will reduce AC costs of everyone living there. And it will mean that the city doesn’t lose out on taxes from people choosing to stay inside during a heat wave.




  • if you know how to write decent C, you’ll have a much easier time of understanding PostgreSQL internals, for example, while if you’ve learned React, it’s anyone’s guess as to whether or not that’ll actually improve your HTML skills, for example.

    I mean, there’s also a much more mundane reason why C comes up more often: It doesn’t use a runtime environment, so a library written in C can be called from virtually any programming language.

    For the longest time, if you wanted to write a cross-language library, C and C++ were pretty much your only choices.
    Rust is now entering that circle and I do think, it will start showing up in lots of places, too.

    But perhaps another reason why mastering C is more educational than mastering other languages, including Rust: C hardly abstracts from how the hardware works, so you’re not just mastering C, you’re also mastering hardware.

    Other programming languages ultimately get executed on that same hardware as well, even if lots of abstraction layers are in between, so that knowledge still keeps being relevant every so often.


  • Kind of weird that this is now just how we depict a T-Rex. Like, we know that the thing likely had feathers. This meme specifically references that it was the ancestor of a bird. Surely anyone who gets this meme wouldn’t be surprised that the T-Rex had feathers.

    But if you actually depicted it with feathers, then no one would know that it is a T-Rex that you’re referencing. You have to depict it naked for the meme…







  • Yeah, I thought the blog post was gonna be about horror stories, because even the greatest senior/architect/whatever will push absolute garbage into your codebase, if they don’t have the time to familiarize themselves with how the code actually works.

    Even if it’s some isolated component, if they implement it without explaining the what and why to others, then no one else can maintain or debug that. And you do not want to rely on your super important guy to have the time to fix things when production grinds to a halt.




  • 5 minutes sounds like way too much, unless you mean a fresh compile. But then you shouldn’t need to wait that long between changes, since incremental compilation should kick in then.

    And like sure you can break shit up into crates to speed up compilation, but to do that you already have to have a design you’re happy with and that’s stable.

    I mean, if you have your modules structured in a tree structure and with proper visibility, then it isn’t a particularly big leap to put it into a separate crate. You just move the files, maybe fix some visibility modifiers still, and then a bit of boilerplate to add it to the workspace.

    It’s only really when you’re publishing to crates.io, that you don’t particularly want to keep changing the names/scopes of the crates, as they’ll stick around on there for the foreseeable future.