3 ms·
> Some user(s) have some kind of task that they want to achieve. They could get together and communicate well with some kind of developer who can help them achi
by meheleventyone 4y ago
> Some user(s) have some kind of task that they want to achieve. They could get together and communicate well with some kind of developer who can help them achieve or complete that task; all of which is likely doable without this middle layer of whatever this is.
Whilst this is definitely true the question is what would the end result be like. All you're doing is having the developer engage in design which isn't a bad thing if they have the temperament and skillset to do it. Which not all developer's actually do. As someone leading a very practically oriented design team that develop all their designs it's painfully obvious that very experienced developers are not inherently good product designers even if they are very good at designing the code they write. In a large part I think the process of design is mostly universal but the nitty gritty parts of it are actually what matter.
There’s definitely a lot of fluff written by consultants with things to sell you though. But that’s not really different to other disciplines. In particular “design thinking” is the “agile coach” for designers.
- taneq 4y agoHow can you be very good at designing the code you write if you're not somewhat good at designing things for people to use in general? Sounds like you'd get incredibly clever algorithms doing something of questionable utility through an awkward interface.
- meheleventyone 4y agoYes. Like git. Or many open source projects that tend to compete on feature set but not usability with paid products. Early Blender is a great example there. The great thing about being able to code is that you can build near enough anything. The trap of coding is that you get more enamoured with the act than the end result from the perspective of other people.