TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

One of the biggest mistakes I’ve made in my career

95 点作者 mtviewdave超过 9 年前

9 条评论

panic超过 9 年前
This title is a bit clickbaity. To save you a click: the author's mistake was, as a designer, to stop writing interactive prototypes and to go back to making static screenshots instead.
评论 #10244640 未加载
评论 #10244464 未加载
评论 #10244441 未加载
_s超过 9 年前
Two or three of the best designers that I would never hesitate to recommend all know how to code. They know exactly what&#x27;s possible in which browser, and they organise their assets, mockups, designs, documentation so beautifully that as a developer I actually look forward to bringing their designs to life.<p>More often than not I&#x27;ll shy away from doing front-end precisely because a lack of understanding from a designers part on what&#x27;s possible or what needs to be hacked together using ludicrous amounts of JS&#x2F;CSS workarounds; especially since these very designs or ideas is what the client or PM okays &#x2F; is expecting.<p>Just my $0.02 - as a dev I&#x27;d love you quite a lot of you knew what I do and help me by taking the limitations into account :)
评论 #10243992 未加载
coldcode超过 9 年前
So, should programmers learn how to design? Oddly enough in the 80&#x27;s programmers were the designers for the most part. The idea of a standalone designer was more of a web idea from the mid-90&#x27;s. Before then we all considered design as a part of programming. The one app I built from 1988-1993 that is still sold (many owners later) has many features remaining identical to what I designed despite being the lead programmer. Today people laugh at the idea.<p>I think the more everyone on the team understands all the specialties the better the app is likely to be.
评论 #10245148 未加载
评论 #10244846 未加载
huuu超过 9 年前
Since CSS2&#x2F;3 I never touched design programs again to design websites and web apps. It&#x27;s so easy to trow a basic interface together and then use CSS to give it nice looks. So this became my way of work:<p><pre><code> * Build a simple HTML template as interaction design * Add some basic design (style, color, fonts) * With the customer fine tune the design * Add code to the templates to make it all work (or hand it over to development) </code></pre> Ofcourse you still need design experience. You are just using other tools.
评论 #10245163 未加载
saintfiends超过 9 年前
I completely agree with this one. Designers and UI&#x2F;UX developers are not mutually exclusive. It works better when it&#x27;s the same team&#x2F;person.<p>It works really well when designers know what they are catering to. In case of browsers, it saves a lot of time when they know browser differences, or when they know JavaScript &#x2F; CSS capabilities.
protomyth超过 9 年前
What a less than visionary manager. I would love UI folks to make a prototype of how they envision the UI to work. It helps a lot and allow for some quick feedback from both the biz and the programmer who has to do the programming. Its in the same ballpark as writing the user manual first then starting to program the project (Pages by Pages, I do believe).<p>I knew a couple of consultants who did enterprise process work and also knew Shockwave. They would program a demo of each process. A little figure moving paper from place to place gets the point across better than any PowerPoint presentation ever will.
qzxvwt超过 9 年前
I have a feeling my biggest mistake will have been not adding &quot;blog-writer&quot; to my list.
segmondy超过 9 年前
My worst mistake as a developer is the inverse, not learning how to design.
mgkimsal超过 9 年前
If &#x27;designs&#x27; are intended to be reused across multiple areas - print, tv, web, whatever... - I cut designers a bit of slack in terms of deliverables. When the designers are primarily&#x2F;exclusively working in the &#x27;web&#x27; or &#x27;mobile&#x27; portion of their industry, and yet, after several years, do not know how to even start to test ideas out in a browser, it&#x27;s a sign that that they don&#x27;t care about their work or career as much as I though they did (or as much as they probably think they do).<p>Even 15 years ago, the best design folks I worked with could do basic HTML stuff, to at least test out their core ideas. We&#x27;d review them, and I&#x27;d point out some problems we&#x27;d have cross-browser, or limitations of JS interaction at that time, and we&#x27;d iterate some ideas. They understood enough of the web portion (and these folks came from print) that when I explained (or could demonstrate) the problems in code, which they&#x27;d already written some of, they knew <i>why</i> the problems were there. They could <i>know</i> something was actually <i>not possible</i> to recreate in pixel-perfect fashion across IE3,4,5, NS2,3,4, WebTV and Opera, because they had experienced a site was more than displaying a single JPG file on a website with a massive HTML map area (did a couple of those WAY early on - insane).<p>Don&#x27;t send me a photoshop file with 280 layers, one for each rounded corner on the 17 round corner boxes with too-small text which only looks good on your 30 inch triple monitors please. It&#x27;s not going to translate and give the same &#x27;feel&#x27; on multiple screens. (how come it&#x27;s OK for you to not have to know html&#x2F;css, but I have to have a photoshop license to work with you? and your agency complains about how expensive I am to boot?).<p>I don&#x27;t expect you to be an expert in coding&#x2F;layout, but I do expect you to know the basics. Similarly, I&#x27;m fine with knowing how to open PS files, resize images, export to different formats when you don&#x27;t deliver what I ask for, etc. I can&#x27;t do all of your job, you can&#x27;t do all of mine, but let&#x27;s have some familiarity with each others&#x27; worlds, OK?<p>About 20-30% of the design folks I&#x27;ve dealt with have truly &#x27;got it&#x27;, when it comes to designing for the medium, and understanding the tools. Most of them also did it in print, and would have an understanding of copywriting basics, font impacts, etc, as well as paper issues (printing on different paper types could impact colors, glossy vs matte, whatever). They understood the print medium, because they understood the basics of paper, then got in to web and understood the basics of web (HTML&#x2F;CSS&#x2F;etc). For better or worse, the other 70+% of folks just don&#x27;t get it, or seem to care.<p>The older I get, the easier it is to choose to not work with those folks, but for the first several years of web work, I couldn&#x27;t put my finger on why it was so much more productive working with person A vs person B.