3 ms·
It's really weird, I'm seeing across the board that people who never believed in them before are suddenly all into good software eng practices (starting with wr
by zmmmmm 6mo ago
It's really weird, I'm seeing across the board that people who never believed in them before are suddenly all into good software eng practices (starting with writing a spec) because of AI.
It's kind of fascinating that we never were willing to do these things for humans but now that AI needs it ... we are all in. A bit depressing in the sense that I think mostly the reason we happy to do it for AI is that we perceive it will benefit us personally rather than some abstract future human.
- taneq 6mo agoIt’s an interesting psychological phenomenon. It’s like the way I keep my house way tidier since I got a robot vacuum. Pick things up off the floor for aesthetics’ sake? Nah. Pick them up because the vacuum will attempt to eat them and might get sick? Of course!
- GarnetFloride 6mo agoMy manager just told me that after 12 years of trying to get one of the founders to understand the difference between dev docs and user docs, they tried getting Claude to do it and he finally got it that they are different. He'd been saying this whole time that customer could just read the dev docs. If they could they wouldn't need our software.
- zenoprax 6mo agoHow firm is the boundary between a dev doc and a user doc in your opinion? I have found that the overlap can be quite large if the users are also technically proficient. Right now I'm trying to balance "how X works so you can use the app better" with "how X works so you can contribute or build your own plugin". DeepWiki really helps as a backstop for anything not already covered though it's not without its own caveats of course.
- PetitPrince 6mo agoNot OP but I think you have the right intuition in making a difference between using the app / contribute to the app. You may want to read https://diataxis.fr/ https://diataxis.fr/ which elaborate on this idea and add another dimension (action / cognition) to this.
- zenoprax 6mo agoI appreciate the suggestion but that's what I've been using! :D In fact, the only area I've been struggling with are "Concepts" because they have less clear boundaries for the right amount of detail. Here is what I've been working on: https://github.com/super-productivity/super-productivity/wiki https://github.com/super-productivity/super-productivity/wik...
- GarnetFloride 6mo agoIn general, I am talking about non-technical or technical in a different field. In my case right now, our users are civil engineers, they just want to be able to use our software to model the environment. They really don't want to become an expert programmer on top of that. They just want to be able to build their thing, like a bridge, so they can make money, and plug numbers into our software to do that. It's like making a hammer, the documentation needed for forging a hammer out of steel will be radically different from using the hammer to build a house or doing ortho surgery.
- ElevenLathe 6mo agoI see variations on this too. It's fascinating that there is a class of people who were uninterested in expressive, natural language communication when it was only a way to speak to other people, but who are now super interested in it because it is a way to speak to machines. I worry about the wellbeing of these people -- they seem like prime candidates to slide into AI-induced psychosis.
- bloppe 6mo agoMy friend at a faang was talking about the "massive overhauls to make everything ready for ai". I asked for an example. He said "basically just documenting the shit out of everything" I guess that just never occurred to anybody before.
- programmarchy 6mo agoAI might actually RTFM
- Cthulhu_ 6mo agoIt would / should / can, but there's big efforts in reducing token consumption now, so AI will likely try to skim and pick documentation just like real humans.
- akoboldfrying 6mo agoThere was a recent effort at work to make it possible for agents to provide up-to-date help on how to do various admin/setup tasks. A very sensible goal: We already have lots of documentation, the problem is that it's scattered everywhere and mostly out of date. Turns out the new solution amounted to someone manually going through it all and painstakingly preparing some Markdown files for consumption by said agent. Somebody pointed out that those Markdown files might be helpful for people to read directly. Bit of an Emperor's new clothes moment. (I wanted to slap a : rolling_on_the_floor_laughing: reaction on it, but sadly it turns out I'm actually too chickenshit to do that in today's job market.)
- trollbridge 6mo agoThe evolution of Markdown into a programming language has been an interesting one to behold.
- _heimdall 6mo agoThe CEO of Uber made the same comment on Diary of a CEO recently. I think it was for their customer service team if I'm not mistaken, they threw their existing docs at an LLM and it was all over the place because policies were poorly documented and defined. The team is now documenting everything from scratch, focusing on outcomes rather than process - TBD if it works out.
- majormajor 6mo ago> It's really weird, I'm seeing across the board that people who never believed in them before are suddenly all into good software eng practices (starting with writing a spec) because of AI. > It's kind of fascinating that we never were willing to do these things for humans but now that AI needs it ... we are all in. A bit depressing in the sense that I think mostly the reason we happy to do it for AI is that we perceive it will benefit us personally rather than some abstract future human. I don't think that's the reason. I think it's because they take time, and few people were willing to put in time for "maybe it'll make writing the actual code faster" gains when the code was going to take a few times longer to write itself. You also can get faster feedback to iterate on your spec now, which improves the probability of it helping future-you. So combine that with the fact that the llms are more likely to get lost if you don't spec stuff in advance, and the value of up-front work is higher (whereas a human is more likely to land on the right track, just more slowly than otherwise, making the value harder to quantify).
- Cthulhu_ 6mo agoYeah I think a lot of pushback to best practices is basic cost/benefit; I like writing documentation, but I'm also often feeling a bit depressed that nobody will actually read it in as much detail as I wrote it. But LLMs do / can. Actually there's a lot of projection there too; I don't read documentation in detail. And nowadays, I point an LLM at documentation so that it can find the details I would otherwise skip over. The destruction of the millennial attention span is real, and it's worse in the younger generations, lmao.
- noduerme 6mo agoWell it's also just that you have a list of 20 features to add, and if it works, you want to ship it, and someone might even get mad if you spend a day dawdling on best practices and documentation and so on. Corporate cultures generally don't have the same long term thinking about reusability and legibility and fault-tolerance that an individual coder may have about the code they want to write once and forget. (Neither do LLMs, for that matter).
- jappgar 6mo ago
- DrewADesign 6mo agoI always knew the dev world leaned more toward interesting technical challenges and interoperability than maximizing the benefit to humanity- it’s why I switched to design. However, I didn’t realize the intensity of that preference until the entire industry got ridiculously AI-pilled.
- cheriot 6mo agoBetter commit messages, better and more up to date docs, etc. It's not all slop!
- deleted 6mo ago[deleted]
- klvino 6mo agoHad similar discussion around prompting. Spend years clearly outlining required data inputs, creating forms to dummy proof communication from users. Now that AI is in the picture, users are willing to learn to write elaborate Shakespearean-scale prompts. They are more willing to learn how to communicate to a computer more than how to clearly communicate to a human.