The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Built a reproducible n8n workflow-repair fixture today. The broken version looked handled but had two structural defects: no bounded retry policy and an unwired separate error output, so failures could disappear. The repaired version adds 3 bounded attempts, routes the error branch to a sanitizer, and separates success and failure paths. Deterministic audit: broken 2 findings → repaired 0; repository tests 3/3 pass. Lab fixture, not a client result; reserved .invalid URL, no credentials or personal data. Full before/after proof: https://blaidlink-labs-services.rluriea.chatgpt.site/#repair-proof
blaidlink-labs-services.rluriea.chatgpt.site
Blaidlink Labs — Decision-ready public data signals
Blaidlink turns authorized public web and government data into source-linked, decision-ready signals.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Found an interesting Webflow build this week — and it impressed me and frustrated me at the same time.
Visually strong: solid typography, animations aren't overdone, mobile looks clean. The designer clearly knows what they're doing.
But under the hood:
— classes named like .div-block-47 (anyone recognize this?)
— no Client-First structure, everything dumped in one pile
— hero section jumps on mobile scroll because of 100vh instead of 100dvh
— Lenis is connected but conflicts with the marquee animation's resize event
A beautiful site that the next developer will spend three days cursing.
Not a callout — I had the exact same hero bug this week and spent half a day diagnosing it. The difference is I now know where to look.
Craft isn't just what you see. It's what holds up when you touch it.
#webflow #webdev #buildinpublic #clientfirst #frontend
Talon Audit — a privacy-first website exposure and remediation platform
I built Talon Audit to solve a problem most website tools handle badly: they detect issues, but rarely help teams understand what matters, what to fix first, or whether the fix actually worked.
Talon analyses public-facing websites across four connected domains:
Exposure — browser protections, cookies, scripts, TLS, and visible configuration risks
Integrity — broken resources, routes, errors, forms, and reliability regressions
Experience — accessibility, mobile usability, speed, and interaction friction
Conversion — messaging, trust signals, pricing paths, forms, and calls to action
The product follows a complete improvement workflow:
Detect → Explain → Fix → Verify → Monitor
Every finding is structured around evidence, severity, confidence, impact, remediation guidance, and a verification method.
I led the project from strategy to launch, including:
product positioning and methodology
UX/UI and design system
full-stack implementation
AI-assisted analysis and remediation workflows
privacy and security boundaries
pricing, demo experience, and launch
Talon performs passive, low-impact analysis only. It does not exploit systems or claim to replace authorised penetration testing.
Built through a terminal-first AI-native workflow using Codex 5.5 and Claude Fable.
Live product: talonaudit.com
Role: Product Strategy, Product Design, Full-Stack Development, AI Development
Every messy backlog I've been handed had the same root cause. It wasn't lazy grooming and it wasn't the wrong tool. It was entry points. Requests came in through Slack threads, sales calls, founder DMs, support escalations, hallway promises. Each one became a ticket, because turning something into a ticket is the polite way to say yes without doing anything.
Do that for a year and you have 400 tickets, of which maybe 60 are real.
The fix I install in every team is boring: one intake channel. Every request, from the CEO's shower idea to the angriest customer, enters through the same door. It gets a short triage against the same priority tiers as everything else, and it either earns a slot or gets a written "not now" with a reason attached.
The first two weeks are uncomfortable. Sales feels slowed down. The founder feels slowed down (I say this kindly, founders are usually the worst offenders). Then something shifts. Requests arrive half-formed less often, because people know they'll be asked what problem it solves and for whom. Planning gets shorter because the arguing already happened at intake. And the engineers stop treating the backlog as noise, which is worth more than any prioritization framework I know.
This doesn't take a new tool. It takes one rule, and somebody willing to enforce it on the people who signed their paycheck.
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?