Every junior dev thinks microservices will fix their spaghetti. It won't. It'll be distributed spaghetti. Congratulations.
developer / builder
Michele Pin
Backend-focused Software Engineer. Building warehouses, side projects, and occasional opinions.
Projects
// things i've built or am building
Lemon WMS
Full WMS rewrite as a portfolio-grade reference implementation. Append-only inventory ledger, multi-tenant RBAC, and integration testing.
WSpace WMS
Production warehouse management system. Bin-to-bin movement, FIFO erosion, OCR document capture, and ERP integrations.
Personal Portfolio
This site. Built with Next.js, TypeScript, and Tailwind CSS. Clean, minimal aesthetic with modal-based project views.
Rants
// opinions, observations, occasional wisdom
Why legacy codebases are actually good for you
Nobody wants to hear this, but two years inside a 400k-line .NET Framework monorepo taught me more about systems design than any greenfield project ever could. When everything is connected to everything, when changing one thing breaks something three modules away, you develop instincts. You start to understand why isolation matters, why contracts between components are worth the ceremony, why the boring solution usually wins. Greenfield projects let you pretend. Legacy codebases make you reckon.
"We'll refactor it later" is a lie you tell yourself at 4pm on a Friday. The code is permanent. The deadline was temporary.
On switching from hospitality to tech
Thirteen years in hospitality before I wrote a line of production code. People always frame this as a disadvantage. Here's what hospitality actually taught me: how to read a room, how to stay calm when systems fail in real time, how to communicate with people who have zero patience and high expectations. Sound familiar? The hardest part of software isn't the code. It's the people, the deadlines, the misaligned expectations. Turns out I'd been training for that my whole career.
All Rants
// a collection
Every junior dev thinks microservices will fix their spaghetti. It won't. It'll be distributed spaghetti. Congratulations.
Why legacy codebases are actually good for you
Nobody wants to hear this, but two years inside a 400k-line .NET Framework monorepo taught me more about systems design than any greenfield project ever could. When everything is connected to everything, when changing one thing breaks something three modules away, you develop instincts. You start to understand why isolation matters, why contracts between components are worth the ceremony, why the boring solution usually wins. Greenfield projects let you pretend. Legacy codebases make you reckon.
"We'll refactor it later" is a lie you tell yourself at 4pm on a Friday. The code is permanent. The deadline was temporary.
On switching from hospitality to tech
Thirteen years in hospitality before I wrote a line of production code. People always frame this as a disadvantage. Here's what hospitality actually taught me: how to read a room, how to stay calm when systems fail in real time, how to communicate with people who have zero patience and high expectations. Sound familiar? The hardest part of software isn't the code. It's the people, the deadlines, the misaligned expectations. Turns out I'd been training for that my whole career.
The best code review comment is silence. Your code didn't need explaining.
Building for production from day one
There's a myth that you can always optimize later. That technical debt is a tool, not a liability. I've spent months untangling this philosophy from systems I inherited. The cost of fixing logging, adding monitoring, refactoring transaction handling "when there's time" is exponentially higher than doing it right from the start. The constraints of production are features, not bugs. Design with them in mind.
CV
// résumé, two flavours
MICHELE PIN Backend-Focused Software Engineer California, US · pinmichele23@gmail.com SUMMARYBackend-focused Software Engineer with production experience building and stabilizing warehouse management systems, ERP integrations, and legacy .NET architectures. Specialized in system reliability, data integrity, and translating complex operational requirements into clean, maintainable backend services. EXPERIENCEBK Solutions — Software Engineer (Backend / Fullstack) 2024 – Present Production warehouse management system serving live logistics operations. • Refactored legacy ASP.NET monolith into modular service-layer architecture • Designed core warehouse flows: bin-to-bin movement, FIFO erosion, goods receiving, dispatch, packing • Built transaction-safe multi-step operations with explicit rollback handling • Integrated Google Cloud Vision OCR for automated document capture • Connected Microsoft Dynamics 365 Business Central as ERP source of truth Pelom — Frontend Developer, Intern Mar 2024 – Aug 2024 • Delivered product features end-to-end from Figma designs to production • Implemented full internationalization (i18n) across the application • Established component patterns to improve UI consistency SKILLSBackend: C#, ASP.NET, Node.js, TypeScript, Express Databases: PostgreSQL, SQL Server, Prisma, Sequelize Frontend: Next.js, React, Angular, Tailwind CSS Systems: REST APIs, transactional workflows, structured logging, ERP integrations EDUCATIONUniversity of London — BSc Computer Science (in progress) Assembler Institute of Technology — MS Software Development (2023)