DEV Community: Abdessamad Bettal

I got tired of QR code generators gatekeeping SVG exports, so I built one that doesn't

Abdessamad Bettal — Fri, 19 Jun 2026 00:25:21 +0000

Here's a small thing that's been bugging me for a while: you need a QR code, you Google "QR code generator," you land on one of the usual suspects, you customize your colors and add a logo, and then — right as you go to download — you hit a wall. PNG export is free. SVG, the format you actually need for a print job or a vector pipeline, is locked behind a paid plan. Sometimes there's a "create an account first" gate too, just for good measure.

None of this is actually expensive to provide. Generating a QR code is cheap, deterministic, and well-understood. The friction is a business model, not a technical constraint. So I built QrFast.io — a QR code generator with no signup, no paywall on exports, and full SVG/PNG downloads from the first interaction.

What it does

QrFast is intentionally narrow in scope: you give it data, you customize the look, you download a file. That's the whole loop.

No login, no account, no saved history. Open the page, generate, download, done. There's nothing to sign up for and nothing tracking your generation history.
Multiple data formats, not just plain URLs — WiFi credentials, vCards, WhatsApp deep links, Bitcoin payment URIs, and calendar events are all supported as first-class input types, each with its own structured form instead of forcing you to hand-format a string.
Full visual customization — foreground/background colors, dot styles, and logo embedding, all rendered live as you type. No "generate then preview" round trip.
SVG and PNG exports, both free, both immediate. SVG specifically matters here because raster QR codes get blurry the moment you scale them for a banner, a poster, or a packaging insert. Vector output means the code stays crisp at any size, which matters a lot more for QR codes than people expect — a soft edge on a finder pattern is exactly the kind of thing that breaks a scanner.

Why I built it this way

The honest answer is that QR generation is a solved problem from an algorithmic standpoint — error correction levels, module placement, quiet zones, all standard. The differentiation isn't in generating a QR code, it's in not getting in the user's way while they do it. So the design constraints I set for myself were:

Every interaction should feel instant. No full-page reloads when you change a color or switch from URL to WiFi mode. The preview updates in place.
Nothing should require an account. If a tool's core function is "take input, produce file," account creation is pure overhead for the user and a data liability for me.
Vector output isn't a premium feature. It's table stakes for anyone using this for print.

The stack, for the curious

The frontend is Nuxt 3, the backend is Laravel. Nuxt handles the reactive form state and live SVG preview — the QR rendering recalculates client-side as you type, so there's no network round trip just to see what a color change looks like. Laravel sits behind it for the heavier lifting: persistent format validation, any server-rendered generation paths, and keeping the whole thing fast enough that SSR doesn't become a bottleneck.

One nuance I went back and forth on: how much of the QR encoding logic should live client-side versus server-side. Client-side keeps the live preview snappy and removes a network hop, but you end up duplicating validation logic (e.g., WiFi credential escaping, vCard field formatting) on both ends if you're not careful. I landed on doing the visual rendering and live preview client-side, with format-specific payload construction validated again server-side before the final export — mostly to make sure malformed input never makes it into a generated file, especially for formats like vCard where a stray special character can produce a QR code that looks fine but fails to parse on scan.

What's next / where I'd love feedback

QrFast is live now and free to use at qrfast.io. It's still early, and there are a few things I'm actively thinking about:

Rendering edge cases — very dense payloads (long URLs, full vCards with multiple fields) push toward higher QR versions with smaller modules, and I want to make sure the dot-style customization doesn't compromise scannability at that density.
UI/UX for format switching — right now each format (WiFi, vCard, WhatsApp, Bitcoin, Event) has its own form, and I'm curious whether that's intuitive enough or whether it needs better signposting for someone who lands on the URL tab by default and doesn't realize the other formats exist.
Logo embedding and error correction — embedding a logo eats into the QR's effective error correction budget, and I'd rather over-warn users about logo size than ship a code that fails to scan in the wild.

If you try it and have thoughts — on the rendering quality, the UX, or anything that broke — I'd genuinely like to hear it. The whole point of building it free and frictionless was to get it in front of more people who'd actually use it, so real feedback from real use cases is the most useful thing anyone could send my way right now.

How to create a Standout Full stack developer Resume with real tips and Free Tool that helped me

Abdessamad Bettal — Sun, 23 Feb 2025 11:29:37 +0000

If you’re a full-stack developer looking to land your next big opportunity, your resume needs to stand out. It’s not just about listing technologies you’ve used—it’s about presenting your skills and experience effectively so hiring managers and recruiters take notice.

I recently tested Cviya to create my resume, and I was honestly impressed. It’s free, super easy to use, and makes building an ATS-friendly resume effortless. If you’re struggling with formatting or just want to save time, I highly recommend trying it out.

In this guide, I’ll break down exactly how to craft a high-impact full-stack developer resume, share real-world examples, and show you how Cviya made my resume-building experience smoother. Let’s dive in! 🚀

Why a Strong Full-Stack Developer Resume Matters
Hiring managers spend less than 10 seconds scanning resumes before deciding whether to continue reading. If your resume isn’t clear, well-structured, and keyword-optimized, it may never even get seen by human eyes!

What Makes a Great Full-Stack Developer Resume?
✅ Clean, professional design (no distractions!)
✅ ATS-friendly formatting (so it doesn’t get rejected by resume scanners!)
✅ Strong technical skills section
✅ Projects & real-world experience
✅ Quantified impact (numbers make a difference!)

I’ve seen a lot of messy developer resumes that bury key information or make it hard for recruiters to understand skills quickly. Let’s fix that.

Step 1: Pick the Right Resume Format
The best resume format depends on your experience level:

🔹 Reverse-chronological (Best for experienced devs): Lists your latest job first.
🔹 Functional (Skills-based) (Best for career changers or juniors): Focuses on skills rather than work experience.
🔹 Hybrid format (Best of both worlds): A mix of skills and experience.
🚀 Pro Tip: If you’re a junior dev, focus on projects rather than job history.

Step 2: Essential Sections of a Full-Stack Developer Resume
🔹 Contact Info (Keep It Simple!)
✔ Full name
✔ Professional email (e.g., john.doe@gmail.com)
✔ GitHub & LinkedIn links
✔ Portfolio or personal website (if available)

❌ Don’t include: Age, marital status, or a photo (unless required).

🔹 Professional Summary (Your Elevator Pitch)
A short 2-3 sentence summary of your skills & experience.

✅ Example:

🚀 Full-stack developer with 4+ years of experience building scalable web applications using React, Node.js, and PostgreSQL. Passionate about writing clean, maintainable code and optimizing performance. Open-source contributor and strong advocate for Agile methodologies.

🔹 Technical Skills (Show Your Stack!)
💻 Frontend: React, Vue.js, Angular, JavaScript (ES6+), TypeScript
🖥 Backend: Node.js, Express, Django, Ruby on Rails
📦 Databases: MongoDB, PostgreSQL, MySQL
☁️ Cloud & DevOps: AWS, Docker, Kubernetes, Firebase
🛠 Tools: Git, GitHub, CI/CD, Jest, Webpack

✅ Use job descriptions to tailor your skill list!

🔹 Work Experience (Show Impact, Not Just Tasks!)
Use action verbs + results to describe your experience.

✅ Example:

Full-Stack Developer | XYZ Tech | 2021-Present

Developed and deployed a React & Node.js app that increased user engagement by 35%.
Optimized PostgreSQL database queries, reducing API response time by 40%.
Led a team of 4 developers to integrate CI/CD pipelines, cutting deployment time by 50%.
❌ Avoid generic phrases: "Worked on full-stack projects."

🔹 Projects (Show Your Work!)
If you’re a junior dev or transitioning, highlight side projects & open-source contributions.

✅ Example:

🔹 E-Commerce App (React, Node.js, MongoDB)

Built a secure full-stack e-commerce platform with JWT authentication.
Integrated Stripe payments, processing $50,000+ in transactions.
Open-source on GitHub: [GitHub Link]
🔹 Education & Certifications
📜 Degree: List your CS degree (if applicable).

🎓 Certifications:

AWS Certified Developer
Full-Stack Web Development (Udemy, Coursera, etc.)
Step 3: Bonus Tips to Make Your Resume Stand Out
✅ Keep it concise – 1 page for juniors, max 2 for experienced devs.
✅ Use keywords from job descriptions to optimize for ATS (resume scanners).
✅ Include GitHub & Portfolio – Show real projects!
✅ List open-source contributions if applicable.
✅ Don’t list outdated tech (e.g., jQuery, Flash).

How Cviya Helped Me Build My Resume (And Why You Should Try It!)
I was testing different resume builders, and Cviya was by far the easiest and best experience I had.

🔥 Why I Loved Cviya:
✅ Pre-designed, customizable templates – No need to mess with formatting.
✅ ATS-friendly – No worries about rejection from automated resume scanners.
✅ Super intuitive & fast – I built my resume in minutes!
✅ It’s completely free!

I highly recommend trying Cviya if you want a quick, professional, and clean resume without the hassle of formatting everything manually.

👉 Try it now: Cviya.com 🚀

Final Thoughts
A well-crafted full-stack developer resume tells the story of your impact, not just your skills.

🔹 Use clear formatting
🔹 Showcase projects & contributions
🔹 Quantify impact with numbers
🔹 Tailor your resume to the job

What’s your biggest struggle with resume building? Let’s discuss in the comments! 👇

🚀 Need a resume? Try Cviya.com – it’s free and works like a charm!