AI for editing is good and have many useful cases. The part where it fails is that the tone/style of the writing gets overtaken and reads like all other AI edited writing. But the quality of the edit is good, its just not in your style. When everyone sounds the same then there is no uniqueness. But using it edit legal letters, software documentation etc are very good use cases, using it to explain your ideas in a blog not so much.

I work mostly on the tech side of things but my corporate limitation has always been writing up documentation, communicating/translating to stakeholders, and recalling everything relevant when writing PR descriptions. AI has been a breath of fresh air. I actually communicate more information efficiently than I would have ever put the effort into before. I still maintain my own writing for more casual things like social media (HN included) and low stakes Slack conversations but AI for getting across ideas and then proofreading it is great.

I was asked to write user stories about a complex topic where I’m the SME at work. I spent two hours info dumping everything I knew about the project, everything the AI wouldn’t have any context for, using Cursor to add related projects to the workspace, tagging specific files where we’d implemented similar things with our styles, noted all the quirks of the system and how it works and where to find relevant information. I spent a lot of time on it, and then asked it to reach out using cli to grab relevant information from our infra, and write stories about how we’d accomplish everything I intend to get done. I then spent another few hours reviewing the 45 or so stories that conversation generated. It was similar to how I’d talk to a new contractor I’m onboarding to work on the work.

I have a deep knowledge of the information, have done the process we’re doing on two previous projects, but organizing all the stories would have been an absolute nightmare. I still spent half a day on this, I’d guess the fatigue from the boring parts would have made this take a week or maybe two, just because I was doing the parts I enjoy (knowing things and describing them) and I was able to offload the parts I’m not great at (using a lot of boilerplate language to organize the info I knew into scrum stories). Then I had a meeting, reviewed the stories with my coworkers, we had a discussion, deleted two or three of them that we determined weren’t necessary, and fixed up one or two where I’d provided insufficient information about some context surrounding coloring of a page.

It burned through a ton of Opus 4.6 tokens, looked through a ton of code (mostly that I’d written, pre-LLM), but has been amazing for helping me move into a lead position where grooming stories and being organized has always been my weakest point.

Also, when I wrote a postmortem for a deploy that had some issues, I wrote it all by hand. You have to know when the tools help and when they will hinder.

I thought it's quite good. Of course, I'm not taking 100% of output, but it takes care of my grammar blindspots (damn you commas and a/an/the articles!).

Can you please share what and how gets degraded? Sometimes I don't like a phrase it selects, but it's not common

It’s kinda useful to me for the following three reasons:

- spelling - grammar or weird grammar as English is not my native language - read proofing and finding things that do not make sense in terms of sentence structure

I do not use it for ideas, discussing the writing, or anything else because that beats the purpose of writing it myself (creative writing).

Only if you don't understand how to control AI. If you understands how it works and have the skills to ride it like a wild horse, you can make yourself a 10x developer. Its maybe a bit of an insult, but you seriously have to change that mindset. AI is not going to be worse tomorrow. It will get better and it will dramatically change our life as developers. Code will no longer be a prominent thing we are working on in the near future.