Just launched DevOpsJoy! Your go-to DevOps service for startups that can’t afford full-time engineers.
We offer unlimited requests with a lightning-fast 48-hour turnaround. Our expertise includes AWS, Terraform, EKS, CI/CD, and security hardening.
https://t.co/vudRdMMSvR
the founders who are quiet on x are usually the ones building something serious
and the ones posting 10 times a day about building
are usually in the early stages of avoiding the hard thing
i include myself in both of these at different points
Havering enforcement starts TOMORROW.
If you're a landlord renting to 3+ tenants sharing facilities — you need a licence by March 18.
Fees this year: £1,400 for HMO (up 55% from £900).
Online portal is still broken. Apply by email: [email protected]
Fine: up to £30,000. Tenants can reclaim 24 months rent via RRO.
Don't wake up Tuesday without a licence.
https://t.co/EJk4SkjLVL
Most London landlords have no idea what compliance actually costs until the invoice lands.
We built a free calculator. Pick your borough, property type, and services — get an instant estimate.
No signup. No email required.
https://t.co/NNryVHnUo2
#LandlordUK #PropertyCompliance
Built automatic property revalidation for FairLet:
Change a rule → every affected property recalculates instantly.
No cron jobs, no manual patching. Just event-driven correctness in Go
If you’re an early technical founder, don’t overbuild.
Architect for today, not your imaginary Series B.
A well-structured monolith can take you a long way.
The monolith architecture gives me the biggest advantage any solo/lean founder needs:
Speed.
Shipping beats architecture debates.
Momentum beats cleverness.
Simple systems win early.
FairLet doesn’t need microservices yet.
It needs to solve a real problem fast.
Clean Architecture still gives me separation of concerns:
Domain → Services → Handlers → Storage
So the monolith stays organised, testable, and easy to grow.
If (when) FairLet gets traction, the boundaries to split services later will already exist.
A monolith lets me move faster:
• 1 repo
• 1 deploy pipeline
• 1 place to debug
• 1 shared domain model
• No distributed transactions
• No premature infra complexity
MVPs should optimise for momentum, not elegance.
Microservices are a scaling solution, not a starting point!
Most teams don’t have a traffic problem.
They have a focus problem.
Adding service-to-service networking, retries, tracing, versioning, and infra overhead too early slows you down before you’ve even validated anything
Two weeks into building FairLet in public:
✓ Go backend foundations
✓ Auth + email verification
✓ Property + landlord domain models
✓ Early rules engine
✓ Readiness Score structure in place
Crazy how fast progress feels when the mission is clear.