21–30 of 253 posts
Earlier quoted context omitted.
So your designers debug your React code now when the AI messes up?
Leading question, feel free to ask a more honest one.
Excellent post. I share the author's sentiment which is essentially "to hell with Figma, at least fix Sketch". Been feeling very lonely in may hatred towards Figma, which is for a whole bunch of reasons (among others, it's an incredibly shitty, memory and CPU hungry Electron app that looks and feels worse than any more or less well designed web site), but now after reading this I realize the number of reasons has dou…
It may look like a crappy Electron app, but Figma has a quite interesting architecture. The browser editor is developed in C++ and cross-compiled to JavaScript with emscripten. The rendering engine looks like its handling HTML, but it's actually rendering their own document format for cross-browser consistency. They have their own CRDT implementation to handle multi-user edits. [0] https://www.madebyevan.com/figma/bu…
Earlier quoted context omitted.
How is it a leading question?
>A leading question is a query that suggests the desired answer or puts words into a witness's mouth, often guiding them toward a "yes" or "no" response.
So let me get this straight (Pretend I'm 50, a developer since childhood, but I can't CSS to save my life) are there shops where developers, even front end developers, have to talk to designers who are't just sketching an idea for a logo or landing page, but designers who run this Figma thing and maintain the entire products "design" in some "style database"? And the idea is that these designers - who aren't develope…
So tools like Figma is nice in that regards as it's simpler to iterate on (From simple to hardest: Sketch on whiteboard|paper, Wireframe tools like Balsimiq, Figma|Sketch, css code) because it's pure fiddling with various properties. Figma has direct feedback while the code may require a compilation phase.
Earlier quoted context omitted.
>A leading question is a query that suggests the desired answer or puts words into a witness's mouth, often guiding them toward a "yes" or "no" response.
It was just restating what you already said; no need for this specious response.
I did not say anything of the sort.
Earlier quoted context omitted.
Leading question, feel free to ask a more honest one.
All right, here's a statement: your designers won't even know when the code is wrong. Just because it compiles it doesn't mean it's fine. They lack code judgment in the same way your coders lack design judgment.
In response I suggest that the engineers using AI also lack code judgement (because they are not reading it either). I don't think questioning the AI use is the actual topic here, it is the shifting roles. Who says it's the designers that are taking the new meta-role? It's probably the FE's honestly.
The role shifting doesn't mean that it's the best path forward. I'm simply stating that it is happening.
Building the same design system component in code versus in Figma is going to be slightly more succinct in code; Figma’s primitives don’t have the sort of conditionals and control flow that code has. But code is much less malleable than drawing on a screen, and creative freedom is harder to achieve in code.
UI can fix the gap where code feels less malleable than Figma, but complexity comes largely from the worlds that humans create, and humans apparently want to create 8 modes for 4 products and 2 light/dark modes. If you want the same setup in Claude, it’ll be a little easier to maintain, but not much less complex.
Earlier quoted context omitted.
So your designers debug your React code now when the AI messes up?
I've been a developer for over 2 decades and I've been using AI in our react codebase for the past 3 months. Outside of some optimizations there's not much a designer couldn't debug through Claude Code. 90% of the industry is toast. I want to be wrong because I'm watching the death of my entire career, but everything I've seen is pointing to this as an inevitability. We are shipping better and more secure code, and d…
Earlier quoted context omitted.
Leading question, feel free to ask a more honest one.
All right, here's a statement: your designers won't even know when the code is wrong. Just because it compiles it doesn't mean it's fine. They lack code judgment in the same way your coders lack design judgment.