# Letting AI analyze my writing style

- Link: https://saguiitay.com/letting-ai-analyze-my-writing-style/
- Published: 2025-02-11T23:41:18+02:00
- Author: Itay

I’m playing more and more with AI recently, and decide to let it analyze my writing
style, to see what it thinks. I’ve used the article “[How to Teach ChatGPT to Mimic my Writing Style](https://wielded.com/blog/how-to-teach-chatgpt-to-mimic-my-writing-style)”
as a guideline, and used the following 4 posts as the baseline:

 * [TheRandom.Tools relaunched](https://saguiitay.com/therandom-tools-relaunched/)
 * [Best Unity Performance tips for C# from a Cloud Developer](https://saguiitay.com/unity-performance-tips-for-csharp/)
 * [Querying Azure Data Explorer using Power BI](https://saguiitay.com/querying-azure-data-explorer-using-power-bi/)
 * [New versions of WebDAVClient and CardinalityEstimation](https://saguiitay.com/new-versions-of-webdavclient-and-cardinalityestimation/)

I selected these articles mainly because they contain a lot of text and explanation,
and not only code sample.

Here’s what the O1 model had to say about my writing style:

> 
> ### Tone:
> 
>  * Generally conversational with a friendly, explanatory feel, as if the author
>    is guiding the reader through their process.
>  * Professional but approachable, blending technical detail with a personal touch.
> 
> ### Diction (Word Choice):
> 
>  * Straightforward, using clear, concise language.
>  * Incorporates technical terminology (e.g., references to C#, Unity, .NET Core,
>    Kusto Query Language, etc.).
>  * Mixes informal pronouns (“I,” “we,” “you”) with precise technical terms to 
>    keep the explanations both personal and instructive.
> 
> ### Sentence Structure:
> 
>  * Primarily medium-length, declarative sentences, often beginning with direct
>    statements of what the author did or plans to do.
>  * Uses occasional short sentences for emphasis or to highlight next steps.
>  * Paragraphs are structured around a single technical or organizational improvement
>    point.
> 
> ### Burstiness (Variation in Sentence/Phrase Length):
> 
>  * Consistent in length overall with mild variation: typically a sentence or two
>    providing context, followed by a more detailed explanation.
>  * Occasional longer explanatory paragraphs or lists for technical deep dives.
> 
> ### Point of View:
> 
>  * Predominantly first-person singular (“I”) when describing personal actions 
>    and decisions.
>  * Shifts to first-person plural (“we”) or second-person (“you”) when inviting
>    the reader into shared considerations or offering advice.
> 
> ### Pace:
> 
>  * Moderately paced, moving steadily from one technical topic to the next without
>    lingering excessively.
>  * Introduces new concepts or technologies in quick succession, reflecting a hands-
>    on, iterative approach.
> 
> ### Literary Devices and Techniques:
> 
>  * Occasional rhetorical questions or casual asides to engage readers (e.g., “
>    But time will tell…”).
>  * Metaphors or figurative language are minimal; most explanations are direct 
>    and literal, focused on clarity.
>  * Uses comparison/contrast (e.g., naive string concatenation vs. StringBuilder)
>    to illustrate performance differences.
> 
> ### Mood:
> 
>  * Optimistic and solution-focused, highlighting progress and potential future
>    enhancements.
>  * Analytical, especially when presenting performance tests and results.
>  * Encouraging, aiming to help or inspire readers to implement similar improvements.
> 
> ### Perspective on Time:
> 
>  * Forward-looking, discussing planned features or future ideas.
>  * Reflects on past experiences (e.g., old code in C#, older library versions)
>    but emphasizes ongoing development and iterative improvements.
>  * Considers both immediate next steps (“I still need to…”) and longer-term possibilities.

Can’t say I’m surprised (especially given the input posts), but it’s still interesting,
and mostly a good analysis of my writing style. Or at least what I’m thinking about
it.

### _Related_
