Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md

hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md

Scheduled Pinned Locked Moved Uncategorized
108 Posts 55 Posters 289 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • thebluewizard@masto.hackers.townT thebluewizard@masto.hackers.town

    @andymoose @cwebber @kkarhan The company then got a problem: Even after hiring a new developer (or two...who knows?), they can't figure out how the code work (no real documents) and, worse, the prompts the original developer wrote is not kept. IOW there is no "source code", so to speak. Disaster eventually strikes the company as a result.

    Ain't that wonderful, huh? *sarcastic tone*

    Multiply that by ten thousands of this scenario across various companies and we got a real economic crisis!

    END

    kkarhan@infosec.spaceK This user is from outside of this forum
    kkarhan@infosec.spaceK This user is from outside of this forum
    kkarhan@infosec.space
    wrote last edited by
    #59

    @thebluewizard @andymoose @cwebber And it's in our best interest for that to happen sooner than later so the fallout for everyone else is kept minimal...

    1 Reply Last reply
    0
    • thebluewizard@masto.hackers.townT thebluewizard@masto.hackers.town

      @andymoose @cwebber @kkarhan The company then got a problem: Even after hiring a new developer (or two...who knows?), they can't figure out how the code work (no real documents) and, worse, the prompts the original developer wrote is not kept. IOW there is no "source code", so to speak. Disaster eventually strikes the company as a result.

      Ain't that wonderful, huh? *sarcastic tone*

      Multiply that by ten thousands of this scenario across various companies and we got a real economic crisis!

      END

      n_dimension@infosec.exchangeN This user is from outside of this forum
      n_dimension@infosec.exchangeN This user is from outside of this forum
      n_dimension@infosec.exchange
      wrote last edited by
      #60

      @andymoose @cwebber @kkarhan @thebluewizard

      So yeah, that's what happens when you suck at vibecode

      1. Write a basic .MD file

      2. Part of the MD file is writing every delta into
      a ./DOCS and ./BACKUPS

      Not only you have every .release you can roll back in source code, but you have every delta in DOCS

      The folks who sucked at being a "real" programmer suck at #vibecode

      P. S. You don't read source code when you vibecode.
      Folks who "WAAAH BUT SAUCE KODE" never vibecoded.

      "Using AI is a learned skill"

      kkarhan@infosec.spaceK 1 Reply Last reply
      0
      • thebluewizard@masto.hackers.townT thebluewizard@masto.hackers.town

        @andymoose @cwebber @kkarhan The company then got a problem: Even after hiring a new developer (or two...who knows?), they can't figure out how the code work (no real documents) and, worse, the prompts the original developer wrote is not kept. IOW there is no "source code", so to speak. Disaster eventually strikes the company as a result.

        Ain't that wonderful, huh? *sarcastic tone*

        Multiply that by ten thousands of this scenario across various companies and we got a real economic crisis!

        END

        tknarr@mstdn.socialT This user is from outside of this forum
        tknarr@mstdn.socialT This user is from outside of this forum
        tknarr@mstdn.social
        wrote last edited by
        #61

        @thebluewizard @andymoose @cwebber @kkarhan And even if they had the prompts, that's no guarantee that the LLM will produce the same output if fed those prompts again. All they could depend on is the raw source code the original dev had generated, no matter how incomprehensible it is.

        The sad part is the company won't blame LLMs for the situation, they'll blame the new devs for not being able to make things work.

        kkarhan@infosec.spaceK 1 Reply Last reply
        0
        • n_dimension@infosec.exchangeN n_dimension@infosec.exchange

          @andymoose @cwebber @kkarhan @thebluewizard

          So yeah, that's what happens when you suck at vibecode

          1. Write a basic .MD file

          2. Part of the MD file is writing every delta into
          a ./DOCS and ./BACKUPS

          Not only you have every .release you can roll back in source code, but you have every delta in DOCS

          The folks who sucked at being a "real" programmer suck at #vibecode

          P. S. You don't read source code when you vibecode.
          Folks who "WAAAH BUT SAUCE KODE" never vibecoded.

          "Using AI is a learned skill"

          kkarhan@infosec.spaceK This user is from outside of this forum
          kkarhan@infosec.spaceK This user is from outside of this forum
          kkarhan@infosec.space
          wrote last edited by
          #62

          @n_dimension @andymoose @cwebber @thebluewizard Granted, "#VibeCoding" is just a different term to "bossing around #AI until it does 50% what it should do and calling that a success when a #Skiddie copypasting shit would've done a better job even when half the amount wasted on *"#AI" Tokens...

          n_dimension@infosec.exchangeN 1 Reply Last reply
          0
          • tknarr@mstdn.socialT tknarr@mstdn.social

            @thebluewizard @andymoose @cwebber @kkarhan And even if they had the prompts, that's no guarantee that the LLM will produce the same output if fed those prompts again. All they could depend on is the raw source code the original dev had generated, no matter how incomprehensible it is.

            The sad part is the company won't blame LLMs for the situation, they'll blame the new devs for not being able to make things work.

            kkarhan@infosec.spaceK This user is from outside of this forum
            kkarhan@infosec.spaceK This user is from outside of this forum
            kkarhan@infosec.space
            wrote last edited by
            #63

            @tknarr @thebluewizard @andymoose @cwebber exactly that!

            Cuz I've seen that shit even with "traditional IT".

            • Ever had to "unfuck" a #ZFS on top of a Hardware-#RAID controller?
              • If you know, you propably already run to the toilet to throw up, because one should not violate THE ONE RULE OF USING ZFS...

            Never ever lie to ZFS!

            1 Reply Last reply
            0
            • kkarhan@infosec.spaceK kkarhan@infosec.space

              @n_dimension @andymoose @cwebber @thebluewizard Granted, "#VibeCoding" is just a different term to "bossing around #AI until it does 50% what it should do and calling that a success when a #Skiddie copypasting shit would've done a better job even when half the amount wasted on *"#AI" Tokens...

              n_dimension@infosec.exchangeN This user is from outside of this forum
              n_dimension@infosec.exchangeN This user is from outside of this forum
              n_dimension@infosec.exchange
              wrote last edited by
              #64

              @andymoose @cwebber @thebluewizard @kkarhan

              "Bossing AI around" is actually a very good description of #vibecoding

              I call it "Hitting the machine with a stick" (like a recalcitant) mule.

              However, the accuracy is significantly better than 50%

              Granted, #Ai will get into the weeds sometimes.

              But because I was a shit programmer before Ai (slow and dim) Vibecoding makes me better.
              There were times I would get stuck on a bug for a day, with Ai, I can mush it in 15 min max.

              In my experience, majority of errors are regex or basic syntax, my Webby got carded last night because the Ai commented out whole anti-carding logic by accident, even though I got it to check it twice.

              Each fuckup makes you write better prompts.

              kkarhan@infosec.spaceK 1 Reply Last reply
              0
              • n_dimension@infosec.exchangeN n_dimension@infosec.exchange

                @andymoose @cwebber @thebluewizard @kkarhan

                "Bossing AI around" is actually a very good description of #vibecoding

                I call it "Hitting the machine with a stick" (like a recalcitant) mule.

                However, the accuracy is significantly better than 50%

                Granted, #Ai will get into the weeds sometimes.

                But because I was a shit programmer before Ai (slow and dim) Vibecoding makes me better.
                There were times I would get stuck on a bug for a day, with Ai, I can mush it in 15 min max.

                In my experience, majority of errors are regex or basic syntax, my Webby got carded last night because the Ai commented out whole anti-carding logic by accident, even though I got it to check it twice.

                Each fuckup makes you write better prompts.

                kkarhan@infosec.spaceK This user is from outside of this forum
                kkarhan@infosec.spaceK This user is from outside of this forum
                kkarhan@infosec.space
                wrote last edited by
                #65

                @n_dimension @andymoose @cwebber @thebluewizard I still think it's #WastefulComputing and doesn't really help oneself to become better at coding.

                • Or not even better at reviewing and testing.
                • At best it'll make one better at documenting requirements.
                  • Basically doing a shitty way to learn "Requirements Engineering"...
                1 Reply Last reply
                0
                • cwebber@social.coopC cwebber@social.coop

                  I mean when I check my feed much of the Bluesky eng team seems to be posting about how great Claude is all the time so I have been background wondering how common vibecoding is in that ecosystem

                  dcoderlt@ohai.socialD This user is from outside of this forum
                  dcoderlt@ohai.socialD This user is from outside of this forum
                  dcoderlt@ohai.social
                  wrote last edited by
                  #66

                  @cwebber
                  Bit of a tangent, but a few months ago, when tech nerds on bsky and fedi started talking about Framework being a milkshake duck, Bsky staff immediately started bragging how cool and fast and powerful their Frameworks are.

                  1 Reply Last reply
                  0
                  • res260@infosec.exchangeR res260@infosec.exchange

                    @erincandescent @cwebber I agree, I think a lot of people don't consider their code craft, but maybe the final product more so

                    benjamineskola@hachyderm.ioB This user is from outside of this forum
                    benjamineskola@hachyderm.ioB This user is from outside of this forum
                    benjamineskola@hachyderm.io
                    wrote last edited by
                    #67

                    @res260 @erincandescent @cwebber if you care about the final product, surely you should care about how it’s made?

                    I see so many apologists for LLM usage recently trying to distinguish between the outcome and the process, as if the quality of the outcome isn’t defined by the process.

                    erincandescent@akko.erincandescent.netE 1 Reply Last reply
                    0
                    • benjamineskola@hachyderm.ioB benjamineskola@hachyderm.io

                      @res260 @erincandescent @cwebber if you care about the final product, surely you should care about how it’s made?

                      I see so many apologists for LLM usage recently trying to distinguish between the outcome and the process, as if the quality of the outcome isn’t defined by the process.

                      erincandescent@akko.erincandescent.netE This user is from outside of this forum
                      erincandescent@akko.erincandescent.netE This user is from outside of this forum
                      erincandescent@akko.erincandescent.net
                      wrote last edited by
                      #68
                      @benjamineskola @res260 @cwebber is this an argument of quality or of morals?

                      Because morals.. people can have different views on. But quality is very much about the end result
                      airtower@woem.menA 1 Reply Last reply
                      0
                      • erincandescent@akko.erincandescent.netE erincandescent@akko.erincandescent.net
                        @benjamineskola @res260 @cwebber is this an argument of quality or of morals?

                        Because morals.. people can have different views on. But quality is very much about the end result
                        airtower@woem.menA This user is from outside of this forum
                        airtower@woem.menA This user is from outside of this forum
                        airtower@woem.men
                        wrote last edited by
                        #69

                        @erincandescent@akko.erincandescent.net @benjamineskola@hachyderm.io @res260@infosec.exchange @cwebber@social.coop If the thing isn't "make once and forget" the process is very much part of quality, because it decides if the thing is maintainable.

                        erincandescent@akko.erincandescent.netE 1 Reply Last reply
                        0
                        • airtower@woem.menA airtower@woem.men

                          @erincandescent@akko.erincandescent.net @benjamineskola@hachyderm.io @res260@infosec.exchange @cwebber@social.coop If the thing isn't "make once and forget" the process is very much part of quality, because it decides if the thing is maintainable.

                          erincandescent@akko.erincandescent.netE This user is from outside of this forum
                          erincandescent@akko.erincandescent.netE This user is from outside of this forum
                          erincandescent@akko.erincandescent.net
                          wrote last edited by
                          #70
                          @airtower @res260 @benjamineskola @cwebber two projects with identical code are, modulo institutional knowledge, equally maintainable; would you disagree?
                          benjamineskola@hachyderm.ioB 1 Reply Last reply
                          0
                          • erincandescent@akko.erincandescent.netE erincandescent@akko.erincandescent.net
                            @airtower @res260 @benjamineskola @cwebber two projects with identical code are, modulo institutional knowledge, equally maintainable; would you disagree?
                            benjamineskola@hachyderm.ioB This user is from outside of this forum
                            benjamineskola@hachyderm.ioB This user is from outside of this forum
                            benjamineskola@hachyderm.io
                            wrote last edited by
                            #71

                            @erincandescent @res260 @cwebber @airtower

                            'modulo institutional knowledge' is doing a lot of heavy lifting there since that's half the problem with LLM usage

                            and the other half of the problem is the assumption that an LLM will produce identical code

                            so I don't think there's a useful discussion to be had if those are your assumptions

                            erincandescent@akko.erincandescent.netE airtower@woem.menA 2 Replies Last reply
                            0
                            • liaizon@social.wake.stL liaizon@social.wake.st

                              @erincandescent @ryanrandall @cwebber its not the same Why. They both have photos of their real face on the internet I checked.

                              davidgerard@circumstances.runD This user is from outside of this forum
                              davidgerard@circumstances.runD This user is from outside of this forum
                              davidgerard@circumstances.run
                              wrote last edited by
                              #72

                              @liaizon @erincandescent @ryanrandall @cwebber this is the one from the mirror universe

                              1 Reply Last reply
                              0
                              • corujosilva@fedi.latC corujosilva@fedi.lat

                                @cwebber before* any judgement on whethe it is a good thing or not, it was expected, tbh. it is very much on brand from their team.
                                they always had the "tech enthusiast" ethos

                                *just before.

                                davidgerard@circumstances.runD This user is from outside of this forum
                                davidgerard@circumstances.runD This user is from outside of this forum
                                davidgerard@circumstances.run
                                wrote last edited by
                                #73

                                @corujosilva @cwebber the team started as coiners, so they were very hot for AI

                                1 Reply Last reply
                                0
                                • november@chaosfem.twN november@chaosfem.tw

                                  @cwebber Ah yes, LLMs are finally good now, this is probably the fourth or fifth time I've heard it and at this point it's like the boy who cried wolf, I'm not even going to bother testing out the LLMs of today to see what they get wrong, I'm just not going to believe their advocates

                                  dzwiedziu@mastodon.socialD This user is from outside of this forum
                                  dzwiedziu@mastodon.socialD This user is from outside of this forum
                                  dzwiedziu@mastodon.social
                                  wrote last edited by
                                  #74

                                  @november
                                  Wait? LLMs are good now? How nobody told me, except swaths of… techbros… …oh wait…

                                  @cwebber

                                  1 Reply Last reply
                                  0
                                  • cwebber@social.coopC cwebber@social.coop

                                    hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md

                                    mkljczk@pl.fediverse.plM This user is from outside of this forum
                                    mkljczk@pl.fediverse.plM This user is from outside of this forum
                                    mkljczk@pl.fediverse.pl
                                    wrote last edited by
                                    #75
                                    @cwebber

                                    RT: https://pl.fediverse.pl/objects/5174b877-5def-4a70-b561-cefdd62c9fa9
                                    mkljczk@pl.fediverse.plM 1 Reply Last reply
                                    0
                                    • erincandescent@akko.erincandescent.netE erincandescent@akko.erincandescent.net
                                      @cwebber @res260 I feel like there's always been a lot of software development that isn't craft but it's just shuffling bits around.

                                      I don't really know how to feel about a lot of it these days. I've played around with some of the tools for work and there's certainly a lot of areas where they can write basically the same code that I would have done with less tedium, and by some metrics they do a better job (mostly things that are good practice but I couldn't be bothered).

                                      Is that abandoning craft or careful allocation of executive function? I don't know.

                                      I definitely think these things aren't going away. The bubble will pop, it'll maybe kill the big AI companies, people will stop shoving chat bots everywhere, but I don't see any way that LLMs don't remain a fact of life, and I don't know what the long term implications are of this
                                      sitcom_nemesis@tech.lgbtS This user is from outside of this forum
                                      sitcom_nemesis@tech.lgbtS This user is from outside of this forum
                                      sitcom_nemesis@tech.lgbt
                                      wrote last edited by
                                      #76

                                      @erincandescent @res260 @cwebber I am no fan of tedium for tedium's sake... but why specifically slop machines, which are notoriously unreliable, to solve this problem, aside from all the money that got poured into this technology? Could the same money have been used to develop languages and frameworks with sensible defaults and configurations, thereby eliminating (or vastly reducing) the need for tedium?

                                      erincandescent@akko.erincandescent.netE 1 Reply Last reply
                                      0
                                      • benjamineskola@hachyderm.ioB benjamineskola@hachyderm.io

                                        @erincandescent @res260 @cwebber @airtower

                                        'modulo institutional knowledge' is doing a lot of heavy lifting there since that's half the problem with LLM usage

                                        and the other half of the problem is the assumption that an LLM will produce identical code

                                        so I don't think there's a useful discussion to be had if those are your assumptions

                                        erincandescent@akko.erincandescent.netE This user is from outside of this forum
                                        erincandescent@akko.erincandescent.netE This user is from outside of this forum
                                        erincandescent@akko.erincandescent.net
                                        wrote last edited by
                                        #77

                                        @benjamineskola @res260 @cwebber @airtower Look, I don’t think we’re talking about (original definition) vibe coding here, where nobody is looking at the output. We’re talking about cases where there’s a human in the loop.

                                        If the tool is generating garbage code and the human is accepting it, that’s a human problem more than a tool problem.

                                        I start from this assumption because we assume the human is competent and has taste. I assume they are not just letting the tool run wild on the codebase and make a mess.

                                        There are issues and questions around institutional knowledge (if the human isn’t exploring the codebase in the same way, how much are they learning? how much do you pickup through review vs implementation?) but even then I’d argue that one of the primary criterions with regards to maintainability is how hard it is for a newcomer to pick something up and work on it.

                                        benjamineskola@hachyderm.ioB 1 Reply Last reply
                                        0
                                        • november@chaosfem.twN november@chaosfem.tw

                                          @cwebber Ah yes, LLMs are finally good now, this is probably the fourth or fifth time I've heard it and at this point it's like the boy who cried wolf, I'm not even going to bother testing out the LLMs of today to see what they get wrong, I'm just not going to believe their advocates

                                          lebramor@piaille.frL This user is from outside of this forum
                                          lebramor@piaille.frL This user is from outside of this forum
                                          lebramor@piaille.fr
                                          wrote last edited by
                                          #78

                                          @november @cwebber but at one point the boy cried wolf for a real reason.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups