Write honestly. Write the way you write. Use your own flow, make your own grammatical wobbles, whatever they are. Express yourself authentically.
Don't let an AI do this to you.
Write honestly. Write the way you write. Use your own flow, make your own grammatical wobbles, whatever they are. Express yourself authentically.
Don't let an AI do this to you.
Person A: Me try make this code work but it always crash! maybe the server hate or i miss thing. any help?
Person A with AI: I've been trying to get this code to work, but it keeps crashing. I'm not sure if I missed something or if there's an issue with the server. Any tips would be appreciated!
For a non-native English speaker, it's much better professionally to use AI before sending a message than to appear authentic (which you won't in another language that you aren't fluent so better to sound robotic than write like a 10 years old kid).Recently, I stumbled upon a bug that initially seemed minor but quickly revealed itself to be a formidable adversary. It disrupted the seamless user experience I had meticulously crafted, and despite my best efforts, this issue has remained elusive. Each attempt to isolate and resolve it has only led me deeper into a labyrinth of complexity, leaving me frustrated yet undeterred.
Understanding that even the most seasoned developers can hit a wall, I’m reaching out for help. I’ve documented the symptoms, error messages, and my various attempts at resolution, and I’m eager to collaborate with anyone who might have insights or fresh perspectives. It’s in the spirit of community and shared knowledge that I hope to unravel this mystery and turn this challenge into an opportunity for growth.
Me: This is the most garbage code I've ever seen. It's bad and you should feel. It's not even wrong. I can't even fathom the conceptual misunderstandings that led to this. I'm going to have to rewrite the entire thing at this rate, honestly you should just try again from scratch.
With AI: I've had some time to review the code you submitted and I appreciate the effort and work that went into it. I think we might have to refine some parts so that it aligns more closely with our coding standards. There are certain areas that are in need of restructuring to make sure the logic is more consistent and the flow wouldn't lead to potential issues down the road.
I sympathize with the sibling comment about AI responses being overly-verbose but it's not that hard to get your model of choice to have a somewhat consistent voice. And I don't even see it as a crutch, this is just automated secretary / personal assistant for people not important enough to be worth a human. I think a lot of us on HN have had the experience of the stark contrast between comms from the CEO vs CEO as paraphrased by their assistant.
For lots of East Asian researchers it's really embarrassing for them to send an email riddled with typos, so they spend a LOT of time making their emails nice.
I like that tools like this can lift their burden
OK -- I can see this. But I think Grammarly would be better than this.
But its suggestion system, where it spots wordy patterns and suggests clearer alternatives, was available long before LLMs were the new hotness, and is considerably more nuanced (and educational).
Grammarly would take apart the nonsense in that screenshot and suggest something much less "dark and stormy night".
But there's not much more important, stylistically, to writing an business email or document than clarity. It's absolutely the most important thing. Especially in customer communications.
In the UK there is/used to be a yearly awards scheme for businesses that reject complexity in communucations for clarity:
https://www.plainenglish.co.uk/services/crystal-mark.html
But anyway, you don't have to act on all the suggestions, do you? It's completely different from the idea of getting an AI to write generic, college-application-letter-from-a-CS-geek prose from your notes.