|
|
|
|
|
|
by cesart
5171 days ago
|
|
|
For someone very vocal and direct about one specific designer's work, there seems to be a very obvious lack of work, a portfolio or a link to a Dribbble profile on his own site. As a designer myself, I'm always down for critiques and feedback (especially when it's a tough pill to swallow — this is what keeps me improving), but Michal, your post was overly critical and not constructive in any way. You mentioned your youth and ambition — being a designer is all about communication, whether in creating a product for your users, in pitching clients, in explaining functionality to an engineer, etc., and in my opinion, this is not the way to communicate with someone regarding their work, designer or not. Best of luck in learning this. Edit: here's an example of someone doing something similar in the right way: http://kyrobeshay.com. |
|
|
To CodeAcademy's credit, they're doing a great job welcoming and acknowledging feedback without making any specific promises.
The web is full to bursting with design critiques, but the ones that build a name for their authors always seem to have an air of "how the fuck did you screw this up!?" While these critiques are annoyingly divorced from workplace politics and not necessarily a great way to deal with clients, coworkers, or bosses, us huddled masses love a good controversy. Frankly, that's why I'm reading this thread - I love seeing someone assert their opinion with an argument stronger than "looks gross". And while this author's particular argument may be presented a bit thin, the underlying principles are sound. Every worthwhile engineer I've ever worked with appreciates concise, believable, REAL insight into why some designs work and some designs don't. Worthwhile engineers like learning things.
Keep your confidence up, MichalBures. Keep writing.