Writing Style Analysis

Writing Style Analysis — Knowledge Base for the AI Agent

Writing Style Summary

General characteristics

Language and tone:

• English only (technical terms in English by default; this is the canonical writing language as of 2026-05-17 — see CLAUDE.md)
• Direct, practical, personal style
• Reflective, experience-driven
• First person frequently (“I”, “my”)
• Prefers concrete examples and practical guidance over abstract theory

Document structure:

• Every document begins with YAML frontmatter containing metadata:
  • title, date, enableToc, openToc, tags, type
• Hierarchical heading structure (H1, H2, H3)
• Heavy use of numbered and bulleted lists
• “Resources” section at the end with external links

Characteristic elements:

• Obsidian internal links in the format [[path/to/file]]
• Emoji in section headings (🚀, 🎨, ☘️, ✍️, 📒, 🗒️, 🔗, 🧩, 📖)
• TODO comments in the format #todo or #todo/replace
• Dataview queries for dynamic content rendering
• Book quotes are often emphasized with bold

Content organization:

• Often opens with a general introduction or framing context
• Topical sections with clear headings
• Bulleted lists preferred for scannability
• Closes with practical guidance or a summary

---

Representative style fragments

Fragment 1: Personal and reflective style

Source: ABOUT/My career path.md

My professional programming adventure began in the fourth year of college. I remember it like today - one of my friends during the vacations started working in one of the software development companies (such a current software house). I spent those vacations in the USA and he wrote to me that they needed someone else. I agreed to an interview and shortly after my return I started working as a junior .NET programmer. Due to my still ongoing studies, the working hours were irregular and unlimited. I worked as much as I could - I usually went straight to the company after class. Even then I paid attention to several aspects:

1.  I knew nothing - much of the time I had no idea what to do.
2.  There is nothing better than a good and helpful team.
3.  Programming is something for me - the satisfaction of completing projects is a great feeling.
4.  Unstructured and unlimited working hours suit me.

Characteristics:

• Personal narrative with concrete detail
• Bulleted list with key observations
• Natural English prose
• Reflective approach to lived experience

---

Fragment 2: Structure with emoji and sections

Source: BUSINESS/BOOKS/Amp It Up.md

# 🚀 The Book in 3 Sentences
"Amp It Up!" is a book for leaders which encourages them to raise standards, energy, and pace within organizations to achieve higher goals. It emphasizes the importance of clear priorities, tight team alignment, and a mission-driven strategy that inspires and centers attention on core values. Key points also include the role of organizational culture, effective execution, and eliminating mediocrity to enhance business outcomes.

# 🎨 Impressions

## How I Discovered It
Recommended by [(7) Frank B. Georgiew 高傅安 | LinkedIn](https://www.linkedin.com/in/fbgeorgiew/)

## Who Should Read It?
C level leaders - CEOs especially

# ☘️ How the Book Changed Me

I understood why this is importand and why the organization where I work in is build and managed in the way it is.

Characteristics:

• Emoji used to categorize sections
• Short, focused answers
• Links to external sources
• Personal reflections on the impact of the book

---

Fragment 3: Practical guidance with hierarchical structure

Source: ABOUT/I have a business and not business has me.md

# How not to become a slave of your own business
## Three commandments:
1. You cannot loose.
 1. You are a winner from the start. Think of what you have and on start you have a lot. If you think about 3 things every day what you can be grateful [[LIFE/KNOWLEDGE/INFO/5 Minute Journal]] I guarantee - no matter who you are and in what situation you would be able to find those 3 things.
 2. Business/life is an endless game and if it is endless you cannot loose.
2. Development is a choice - you don't have to do it but it gives you a great advantage in terms of building a business but if you just do it the development will come since you will learn on. Avoid constant pressure that you need more, that there is something you can do. [[BUSINESS/BOOKS/Company of one]] #reading-list/business-finance
3. Enjoy it all - do it for fun (business and life). Enjoy the process and not only when you achieve something. Goal alternative:
 1. Values - what values you follow in life - write it down and stick to it and all decisions you make confront with those values.
 2. Direction - instead of defining a goal you can define a direction - you will avoid the pressure of not reaching the destination when you won't achieve the goal, if only you will go in the direction you defined you will be able to get somewhere and enjoy the process.

Characteristics:

• Hierarchical structure with nested lists
• Internal links to other notes
• Practical, concrete guidance
• Personal angle on business topics

---

Fragment 4: Book notes — template structure

Source: LIFE/BOOKS/How to take smart notes.md

# 🚀 The Book in 3 Sentences
The book is about how you should take notes in order to take advantage of them in the efficient way. It describes the slip-box technique and describe who invented it and how it worked for him. Approach to note-taking was inspired by the 20th-century German sociologist Niklas Luhmann.

# ☘️ How the Book Changed Me

This was the "why" for taking notes while reading and looking for the purpose of reading and learning specified stuff. The important thing for me was finding the purpose of note taking - it is not just collecting information; it is seeking to develop ideas and arguments. I try to read with a pen in my hand - I always did but now I know that it makes sense.

# Summary + Notes

Systematically make three types of notes to develop your ideas and arguments:
1. Fleeting notes - they don't go in a slip-box; they're simply for capturing ideas and thoughts. You can take them in a notebook, on a scrap of paper, or wherever works for you. Keep these notes in one place so you can go through them later.
2. Literature notes - notes about what you read. While you're reading, write down things you don't want to forget along with reference details. Your notes should be short and in your own words. These go into your reference slip-box– the first of the two slip-boxes.
3. Permanent notes - These will arise from your fleeting and literature notes, which you should go through regularly– preferably daily. As you review your notes, ask yourself what's relevant to your own ideas, your research, and your interests.

Characteristics:

• Template structure for book notes
• Emoji in section headings
• Personal reflections on impact
• Practical summary with bulleted lists

---

Fragment 5: Technical notes — concise and practical

Source: LIFE/KNOWLEDGE/INFO/Pomodoro.md

# Pomodoro

## 🗒️ Description
Is a technique of working on the tasks.

## 🔗 Links
[Pomodoro Technique - Wikipedia](https://en.wikipedia.org/wiki/Pomodoro_Technique)

## 🧩Features:
Helps you if:
- you want to stay focus on the task
- can't beat the procrastination
- find little distractions often derail the whole workday
- consistently work past the point of optimal productivity
- have lots of open-ended work that could take unlimited amounts of time (e.g., studying for an exam, research for a blog post, etc.)
- re overly optimistic when it comes to how much you can get done in a day (aren't we all 🙃)
- enjoy gamified goal-setting

How to:
1. Pick a task
2. Set a 25-minute timer
3. Work on the task until the time is up
4. Take a 5 minute break
5. Every 4 pomodoros, take a longer 15-30 minute break

Characteristics:

• Short, focused description
• Emoji per section
• Bulleted list with practical pointers
• Step-by-step instructions

---

Fragment 6: Project notes — technical detail

Source: PROJECTS/ARCHIVE/SHAREFUND/ShareFund.md

# ShareFund

## Description
A tool that helps in distributing shares in a non incorporated startup. Aimed at startup founders and project creators. It responds to the needs of building projects together and instead of paying for adding value to the business each member receive a piece of a project. Another words the tool helps with fairly distributing shares in the project.

## Technology stack
1. ASP .NET 6 WebApi
2. Blazor WASM
3. SQL Server
4. SignalR
5. Hangfire
6. Azure

## About project
### What's new about this?
Innovative way to work on projects and sharing the equity.
It's build using the API First principle.

### What?
An app
### How?
It will be able to count equity-split for all members of the project fairly from the input. Moreover, it would be easy to integrate into other tools with open API and each member will be able to control entries for the rest of the team.
### Why?
To avoid wasting time, suffering unnecessary financial losses, sacrificing relationships and experiencing emotional regret while struggling in an early-stage startup environment, use the dynamic equity-split model.

Characteristics:

• What/How/Why structure for projects
• Technology stack list
• Concrete, technical language
• Explanation of business value

---

Fragment 7: Reflections and lessons learned

Source: CRYPTO/NOTES/What mistakes I made on the crypto market in 2021-2022.md

# What mistakes I made on the crypto market in 2021-2022

## What mistakes I took
1. Didn't take profit
2. Didn't make own research
3. Didn't listen to Phil Konieczny - he said that we should get back to bitcoin, if I had done what he said I would save a lot from the losses I took
4. Trusted in Luna
5. Getting into Polkadot parachains - it was too late
6. Getting into project I didn't fully understand

## What worked
1. Following influencers - getting into the projects, they talked about, early
2. Diversification - it was good that I kept my assets in few places
3. I moved some BTC to ledger

Characteristics:

• Personal, candid reflections
• “What went wrong” vs “what worked” structure
• Concrete examples of mistakes
• Short, focused points

---

Fragment 8: Long book quotes with own commentary

Source: BUSINESS/BOOKS/Amp It Up.md

## 1. Raise your standards:

The late Steve Jobs was only inspired by "insanely great" things. He set a high bar for seemingly everything, and anything that didn't meet his standards was summarily rejected. Try applying "insanely great" as a standard on a daily basis and see how far you get. People lower their standards in an effort to move things along and get things off their desks. Don't do it. Fight that impulse every step of the way. It doesn't take much more mental energy to raise standards. Don't let malaise set in. Bust it up. Raising the bar is energizing by itself. Instead of telling people what I think of a proposal, a product, a feature, whatever, I ask them instead what they think. Were they thrilled with it? Absolutely love it? Most of the time I would hear, "It's okay," or "It's not bad." They would surmise from my facial expression that this wasn't the answer I was looking for. Come back when you are bursting with excitement about whatever you are proposing to the rest of us.

**Leaders can do two things that bring almost instant benefit. First, think about execution more sequentially than in parallel. Work on fewer things at the same time, and prioritize hard. Even if you're not sure about ranking priorities, do it anyway**. The process alone will be enlightening. Figure out what matters most, what matters less, and what matters not at all. Otherwise your people will disagree about what's important. The questions you should ask constantly: What are we not going to do? What are the consequences of not doing something? Get in the habit of constantly prioritizing and reprioritizing.

Characteristics:

• Long book quotes
• Key passages highlighted with bold
• Own commentary and reflections
• Practical takeaways from reading

---

Patterns and Conventions

1. YAML frontmatter

Every document opens with metadata:

---
title: "Document title"
date: YYYY-MM-DD
enableToc: true
openToc: true
tags: ["tag1", "tag2"]
type: basic-note | book-note | knowledge-note
---

2. Internal links

Format: [[path/to/file|Display text]] or [[path/to/file]]

3. Emoji in headings

• 🚀 — The Book in 3 Sentences / main message
• 🎨 — Impressions
• ☘️ — How the Book Changed Me / impact
• ✍️ — My Top 3 Quotes
• 📒 — Summary + Notes
• 🗒️ — Description
• 🔗 — Links
• 🧩 — Features
• 📖 — Further reading

4. Book note structure

# Book title
Date Finished: date
Author: author
Tags: tags

# 🚀 The Book in 3 Sentences
# 🎨 Impressions
## How I Discovered It
## Who Should Read It?
# ☘️ How the Book Changed Me
# ✍️ My Top 3 Quotes
# 📒 Summary + Notes
# Resources

5. Knowledge note structure

# Title
## 🗒️ Description
## 🔗 Links
## 🧩Features:
## 📖Further reading

6. TODO comments

• #todo — general task to be done
• #todo/replace — placeholder to be replaced
• #inbox/todo — task sitting in the inbox

7. Dataview queries

Used for dynamic content rendering:

```dataview
table title
from "CATEGORY"
```

---

Recommendations for the AI agent

When writing new documents

1. Always use YAML frontmatter with the right metadata
2. Use emoji in section headings per the convention
3. Create internal links to related documents
4. Write in first person for personal reflections
5. Use bulleted lists for scannability
6. Add a Resources section with external links
7. Be concrete and practical — avoid empty generalities
8. Write in English — this is the canonical vault language as of 2026-05-17
9. Use hierarchical heading structure
10. Add personal reflections and experience where it adds signal

When editing existing documents

1. Preserve the existing structure and style
2. Don’t change frontmatter without a reason
3. Preserve internal links and emoji
4. Add new sections following existing conventions
5. Update dates when the document is materially modified

---

Examples of different document types

Personal / reflective note

• ABOUT/My career path.md
• ABOUT/I have a business and not business has me.md
• CRYPTO/NOTES/What mistakes I made on the crypto market in 2021-2022.md

Book note

• BUSINESS/BOOKS/Amp It Up.md
• LIFE/BOOKS/How to take smart notes.md
• LIFE/BOOKS/Atomic habits.md

Knowledge / informational note

• LIFE/KNOWLEDGE/INFO/Pomodoro.md
• LIFE/KNOWLEDGE/INFO/Trust.md
• LIFE/KNOWLEDGE/INFO/Zettelkasten.md

Project note

• PROJECTS/ARCHIVE/SHAREFUND/ShareFund.md
• PROJECTS/ARCHIVE/Drug Temperature Control System.md

Travel note

• TRAVELS/TRIPS/2023 Greece January.md

---

Summary of key style characteristics

1. Personal and reflective — first person and lived experience
2. Practical — concrete pointers and examples
3. Structural — clear hierarchy and organization
4. Visual — emoji and formatting aid navigation
5. Networked — internal links form a web of references
6. English — canonical writing language (as of 2026-05-17 PL→EN migration)
7. Template-driven — consistent patterns for different document types
8. Evolving — documents are updated and developed over time

---

Document generated from analysis of the Obsidian notes repository. Analysis date: 2025-01-27 Translated to English and language rule updated: 2026-05-17