4 ms·

For me, this article comes around more as a designer-influencer production than a form of deep insight. He writes polarizing content and converts the reaction

by nbzso 4y ago

For me, this article comes around more as a designer-influencer production than a form of deep insight. He writes polarizing content and converts the reaction to "his own service for designers portfolios". Regularly. >One asks when the deadline is. The other knows the answer is "ASAP,” so they propose their own timeline. I always ask when the deadline is. Design is part of the production process. The production process even when I control it (as a PM and PD) is bound to the projected timeline. >One designs exactly what they’re told. The other knows what they’re told is just one idea, and explores beyond it. Again, there is a place and time when you design to spec and exploration is not limitless. Exploration has boundaries. >One turns in their first or second draft. The other does as many drafts and explorations as possible within the time allotted, then shares their favorite options. Actually in high level design thinking, designers "favorite" option has no merit. Forming a logical design solution over a set of UX research data and actual testing is the winning method.

malfist 4y ago
There was a book I read one time, early in my journey, called "Hardcore Java" It's promise was to take you from beginner java engineer to an advanced one. It was written by someone who "knew" the craft and was ready to pass on their anointed knowledge. The author of the book had just recently made the progression to what they considered advanced, so the book was chock full of beginner-cum-expert advice like this article. And it was all wrong. The errata for the book is more pages than the book itself. It had the basics of java incredibly wrong, most of the code samples in the book were not compilable, it was a mess. This article strikes me the same way. Someone who has a little more knowledge than a beginner, but hasn't yet learned how little they know. So they want to show off their new knowledge with gatekeeping "lessons" The difference between junior and senior isn't just about going from "easy way" -> "best way" It's about understanding when you can get away with the easy way, when the best way is too hard for a situation, or the situation isn't called for. It doesn't fit nicely into X does Y and A does B. Design/Engineering isn't black and white.

by nbzso 4y ago

malfist 4y ago

There was a book I read one time, early in my journey, called "Hardcore Java" It's promise was to take you from beginner java engineer to an advanced one. It was written by someone who "knew" the craft and was ready to pass on their anointed knowledge. The author of the book had just recently made the progression to what they considered advanced, so the book was chock full of beginner-cum-expert advice like this article. And it was all wrong. The errata for the book is more pages than the book itself. It had the basics of java incredibly wrong, most of the code samples in the book were not compilable, it was a mess. This article strikes me the same way. Someone who has a little more knowledge than a beginner, but hasn't yet learned how little they know. So they want to show off their new knowledge with gatekeeping "lessons" The difference between junior and senior isn't just about going from "easy way" -> "best way" It's about understanding when you can get away with the easy way, when the best way is too hard for a situation, or the situation isn't called for. It doesn't fit nicely into X does Y and A does B. Design/Engineering isn't black and white.