| |
| ▲ | doug_durham 5 hours ago | parent | next [-] | | In my opinion this should have always been the case. All designers should be able to code and do html/css. It's the medium of design. | | |
| ▲ | esafak 5 hours ago | parent | next [-] | | HTML and CSS, sure, but modern frontend design is way more than that; it's a jungle out there. | | |
| ▲ | operatingthetan 4 hours ago | parent [-] | | React, Nextjs, Vue, Nuxt, and Angular are pretty much what AI is the very best at coding in my experience. Probably because they are all meant to build essentially the same thing with different curtains. |
| |
| ▲ | re-thc 5 hours ago | parent | prev [-] | | > All designers should be able to code and do html/css. It's the medium of design. So a fashion designer can mass produce clothing? So an interior designer can build a house? This designer should has never held. | | |
| ▲ | rcxdude 4 hours ago | parent | next [-] | | Fashion designers can, in general, work with fabric, yes. And an interior designer should probably have some idea of how to paint at the very least. To me with web design so much of what matters is encoded in the CSS and HTML that it is the final design product. Anything produced before is a sketch, a concept, but it's not a design. | |
| ▲ | operatingthetan 4 hours ago | parent | prev [-] | | The analogies you have offered aren't great. For example designers and developers both use the computer as their primary medium of working. Their outputs resemble each other very closely, despite having a different underlying form. Contrast that to the interior designer building a house, well those are different mediums. There is no efficiency gain from the interior designer designing the plan and also implementing it. Where as with a designer working in code there is one. Fashion designers do indeed make clothing by hand, it's a very important part of their craft. This example disproves your stance. |
|
| |
| ▲ | micromacrofoot 6 hours ago | parent | prev | next [-] | | 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 doing it easily twice as fast. Many development teams can be cut in half today with no reduction in output. I don't want to say it out loud at work yet, but we're actually producing too much. | | |
| ▲ | beachy 5 hours ago | parent | next [-] | | I've been writing code for 50 years and it looks now that we have seen sunrise and are about to see sunset on humans writing code by hand. Is that bad? Not to anyone who has managed dev teams and is familiar with the incredibly tortuous and painful business of trying to corral a bunch of humans with varying skill and enthusiasm levels to create software. We have tied ourselves in knots with things like Agile just trying to work around the fact that software development is so slow and arduous. Many times back in the waterfall days I have written up design documents to kick off dev teams on multi-week or month projects. Now I could feed those into Claude Code and get results in days. This stuff is exciting beyond belief in just getting shit done. This is a golden era for any established company with an existing customer base. My question to them would be "with Claude Code, why aren't you carving through that massive backlog of feature requests that has been building up over the years?". A lot of people seem to look at this as job threatening, and it surely is for junior devs. But for companies that already have a strong senior talent bench, it's time to raise the ambition levels and ask not how many jobs can be shed, but instead just how fast and hard can we go now we have these new superpowers. | | |
| ▲ | slopinthebag 4 hours ago | parent [-] | | This is so context-dependent. Coding some generic crud app is indeed becoming more automated, but most of the stuff I end up building is just way outside the capabilities of current LLMs to accomplish without significant steering and gasps hand written code. Most of the stuff LLMs are good at ones hotting are the same things a non-coder could build with no-code platforms anyways. Which is great imo, it means we can utilise our skills and expertise on stuff that is more "cutting edge". |
| |
| ▲ | bombcar 5 hours ago | parent | prev | next [-] | | 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, now considered barely above a macro assembler), to high-level languages like Java and even higher ones (arguably) like Rust. Every one of those transitions has resulted in more programmers - though not necessarily the same programmers. 354: https://en.wikipedia.org/wiki/Computer_(occupation) 892: https://en.wikipedia.org/wiki/The_Story_of_Mel | | |
| ▲ | zaptheimpaler 5 hours ago | parent | next [-] | | But things really are different this time. Computers and software were nascent industries with lots of room to grow, lots of software to build in previous transitions. Today software and technology companies are the biggest in the world. Every industry uses software. Getting your web app, mobile app or game discovered is actually a huge problem today because we have so much software. There is not infinite demand for software, or for anything else, even if it seems that way in the early days. | | |
| ▲ | bombcar 5 hours ago | parent [-] | | The Olde Days were custom code for a business doing business things (only they could afford a computer, and some universities), then there was a Cambrian explosion of software sold by individuals or small developers to many (80s and 90s), then we've moved to large companies and SaaS. I think we're about to cycle back to "custom code" except now it's for everyone, by AI - you don't need to find the to-do app of your dreams; you can code one for yourself in a fever-dream. The era of "write Wolfenstein 3D in a few months and make millions" are gone, but they've been gone a long time already. | | |
| ▲ | rapnie 3 hours ago | parent [-] | | Or - there was a HN discussion on this half year or so ago - there's consolidation again, and there will be AI, but no code. Domain expert talks to the AI, perhaps with an expertised intermediary. AI spins up a whole new 'software platform' for the customer.. internally. Offers all the UI that is needed to work with it.. still 'in the cloud' i.e. in AI data centers. Customer happy, devs less happy. |
|
| |
| ▲ | throw310822 5 hours ago | parent | prev [-] | | AI isn't a technology that replaces programmers, it's a technology that replaces generic human beings. The manager of your agents will be an agent, too. |
| |
| ▲ | operatingthetan 5 hours ago | parent | prev | next [-] | | 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. | | |
| ▲ | only-one1701 5 hours ago | parent [-] | | I would ask this: which is the worse failure mode —- design not quite right, or users can’t access the app? | | |
| ▲ | girvo 5 hours ago | parent | next [-] | | On the other hand, teaching taste is quite hard, and is what people respond to and what designers learn. Teaching programming is a bit of mostly solved problem, today anyway. | | |
| ▲ | operatingthetan 4 hours ago | parent [-] | | Realistically this doesn't mean all pure designers go away. Large orgs can have a small team that set the overall style guide and designs important pages, and the rest of the org just follows using AI to iterate. |
| |
| ▲ | esafak an hour ago | parent | prev [-] | | That's the kind of question you will have to ask if you don't hire right. I get collapsing frontend/backend and PM/UI/UX but two then collapse code and product may be a bridge too far. |
|
| |
| ▲ | troupo 5 hours ago | parent | prev [-] | | > Outside of some optimizations there's not much a designer couldn't debug through Claude Code. 90% of the industry is toast. 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 |
| |
| ▲ | only-one1701 5 hours ago | parent | prev | next [-] | | That’s what CEOs think lol. Let’s see if it pans out! | | |
| ▲ | lodovic 5 hours ago | parent [-] | | "I have an error when i click on the orange button, see screenshot. fix it." |
| |
| ▲ | operatingthetan 6 hours ago | parent | prev [-] | | Leading question, feel free to ask a more honest one. | | |
| ▲ | ioasuncvinvaer 6 hours ago | parent | next [-] | | How is it a leading question? | | |
| ▲ | hombre_fatal 6 hours ago | parent | next [-] | | They entailed scenario that isn't entailed by the person's claim. i.e. The OP doesn't need to answer yes to their question for OP's claim to be true, yet their question pretends otherwise. (non sequitur) | |
| ▲ | operatingthetan 6 hours ago | parent | prev [-] | | >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. | | |
| ▲ | viccis 6 hours ago | parent [-] | | It was just restating what you already said; no need for this specious response. | | |
|
| |
| ▲ | esafak 6 hours ago | parent | prev [-] | | 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. | | |
| ▲ | operatingthetan 5 hours ago | parent | next [-] | | Thank you. 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. | |
| ▲ | nslsm 5 hours ago | parent | prev [-] | | It's very easy to know when code is wrong: it doesn't work the way it's expected to. So you explain to the AI what's wrong and the AI fixes it. | | |
| ▲ | only-one1701 5 hours ago | parent | next [-] | | This isn’t meant to be sarcastic: have you ever worked for a real company? | |
| ▲ | esafak 5 hours ago | parent | prev | next [-] | | Your designers are going to be looking at the layout; they're not going to notice if it's slow, uses too much memory, is not maintainable, doesn't follow repo patterns, etc. Do you think it is reasonable to expect a person with an arts degree to know this? | | |
| ▲ | jmye 5 hours ago | parent [-] | | > Do you think it is reasonable to expect a person with an arts degree Of course it is. The only people who think your fucking college degree determines your knowledge level and ability are teenagers and people who are so deeply untalented that it’s the only way they feel qualified. |
| |
| ▲ | thunderfork 3 hours ago | parent | prev [-] | | As we know from THERAC-25, etc., comprehensively verifying that code works the way it's expected to is not actually very easy - it's perhaps one of the hardest parts of building any system more complex than a toaster. | | |
| ▲ | nslsm 3 hours ago | parent [-] | | Thankfully the CRUD app that is being developed by some random startup is not likely to cause as much harm as the THERAC. |
|
|
|
|
|