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

help-circle


  • None of what you described requires a video. Articles can be written for different audiences, and, in fact, are much more capable of mixed-media content. Text can be selected/copied/consumed by screen readers etc, graphics can be embedded with accessibility information (unlike videos, which can easily contain inaccessible content), images can contain controls that allow one to pan, zoom, etc. and can be separately downloaded, other file types can be embedded with their own controls (including animations, as needed). Relevant related content (like, say, documentation) can be linked inline where it’s referenced, rather than dropping a huge bag of links in a video description. Articles can be indexed, searched, translated, and more. Articles also allow each person to consume the content at their own pace, rather than whatever pace is determined by the person in the video. I personally find videos agonizingly slow compared to how fast I can read.

    Videos are an ineffective mechanism for communication of information, particularly for information that is more complex or technical in nature. They are popular due to the ever-shrinking attention span of people, but that doesn’t mean we should optimize for that.


  • I mean, there’s no real reason laptops shouldn’t like any desktop computer with parts that can be swapped out. Maybe when laptops were first coming on the market with a difficult form factor to work with, but it’s been long enough that modularity should be easy and the default.

    If you can swap out tiny little SIM cards in a phone, you should be able to slot in standardized, smaller form-factor components like RAM, SSDs, etc.

    And by the way, people can and do swap out motherboards all the time for desktops. There is no good reason to need to buy all new components all the time.






  • Actually typing out code has literally never been the bottleneck. It’s a vanishingly small amount of what we do. An experienced engineer can type out bash or Python scripts without so much as blinking. And better yet, they can do it without completely fabricating commands and library functions.

    The hard part is truly understanding what it is you’re trying to do in the first place, and that fundamentally requires a level of semantic comprehension that LLMs do not in any way possess.

    It’s very much like the “no code” solutions of yesteryear. They sound great on paper until you’re faced with the reality of the buggy, unmaintainable nightmare pile of spaghetti code that they vomit into your repo.

    LLMs are truly a complete joke for software development tasks. I remain among the top 3-4 developers in terms of speed and output at my workplace (and all of the fastest people refuse to use LLMs as well), and I don’t create MRs chock full of bullshit that has to be ripped out (fucking sick of telling people to delete absolutely useless tests that do nothing but slow down our CI pipeline). The slowest people are those that keep banging their head against the LLM for “efficiency” when it’s anything but.

    It’s the fucking stupidest trend I’ve seen in my career and I can’t wait until people finally wake up and realize it’s both incredibly inefficient and incredibly wasteful.




  • Just because a lot of people are using them does not necessarily mean they are actually valuable. You’re claim assumes that people are acting rationally regarding them. But that’s an erroneous assumption to make.

    People are falling in “love” with them. Asking them for advice about mental health. Treating them like they are some kind of all-knowing oracle (or even having any intelligence whatsoever), when in reality they know nothing and cannot reason at all.

    Ultimately they are immensely effective at creating a feedback loop that preys on human psychology and reinforces a dependency on it. It’s a bit like addiction in that way.






  • No, good engineers were not constantly googling problems because for most topics, either the answer is trivial enough that experienced engineers could answer them immediately, or complex and specific enough to the company/architecture/task/whatever that Googling it would not be useful. Stack overflow and the like has always only ever really been useful as the occasional memory aid for basic things that you don’t use often enough to remember how to do. Good engineers were, and still are, reasoning through problems, reading documentation, and iteratively piecing together system-level comprehension.

    The nature of the situation hasn’t changed at all: problems are still either trivial enough that an LLM is pointless, or complex and specific enough that an LLM will get it wrong. The only difference is that an LLM will spit out plausible-sounding bullshit and convince people it’s valuable when it is, in fact, not.