51–60 of 253 posts
Then I looked at the usage and it said I had used 95% of my Claude design usage for the week!
This isn't a real tool. This is a plaything, if that's what they're providing as examples.
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…
But yes, the "design to code" gap has always been where designers' intentions were butchered and/or where frontend developers would discover/have to deal with designs that didn't take into account that some strings need more space, or what to do when there are more or less elements in a component, how things should scroll in real life, how things should react to a variety of screen sizes, etc.
this short meme video is funny/not funny because it hits too close to home - https://www.youtube.com/shorts/r6JXc4zfWw4 - but yes, "designers don't code and developers don't design", roughly speaking
and then of course you meet some people who do both really well... but they are pretty rare. :-)
I suppose that a layout engine made sense in the context of Flash, and you saw the future of the web as a set of keyframe animations. But the notion that there's a lot of value in creating a very heavy, high-friction abstraction between the UI/UX and the platform it ultimately runs on was always going to be a loser.
In the end, it turns out we're all just web developers, regardless of your weapon of choice.
Earlier quoted context omitted.
I think the real question is which of the four roles is going to be the one that takes over. Probably people who were already UX-Engineers.
I would ask this: which is the worse failure mode —- design not quite right, or users can’t access the app?
Teaching programming is a bit of mostly solved problem, today anyway.
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…
I've seen the "debugging" and "coding" that non-coding designers are attempting to vibe-code. 90% industry is definitely toast, but not the 90% you're thinking of. Most industry is going the way of Microsoft that cannot even display a start menu in under a second
Oh no. Figma has variables and instances and it's hard to debug bad colors. And here I am with Claude Code... That so far generated a 2000-line CSS file for a 7000-line app consisting of literally three web pages [1]. Where almost every single color, component, class and style is duplicated at least two times. Where custom classes are fighting with Tailwind classes (yes, there's also Tailwind ON TOP of custom CSS) th…
Basic web development is completely over, and will be automated end to end, product, ux, design, and the code. I have a complicated nextjs webapp, and I havent had to write front end code in six-nine months now.
If it’s used by < 1000 people, it’s not a complicated app
I tried yesterday for about an hour to have Claude design make me a simple logo (just the symbol) and didn’t get anywhere good. I’m sure for certain things like UI it’s great, and so is just Claude code, but this Claude Design thing very much to me feels like a demo and not a product. Maybe one day!
We've got an LLM using CSS and emojis and maybe pelicans riding bikes (SVGs).
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…
@kevinsync's answer is 100% correct and it's been this way for the last ~~~20? years? at least - only it was "Photoshop files hold the (design) truth" before - now it's figma. But yes, the "design to code" gap has always been where designers' intentions were butchered and/or where frontend developers would discover/have to deal with designs that didn't take into account that some strings need more space, or what to d…
You mean Fireworks. Photoshop was for graphic design. Web designers used Adobe Fireworks. Figma is a successor to Fireworks, not Photoshop.
Earlier quoted context omitted.
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…
AI is impressive but this same sea-change happened at least twice before - the era when computers went from being rooms full of women(354) to machines programmed in machine language(892) to those with screens, keyboards and even assemblers (assembly language, especially macro assemblers, were considered seriously high level at a time), to mid-level languages like C (considered needlessly complex and slow at one time,…