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
Dotnet Audit Studio is accepting the first three pilot projects for a fixed-scope .NET Backend & AI Readiness Audit.
Best fit:
• an existing C# backend that became hard to change
• slow EF Core or SQL paths
• reliability issues around DI, async code, HTTP clients, or background workers
• weak tests or CI/CD gates
• a repository that needs clearer boundaries before introducing coding agents
You receive:
Executive summary
Architecture map
5–7 prioritized findings
Concrete recommendations and effort estimates
Remediation backlog
Recorded walkthrough
Launch package: $199, one service/repository, three business days, no code changes included.
The process is asynchronous and fixed-scope. Production infrastructure and penetration testing are not included. Private code is not sent to third-party AI services without explicit permission.
Public sample report: https://github.com/Dalkory/DotnetAuditDemo/blob/main/AUDIT_REPORT.md
Contact: taushkanovdaniil@gmail.com | Telegram @DanilDotNet
github.com
DotnetAuditDemo/AUDIT_REPORT.md at main · Dalkory/DotnetAuditDemo
ASP.NET Core backend audit case study: 15 findings, prioritized remediation plan, and a before/after PR. - Dalkory/DotnetAuditDemo
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
Terra — AI Environmental Risk Platform
Designed the landing page and product UI for Terra — a platform that helps land developers and engineering teams see environmental risk (soil stability, tree canopy loss, water table depth) before breaking ground.
The challenge:
Development decisions are usually based on estimates, not real ground data — and by the time issues show up, it’s often too late to reverse them. The interface needed to make complex sensor/AI data feel immediate and trustworthy, without losing emotional weight.
The solution:
Raw, organic photography (wildflowers, grass, natural terrain) paired with clean glass-panel data cards — creating a visual tension between “nature” and “precision engineering.” Bold editorial typography carries the emotional message, while translucent metric cards surface real numbers: soil stability, canopy loss %, water table depth.
A strong example of turning dense environmental data into something a non-technical stakeholder can understand in seconds.
Nice one
What I check before calling a SaaS MVP launch-ready
A SaaS MVP is not launch-ready just because the main flow works once.
While building Elyris, a booking and CRM SaaS platform for service professionals, I learned to look at the product as a full system — not just screens.
Before launch, I usually check:
• Can the user complete the core workflow without confusion?
• Are booking, payment, confirmation and message delivery treated as separate facts?
• Are edge cases handled clearly?
• Does the backend own the source of truth?
• Are error states understandable?
• Are mobile and slow-network paths usable?
• Is there a clear QA / smoke checklist before release?
• Do we know what is still unfinished?
For early SaaS teams, this kind of product and QA work can be the difference between “it technically works” and “it is safe enough to put in front of real users.”
That is the kind of work I focus on: product scoping, workflow design, QA, release readiness and AI-assisted SaaS delivery.
That point about launch readiness being a full-system question, not just a happy-path demo, really lands. Which failure mode in Elyris changed your checklist the most?
Day 5/30: MISREGISTER
An operating-room case can still look ready on paper after it has stopped being operationally executable.
I built MISREGISTER to make that gap physical.
CASE 04 is connected to four changing dependencies:
— staffed OR team
— sterile instrument set
— postoperative ICU bed
— remaining operating-room time
As those windows drift apart, the operating list stays unchanged.
The signature moment: the crank freewheels to the end-stop while CASE 04 still reads SCHEDULED.
Only after that failed test does a human re-strike the case as DELAYED or RESEQUENCED.
This is not clinical decision support. It is a synthetic operational prototype exploring the difference between a scheduled slot and executable capacity.
Built with React, TypeScript, SVG, Playwright, Remotion, Claude Code, Kimi, Agent Reach, ChatGPT, and AI33Pro.
Live prototype:
https://faadil1.github.io/misregister-day-5/
Making readiness physically understandable instead of dashboard-inferred is such a good design goal, that's usually the exact gap that causes people to ignore dashboards in the first place. Curious to see where you take the physical interaction idea next.
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?