I apologize ahead of time, what follows has no tooling applied to it. No grammar checks, no AI, and no edit passes for flow. It might be a bit roug...
For further actions, you may consider blocking this person and/or reporting abuse
Thank you for the shoutout, @ryansolid. I'm glad you remembered some of my pointers, annoying as they may have seemed. At the end of the day, you decide on your content.
"Short attention spans and a need to get to the point." also sounds like something I would say 😄
One thing you always get right: You add your own perspective and that's what's unique, can't be copied by other humans or imitated by AI.
In case you or someone else wants a few pointers about tech writing, I share them in multiple slides of the deck for My 10 steps to tech community contributions talk (link to recording in slide deck description).
The problem with AI writing is that it makes repetitive slop sound useful and insightful - you get halfway through an article and think, I've read too many words for this very simple point.
No matter how you write, Ryan, you can never be accused of that. I've been very inspired (and sometimes lost) by your writing and your work. You have something to say that's worth hearing, and anyone who dismisses that as AI slop isn't actually consuming your content -> but does that matter? Maybe you'd never have got your point across to 90% of those people anyway - the 10% who now get it, that's the gold.
I think this might actually be one of the best ways to work with an LLM. It always wants to shorten and get straight to the point, because that's basically what it's trained to be good at.
I also write fiction, and I once asked a model why it was so good at evaluating conference presentations but so bad at fiction. It basically admitted that this is just its nature: if you gave it "The Lord of the Rings", it would probably cut the entire Shire because “this part could be summarized” 😂
I’ve always found your voice and perspective one of the most interesting in the landscape, and honestly I never stopped thinking “is this ai generated?”, as content was so interesting that really the form didn’t matter too much to me. After all those were not meant to be screened by literary prize judges.
Keep on writing articles please, I've learnt so much from yours… thank you 🙏🏽
AI hate is real and often irrational. People are scared of AI slop, but look what is happening - all media platforms have switched to algorithmic feeds where you basically see random content, with very little control over it. And now we are mad that it's AI in there. Platforms encourage posting frequency over quality, and now we are mad that someone is automating it.
I like this article. Soon we will all be flooded by AI assisted content that we won't see the difference anymore. I don't care if an article was AI generated / assisted or not. What I care about is the content. And I always look forward to reading your articles. I've read them all !
You can never please such people, with or without AI. They would never offer valuable feedback, or have a civil discourse where you can leave with new insight or things to ponder. They complain of stock photos, bad photoshopped photos, AI generated photos, etc. And often times, their guesses at what's "AI generated" is a wrong guess.
Publishing it without the passes is doing more work than the essay is. The roughness is what makes it read as someone thinking rather than someone presenting, and that is exactly the layer a cleanup pass files off first.
Something funny about the strongest case against the tooling being what the text sounds like without it.
As someone who writes hugely long Slack replies and then has to rewrite and trim them heavily so that anyone can actually read through and understand them, I liked this article very much.
Nice frontend patterns. One thing I've been paying more attention to is Core Web Vitals impact — CLS in particular can creep in with dynamic content loading. Have you measured the Lighthouse scores with these patterns?
This has a practical engineering lesson: validate the system at the real boundary, not only where the code looks clean. Integration inputs, permissions, retries, and state transitions are where the expensive surprises tend to hide.
I love how you kept your AI content journey completely unfiltered, letting the raw process speak for itself without any grammar checks or tooling. Have you thought about cross‑posting it to ZyVOP (zyvop.com) to reach even more engineers?