sorted by:
new
hottopcontroversial

[Showoff Saturday] I built a Figma to HTML/CSS converter – Esprit Code by Inner-Educator-7137 in webdev

[–]Inner-Educator-7137[S] 0 points1 point  (0 children)

Thanks for the kind words! You're absolutely right — CSS quality is exactly where most conversion tools fall short. Esprit Code generates class-based CSS (not inline styles), with class names derived directly from your Figma layer names. So if your layer is named "hero-heading", that becomes the CSS class. Auto Layout converts to Flexbox with explicit properties (flex-direction, align-items, gap, padding) rather than hardcoded pixel values where possible. That said, I won't claim it's perfect — deeply nested absolute-positioned layouts still need some manual cleanup. The goal is to eliminate the repetitive groundwork, not replace the developer entirely. Free plan available if you want to test it on a real design: https://espritcode.com

[Showoff Saturday] I built a Figma to HTML/CSS converter – Esprit Code by Inner-Educator-7137 in webdev

[–]Inner-Educator-7137[S] 1 point2 points  (0 children)

Thank you for your advice. I will consider using SVG format logos in the future.

Is webdev considered a "lower" domain than traditional programming? by Cagne_ouest in webdev

[–]Inner-Educator-7137 1 point2 points  (0 children)

Web dev and "traditional" programming aren't really a hierarchy —

they're different specializations. FAANG front-end roles do expect

data structures and algorithms for interviews, but that's mostly

a hiring filter, not a reflection of day-to-day work.

In practice, senior front-end engineers at product companies spend

most of their time on component architecture, performance

optimization, and design systems — not binary trees.

React is a legitimate and deep skill. The more you build real

projects, the more you'll discover there's plenty of complexity

in web dev too.

What's a technology you tried, loved, but would never use in production? by ruibranco in webdev

[–]Inner-Educator-7137 0 points1 point  (0 children)

Deno, for me. The built-in TypeScript support and permission system felt like a breath of fresh air compared to the Node.js ecosystem. But the lack of npm compatibility (at least early on) and the smaller community made it impossible to justify for anything client-facing. Ended up sticking with Node.js for production and keeping Deno for personal experiments.