Proof
Every project was different, but each started with something useful that already worked. The next safe step was unclear.
The work covers live platforms, inherited products, internal workflows, booking logic, integrations, migrations, messy data, and early-stage product work.
These were real systems, not demos, with users, business rules, edge cases, and consequences.
Examples from systems that had consequences.
2019–2024 · Booking platform
I worked on a live accommodation booking system. Booking rules, pricing, availability, partner integrations, and migrations affected day-to-day operations.
Useful when a system already matters, has grown messy, and changes need to account for what they affect.
Read the Travelminit project noteTECH: PHP, MySQL, partner APIs, channel-manager integrations, iCal sync, mobile web.
2012–2016 · Grant platform
I worked on an inherited production platform with dynamic forms, complex reporting, admin workflows, and performance problems under deadline pressure.
Useful when the system still has to run, even though its code, data, and business rules are no longer clean.
Read the Go Grants project noteTECH: PHP, Zend Framework, MySQL, SQL/EAV, jQuery, performance optimization.
2025 · Internal workflow
I built a custom admin system for a small hospitality business. Its shared spreadsheet no longer handled rooms, bookings, clients, services, prices, and change history well.
Useful when a spreadsheet has become part of daily operations, but no longer gives the team enough clarity or control.
Read the guesthouse admin system project noteTECH: Laravel, Livewire.
2017–2019 · Product rescue
I moved an unfinished AngularJS frontend closer to launch by stabilizing the app, setting up the build process, fixing browser/mobile issues, and rebuilding the embeddable badge with a much smaller footprint.
Useful when a product is close to launch, but still too fragile, unfinished, or tangled to ship confidently.
Read the Authorized.by project noteTECH: AngularJS, Preact, Webpack, jQuery, mobile web.
2026–present · Booking workflow
I am building FishFlow around how small fishing lake operators handle bookings: manual confirmation, resources, cabins, docks, boats, time slots, and lake-specific rules.
The difficult part is understanding how the business handles availability, requests, and exceptions, not simply making a calendar.
Read the FishFlow project noteTECH: Laravel, Livewire.
2026 · AI data pipeline
I built a public AI-assisted pipeline that crawls marketplace listings, filters noise, enriches messy data, controls cost, and keeps human review in the loop before anything is published.
Useful when AI supports a real workflow without replacing judgment, especially when the data is noisy, incomplete, expensive, or hard to trust.
Read the retro.dog project noteTECH: Laravel, NodeJS, LLM pipeline.
2016–2017 · Startup product
I worked across backend architecture, admin functionality, and mobile APIs while the product was still taking shape inside a small team.
Useful for projects that need someone who understands the product, makes technical decisions, and keeps work moving across several technical areas.
Read the Doorie project noteTECH: MeteorJS / Node.js, MongoDB, React.
What these examples have in common
The projects differ, but the useful work often begins in the same situation:
The work begins by understanding the real situation and making the risks visible. Then the system can move forward without pretending the mess is simpler than it is.
Describe the systemStart with the closest example
Start with the closest example. Tell me which part feels familiar, where your system is stuck, and what would make the next few weeks easier.
A few sentences are enough. I will read the message myself and usually reply with a few questions or suggest a short conversation.