This is anecdotal folksy wisdom porn.
Deleted Comment
This is anecdotal folksy wisdom porn.
It still screws up, but unlike 3.5 it sometimes catches unreasonable answers and corrects itself. Case in point: the other day I asked it for the gain of a helical antenna with certain dimensions. It said "150 dBi," then said, basically, "Wait, no, that's nuts," and used a different approach to get the right answer.
Parrots don't do that. If yours does, I would like to buy your parrot, please.
In any case, as you learn to ask it the right questions to explain, verify and correct itself interactively, you will be learning the material. I find this to be amazingly effective.
1) You have a marketing project that is speculative (as all marketing is). Say it's an API hookup and some automation between some tools.
2) You submit your project for prioritization by the dev department.
3) It gets done 9 months later. The specs are wrong because there were so many layers between the marketer and developer and the developer has no context for the project. You submit edits which get prioritized and takes another few months.
OR
You get Zapier approved by security once. Then for every project like this you fiddle with it until it does what you want. Total time: A couple of weeks.
No code removes friction from the org.
Developer time is always the biggest bottleneck at any org I've worked with. Anything that let's you get around it is worth its weight in gold.
If the business doesn’t think something should be prioritized, but a marketer decides that they really want to have it, I’m not sure it’s a great idea to go around what the business has prioritized. Most of the cost in software comes from maintenance of legacy systems. I hope this new no-code solution is something a department has decided to maintain indefinitely! I my experience, after the marketing person quits, the no-code solution gets chucked across the fence to IT, the no-code provider stops supporting their tool, and IT is forced to build a new one as an emergency a few years later because “the business has been using it for years.”
In a healthy org, if something is truly good for the business and will create global gains across the company, it should hop to the top of the priority list. Admittedly, I’m still hunting for this theoretical healthy org, though.
If you’re just throwing notes into a note-taking app with no way of processing them, I can see how this would be true, but my system is constantly resurfacing old thoughts, and I make conscious choices about what gets archived and preserved.
I read the full article, and it sounds like the author hasn’t heard of these. Confident article. Not deeply researched in my opinion.
I thought it was saying "a letter to those who fired tech writers because they were caught using AI," not "a letter to those who fired tech writers to replace them with AI."
The whole article felt imprecise with language. To be honest, it made me feel LESS confident in human writers, not more.
I was having flashbacks to all of the confusing docs I've encountered over the years, tightly controlled by teams of bad writers promoted from random positions within the company, or coming from outside but having a poor understanding of our tech or how to write well.
I'm writing this as someone who majored in English Lit and CS, taught writing to PhD candidates for several years, and maintains most of my own company's documentation.