process

My work process

How I go from problem to production. Git strategy, testing philosophy, and yes — AI as a tool, with intention.

git

Git workflow

Branching strategy I use to keep a clean and collaborative history in my projects.

Atomic commits

Each commit represents a complete logical change. I use `git commit --amend` to keep the history clean before push.

Branch strategy

Short feature branches (max 2-3 days). Merge to develop with squash. Release branches for QA.

Code review

Every merge to develop goes through PR with at least one review. I use conventional commits for automatic changelogs.

How I integrate AI into my workflow

Tools and techniques I use to increase my productivity without compromising code quality.

Prompt engineering for architecture

I use language models to explore architectural trade-offs, generate initial database schemas, and document technical decisions (ADRs).

Automation of repetitive tasks

Boilerplate generation, data transformation (e.g., Excel to DB seeds with Python), and NestJS module scaffolding.

Review and refactoring

Code analysis to detect code smells, refactoring suggestions, and unit test generation as a starting point.

prompt_example.md

## Prompt Example

`You are a Senior Software Architect. Analyze the following requirements and provide:
1. A database schema with tables, relationships, and indexes
2. API endpoints following REST conventions
3. Key architectural decisions with trade-offs
4. Suggested tech stack with justifications

Requirements:
- Users can create projects
- Projects have tasks assigned to team members
- Tasks have status (todo, in-progress, done)
- Team members get notified of assignments

Provide the response in a structured format suitable for an ADR document.

Example of well-structured prompt for documenting architectural decisions