About

Serhii Malyshev

I'm Serhii Malyshev, a software architect and tech lead based in Ukraine. Decades in software — most of it on large web platforms where architecture, delivery, and operations can't be treated as separate problems. I own systems end-to-end: service design, implementation, infrastructure, and the teams around them.

I run this hub because tech work is wider than code — teams, trade-offs, burnout, leading — and most writing treats those as separate worlds. That work taught me they're the same job.

What Ship Then Fix is

Ship Then Fix is a knowledge hub for tech work— code, teams, leadership, and the human side of the job. Not RTFM docs. Not a link dump. Not a personality blog where every piece is "my journey."

Articles are organized on four shelves:

• Build — architecture, tooling, the craft of shipping software
• Team — productivity, collaboration, self-org, conflict
• Lead — tech leading, stakeholders, trade-offs
• People — burnout, hiring, interviews, career

One format on purpose: short reads you can finish in one sitting, each on one topic that mattered in real delivery — not manuals, not listicles, not a diary.

Every piece carries a level — Finding your footing, Doing the work, or Mastery mode— because "intro to X" and "what I'd do differently after the third outage" are not the same conversation.

What we optimize for

• One clear takeaway — not ten frameworks per scroll
• Honest altitude— footing, doing, or mastery; labeled so you don't waste a read
• Claims you can check — sources when a number or platform rule is doing the work
• Peers who've shipped— written for people who've debugged production, not for traffic

What this isn't

• Official documentation for NestJS, Laravel, Medium, or any vendor
• Medical, legal, or HR authority — practical experience, not prescriptions
• A Medium-income or growth-hacking blog
• A product landing page for side projects — this hub is editorial, not a tools catalog

Background

I've reviewed tech books for Packt and written for JavaScript in Plain English. Outside this hub I'm an architect and tech lead on large web platforms — polyglot because the job demands it, not because I collect logos.

Backend: Node.js, TypeScript, NestJS · PHP, Laravel
Frontend: React, Next.js, Vue — and whatever else the team already bet on
Data & infra: MySQL, PostgreSQL · Docker, Kubernetes, AWS

The specific framework matters less than whether the system survives real load, real deadlines, and real teams. I write here about the gaps between slide-deck architecture and that.

I work during working hours. Plan well, ship in daylight, eat on time, leave room for friends — serious systems don't require sleep sacrifice. Since 2009 I haven't worked weekends unless the problem was genuinely interesting, not because someone ran out of Friday. Fire drills at night are a planning failure, not a credential.

Get in touch

This site is the library. If you're building in that neighborhood — architecture, delivery, a team stuck between frameworks — say hello on LinkedIn. Code and side projects live on GitHub.

← Back to the hub