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
Documentation is one of the most underrated parts of Quality Assurance.
Clear test cases and bug reports save teams a ton of time. Less back-and-forth, and way smoother collaborations. That's what actually helps teams ship products faster.
I've put together some real examples in my portfolio showing how I document QA artifacts in an enterprise setting, from test cases to bug reports.
Check it out: jawadakram.dev
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
Reviewing your audit log workflow for a legal tech platform
I recently created a demonstration of an AI-powered penetration testing workflow in an authorized lab environment.
The workflow covers:
✅ AI-based reconnaissance
✅ Automated vulnerability discovery
✅ Safe vulnerability validation
✅ Attack-path analysis
✅ Evidence collection and CVSS assessment
✅ Automated security report generation
AI can help security professionals reduce repetitive work, organize evidence, and accelerate reporting. However, human validation remains essential for confirming findings, understanding business impact, and avoiding false positives.
This project uses a fictional application and simulated security findings. No real systems or data were involved.
💬 Where do you think AI can provide the most value in penetration testing: discovery, validation, or reporting?
#AISecurity #Cybersecurity #PenetrationTesting #ApplicationSecurity #EthicalHacking #SecurityAutomation #AppSec #DevSecOps #AI
13:40: a finished Figma frame. 15:48: this, live on Vercel
Claude wrote every line of the code. I spent those two hours on the part clients actually pay for: looking at each version and saying what's off
17 commits, each one deployed. My notes went in as screenshots with red circles:
→ make the button edges look like ticket cutouts
→ replay the story chips every time you scroll past them
→ spacing 156, then 92, then back to 156
What made it fast was one Figma frame called "Ready for Dev". Every size, color and gap came from there, so nobody had to guess what the mockup meant
For a founder this means a real link on day one, and a fix you ask for at lunch is live by the afternoon
This is the workflow! From Figma to live in 2 hours - love that you spent time on what actually matters: having taste and directing. 17 deploys is wild! 🚀