> There’s a big long clear approach to Dunning-Kreuger’s Mt. Stupid with dev work.
Is it really that clear? Or do we just think so because most of us here are devs, while everyone else is thinking “Wow what happened? That codebase was great until suddenly it wasn’t.”
Re:Your Website Is Not for You
by DrewADesign on Sunday May 03, 2026 @02:40PM
(#48000011)
Yes it’s really that clear. The moment non-technical people see code syntax or hear technical jargon, they instantly nope out. That’s why people ask their developer friends and family to fix their computers — they don’t know the difference. It’s all just ‘tech’ to them. It’s also why people toil away at bonkers “no-code” machinations that would have been far simpler with a little more tech knowledge… it’s very intimidating to outsiders. OTOH, far fewer people even know what problems designers are meant to solve, let alone judge the solution, but many think ‘well I have good taste and I’ve worked with designers before’ and confidently wield their broken ideas based on false assumptions.
The complexity in dev is a lot more obvious than the complexity in design. There’s a big long clear approach to Dunning-Kreuger’s Mt. Stupid with dev work. With design work, the whole idea is to make something that clearly communicates its purpose. That makes a lot of people think they understand what went into it because if it’s done well, the solution should feel ‘obvious.’ Getting something that feels obvious is way more nebulous and convoluted than getting from point a to point B in most dev tasks.