whoami - Damian Fastowiec

I'm Damian - I live in Warsaw, and after eight years, I’m still genuinely fascinated by programming. I went into engineering because I like figuring things out, and I’ve stayed in this industry because creating things that work still brings me the same joy week after week.

This journey has taken me from ensuring system reliability to shaping artificial intelligence so that it becomes a tool the team can rely on. I work best when I have the space to be creative, the discipline needed to see a task through to a successful conclusion, and people with whom I can brainstorm solutions.

I started CodeMonkey because I care about the work — and about the people I do it with. When I join a project, I join your team: listening first, sharing the pressure, and solving hard problems side by side.

← Back to CodeMonkey · See also How I Work | Ways to Engage

What you get

# collaboration.py
assert ship_production_systems     # not demos that die after the call
assert clarify_architecture_fast   # decisions your team can act on
assert transfer_capability         # specs, docs, optional training — not a dump

Ship

Backends, agents, and RAG that hold up past the first demo.

Clarify

Architecture and delivery choices when you need a clear next step.

Transfer

Handoff your team can run and extend — not a silent repository drop.

Partners

Work delivered with engineering partners across telecom AI, finance, and platform delivery. Same thread throughout: make systems testable, shippable, and owned by the people who keep them.

Telecom & multimodal AI — partner: Orange

• Built and tuned deep learning models for vision, audio, text, and generative use cases — then turned results into recommendations stakeholders could act on.
• Designed chatbots and AI agents with modern frameworks; moved experiments into interactive systems teams could actually use.
• Ran feasibility studies on cost and performance so new approaches earned their place — or got dropped early.
• Owned containerized test environments and CI for hardware-related automation; used computer vision to measure system metrics, not guess them.
• Introduced small-LLM proof-of-concepts into testing (e.g. object recognition on images) to show what was possible without derailing delivery.
• Established automation and CI discipline on hardware systems that still shapes how I design software today.

Financial systems — partner: Nordea

• Automated validation of financial data and reporting flows where mistakes are expensive.