• 0 Posts
  • 19 Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • Tired of this trope. Learning data structures and algorithms is not about memorizing the specifics of some particular algorithm. That’s like thinking that learning math is about memorizing formulas.

    DS&A is about learning *algorithmic thinking" and how common data structures actually work, so you can begin to build a toolbox of things you can use when making your own data structures. Software engineers that are actually good know this shit backwards and forwards, because it does actually come up all over the place (and these are the kind of people that actually write libraries). Even the basic things you learn in school are actually incredibly useful for understanding the implementation details of databases and how query planners and indexes work, for example (very helpful when trying to understand query performance).

    And don’t get me started on just how fucking much directed acyclic graphs come up in the real world. Git? DAG. Any package manager? DAGs. Nix? DAGs. Open Telemetry? DAGs (the main data structure is a tree which is a special case of DAGs, but if you use linked spans, it would form a DAG). Hell, I’m working on something right now that needs to be modeled as a DAG. It’s almost comical how useful they are.

    We should be encouraging people to learn and grow more, not less.


  • It’s not, they are correct. There are so many telltale signs of AI code it’s not even funny. The most obvious being the absolutely garbage comments that people invariably leave in. And the god awful naming of things.

    But it’s more than that. If you’re in this industry long enough, you get pretty good at reconstructing a real author’s thought process when they wrote the code. Part of understanding code is understanding why it was written the way that it was, which means understanding how the author thought. Sure, there was plenty of garbage code and stupid thinking, but it was still thought and usually had its own kind of internal consistency. AI code has no thought process, no reason. It is pure mimicry, an amalgamation of millions of authors all at once. It has no internal consistency. It produces code no human ever would, because it doesn’t make any fucking sense. It’s like reading an alien language, where the constructs it produces are so aberrant to how any human would ever think that it could be nothing but an LLM.

    I definitely can’t tell you everything about a piece of code by reading it, but I sure as hell can smell an LLM in it, because it fucking stinks.






  • I was not talking about your specific lawsuit, or TLS.

    Companies trust other companies all the time, and it’s foundational to most all SLA/SLOs. Any time I’ve voiced concerns around how AI companies are using the data we are giving them (like giving them access to our codebase), it’s brushed off as “we have an agreement with them”. It’s just a load of hogwash. They can and will abuse all data they have access to, just as they have done thus far.

    In this particular case, we are talking about a data center, and it is not at all reasonable to assume that the data that flows to said data center is in any way protected, especially one run by Musk.





  • Did the headline change? The current headline is Torvalds: “100% of Their Code is Written by Compilers” Too

    The title of this post makes for a dumb headline, at any rate. Linus, in response to claims in the industry that projects are now “99% written by AI”, drew an analogy to compilers by saying that all machine code for projects are written by compilers, yet no one says their project was 100% written by a compiler. It’s just talking about stupid hype, which is valid.

    That being said, it’s still quite unfortunate that Linus has fallen into the trap of LLMs.