Skip Navigation

Posts
11
Comments
209
Joined
5 mo. ago

  • As I typed it I felt in my bones that someone was going to come along with an example of someone doing exactly that. I kinda hope someone does, I've looked into homegrown silicon and it looks... very difficult and expensive.

  • I don't think it's a binary switch between "understanding" and "not understanding". I have the basic gist of how semiconductors and logic gates work, I know a little about how CPUs and assembly work, and I can work with assembly if I have to, but those aren't my areas of expertise. I know enough about floating point arithmetic that I can identify floating point errors as floating point errors, but I don't claim to have anything close to the fluency in those systems that I do for higher-level languages. The ability to specialize makes it possible to make fantastic machines like the global Internet even though no one person on earth understands all the sub-components to the degree that a specialist in a particular sub-component does. I'm not saying that there aren't some computing systems that are fully comprehended by a single person, but the ability to specialize increases the scope of what is collectively possible.

  • I feel like they kind of lost the thread here, even though I think I agree with the idea that vibe coding is a fundamentally different thing than another layer of abstraction. There's no need to punch on the web developers. We've all known, for the last several decades at least, that we don't have to understand the entire mechanism completely. No one is out there doping their own silicon and writing JS apps to run on it. The whole point of layered abstractions is that you can build on a set of assumptions without having to know all the implementation details of the layers below. When an abstraction leaks, then it can be useful to have some facility with the lower levels, but no person alive is a master of the full stack. The beautiful thing about abstractions is that you don't have to be. That's still true with vibe coding, just with the extra complexity of having a ticker tape spitting out semi-coherent code faster than any human could type it, which moves the dev from a creative role to more of an administrative one, as they mention earlier in the piece, which 1) is not nearly as fun, and crucially 2) doesn't help you build the muscles that make one good at code administration.

  • Yeah I think so. Also checked with another browser and the page seems to be loading fine so I think whatever's making the content disappear is on my end. I'll make an edit.

  • EDIT: as of this edit the Wired page is loading normally, seems to be some plugin interference in my browser. I'll leave this up just in case anyone wants a quick tutorial on how to defeat sloppy censorship, even though I don't think that's what's happening here.

    --- ORIGINAL POST ---

    Thanks for copying the info. The mirrors are 429ing, and if I just open the Wired article, I don't see the contents of the article, just the headers and footers.

    Not sure if this is Wired's attempt at a takedown or if I just have a bunch of plugins interfering with their site, I don't visit often. However, the body of the article is still appears to be there in the page source. You can open the inspector by right-clicking and (in Firefox) clicking "Inspect", then search the page source for your city.

  • They're just trying to protect your beautiful eyes from the harsh world ❤️ Chin up, it'll make your brows seem taller.

  • I'm still working on my first one, apparently :/

  • N0o one is happy about this.

  • I am so mad right now

  • haha same. I went years knowing from technical osmosis that it meant "supporting other languages" but I never knew what it represented or why it had numbers in it. There are so many acronyms in tech I think inevitably some of them fall by the wayside for everyone.

  • Still at a loss as to what ""Sk8er Boi" is short for.

  • Bet

    Jump
  • frfr

  • Scientists are often criticized for giving prosaic names to the things they discover but I think they really knocked it out of the park with time crystals.

  • It insists upon itself.

  • I want to make a documentary about a guitar player who lived hard and died young just so I can name it "Struts and Frets".

  • It often is, but this poem isn't about the kind of death that includes an afterlife. That's just more life. This is an exhortation for nonexistence. I think that's what makes the volta tricky, is that the speaker knows exactly what they're asking for from the jump. Which I think is what makes it feel kind of like a prayer, the old school Catholic kind, not the non-denominational invocative freestyling where people just say whatever they want to god. When I was a kid we got all our prayers pre-written from the church, and those were the prayers we said. Feels... genre bending to have realizations in the middle of prayers, lol.

  • I don't set out to write sonnets, but I keep getting pulled in that direction. Three quatrains is a good length for a poem, I think. I also spent a lot of time trying to think of a good couplet to put at the end because I feel, for some absurd reason, that it "should" have a couplet, but I can't think of one that fits the tone. Couplets just feel too cutesy and rhymey for a topic as super serious as the shuffling of the ole mortal coil.

  • Right, I guess I'm more taking issue with the article than with you, because the "trail" is always documents, and it's pretty easy for LLMs to fake documents. I mean, humans have been half-assing verification checks for decades, and it has kind of worked because even half-assing a verification document has required at least some fluency with the code under test, which in turn has required the engineering team to develop enough understanding of the code that they can maintain it, just to produce plausible verification trail documents. Now, the relationship between plausible documentation and a dev's understanding of the code being verified is much less reliable, so we need more precise mechanisms. In other words, the signals of trust have always been broken, it's just that it hasn't been a problem up until now because there were side effects that made the signals a good-enough proxy for what we actually wanted. Now that proxy is no longer reliable.