My users never read my code. They judge it daily.
I lead engineering at a medical SaaS. Our users are receptionists — if the booking screen makes one hesitate, I failed.
Clean code is invisible. The UI is the whole product.
Who are your devs building for — reviewers or users?
Founders, HRs, recruiters — when you pick a freelance dev, what actually seals the deal? As a lead engineer at a medical SaaS, I am genuinely curious how you decide.
I pasted a screenshot of a landing page into an AI tool. It gave back working code.
Design-to-code turns mockups into real pages. Fast for prototypes — messy for production: broken spacing, no accessibility, no logic.
Would you ship AI-generated code to production?
My demo store has products, coupons and COD — but no real payment gateway. Just a card stub.
As a lead engineer at a medical SaaS, I show what works AND what's missing.
Which would you hire: the dev who hides the gaps, or the one who points them out?
Vibe coding ships the demo in a weekend. The bugs arrive in month two.
As lead engineer at a medical SaaS, I use AI coding tools daily — I just never ship what I cannot fully review: architecture, tests, edge cases.
Would you trust an app your dev cannot explain?
My clinic's patients book over WhatsApp now — no calls, no paper register.
As lead engineer at a medical SaaS, I built the booking flow: OTP signup, doctor discovery, advance payment, WhatsApp notifications.
What part of your business still runs on missed calls?
ChatGPT just learned to design its own screens.
GPT-6's Intelligent UI renders calculators, tables and diagrams inside the chat, shaped to your question.
Good for users. Dangerous if your product IS the interface.
Founders: is your UI a moat, or a feature anyone can generate?
As a lead engineer at a medical SaaS, I build for failure. My AI fitness coach runs as 4 microservices, not one big server — if the AI service crashes, tracking still works.
I'd rather debug one small failure than one big outage.
Hire the demo, or the system?
AI voice agents can now answer your business calls — book appointments, answer FAQs, 24/7. Upside: no lead ever hits voicemail. Downside: awkward pauses, misheard names, trust issues. Would you let AI pick up your line?
My portfolio used to impress developers.
But nobody who hires me is a developer.
Rebuilding https://t.co/eXATGEPx8L in Next.js — cutting it down as I go. Every screen left has to answer one question: can he ship?
What does YOUR portfolio prove in 10 seconds?
I run AI on my own laptop — not the cloud.
Local LLMs keep every line of client code private. Slower and weaker than cloud models, but zero data leaves the room.
For a medical SaaS, that's non-negotiable.
Would you trade AI smarts for full privacy?
Most devs show e-commerce screenshots. I built a store that works: products, cart, coupons (WELCOME10/ROOTS20), checkout flow. MERN + JWT + MongoDB Atlas. If you're hiring a dev for an online store — design, checkout, or page speed first?
Your AI chatbot doesn't know your business — that's why it hallucinates.
RAG (retrieval-augmented generation): search YOUR docs first, answer from them.
Pro: grounded answers. Con: bad retrieval = bad answers.
Is your product's AI reading your data, or guessing?
No music app felt like mine, so I built one: Wavecrate, an Android music player in Kotlin (Jetpack Compose, ExoPlayer, Room).
I'm a lead engineer at a medical SaaS — side builds are where I level up.
Founders: what tool does your business wish existed?
My users never read my code. They judge it daily.
I lead engineering at a medical SaaS. Our users are receptionists — if the booking screen makes one hesitate, I failed.
Clean code is invisible. The UI is the whole product.
Who are your devs building for — reviewers or users?
I use AI coding agents every day. They write my boilerplate, tests, and refactors. They never design the system, and nothing ships without my review. Speed is real. Judgment is not replaceable yet. Where do you draw the line with AI in your workflow?
I use AI coding agents every day. They write my boilerplate, tests, and refactors. They never design the system, and nothing ships without my review. Speed is real. Judgment is not replaceable yet. Where do you draw the line with AI in your workflow?
Resumes lie. Portfolios don't.
500 applications, same bullet points. The devs who stand out show live work, not adjectives.
Hiring managers — what's the one green flag on a developer's profile that makes you reach out?