Live data from Hacker News

Design Secrets For Engineers

eng.pulse.me

21–30 of 39 posts

Re: Design Secrets For Engineers

#21
post #13

I like it, and most of the advice is pretty good. However, I have one concern- for the past few years, it seems all engineers and designers have been feeding off of each other's ideas, and this has resulted in websites that look nearly identical in color schemes, typeface, and wording. This makes each successive product less and less distinguishable and boring. I think breaking free from design norms (as long as rule…

What are the design norms we need to break free from?

I think it largely depends on the product and audience you hope to attract. But for starters, I would like to see fewer sites with a large, bold, Helvetica font against a plain background with an intro that says something vague about what the business does. Then the large "Sign Up Now For Free" button with rounded corners that slightly illuminates when you mouse over it.

Look, I'm not shitting on other people's work. Building something original is tough, but I do think that clever design is one of the best ways a new service can set itself apart from the rest, and I think that it is an opportunity that is often missed.

Re: Design Secrets For Engineers

#22
post #7

I hate to be that guy, but this isn't "Design Secrets For Engineers", it's "Design Secrets For Software Engineers." (or developers/UIX/etc). "Keep visual hierarchy in check" and "Use designer fonts" isn't very useful advice in designing an instrumented hammer... "Engineering," especially in the colloquial usage of the word, covers a lot areas that have things in common, but there are lots of things those areas don't…

I hate to be that guy

Then don't be. It's posted on HN - the context makes it pretty obvious.

If a computer could trivially work out it was likely to be about software engineering using Bayesian reasoning ("engineer" in title AND posted on HN) then a person should be able to as well.

Re: Design Secrets For Engineers

#23
post #22
post #7

I hate to be that guy, but this isn't "Design Secrets For Engineers", it's "Design Secrets For Software Engineers." (or developers/UIX/etc). "Keep visual hierarchy in check" and "Use designer fonts" isn't very useful advice in designing an instrumented hammer... "Engineering," especially in the colloquial usage of the word, covers a lot areas that have things in common, but there are lots of things those areas don't…

I hate to be that guy Then don't be. It's posted on HN - the context makes it pretty obvious. If a computer could trivially work out it was likely to be about software engineering using Bayesian reasoning ("engineer" in title AND posted on HN) then a person should be able to as well.

>It's posted on HN - the context makes it pretty obvious.

I've read (and commented on) all kinds of front-page articles of interest to non-software hackers & engineers, including articles on the economy, construction projects, healthcare, education, transportation, and other issues:

http://news.ycombinator.com/item?id=2918950 http://news.ycombinator.com/item?id=2881546 http://news.ycombinator.com/item?id=2871117 http://news.ycombinator.com/item?id=2498109 http://news.ycombinator.com/item?id=2477475 http://news.ycombinator.com/item?id=2276033 http://news.ycombinator.com/item?id=2240603 http://news.ycombinator.com/item?id=2176868 http://news.ycombinator.com/item?id=2108564 http://news.ycombinator.com/item?id=2086873 http://news.ycombinator.com/item?id=2029281 http://news.ycombinator.com/item?id=1973985 http://news.ycombinator.com/item?id=1486745 http://news.ycombinator.com/item?id=1434017 http://news.ycombinator.com/item?id=1423352 etc.

I'm not aware that this is a forum that caters to software-only topics. Please enlighten me if I am mistaken. I'm certainly not a software guy and yet HN is one of my go-to sites because I am a hacker.

Re: Design Secrets For Engineers

#26

I never thought of using KeyNote to design a UI. I always thought designers use Photoshop or InDesign for that purpose. Is KeyNote used just for the ease of use, or is there some other requirement that the Adobe products don't measure up to?

A good friend of mine has been a lead designer at a number of big companies and he also uses Keynote to mockup UIs. For $20 it's not much of a risk to try it.

I like Fireworks much better than Photoshop for mocking up web or mobile UI too.

Re: Design Secrets For Engineers

#28
post #9

Good general advice. One remark though: while it is generally better to use designer typefaces, it's important to remember a lot of them weren't designed for the screen, but paper. As such, Garamond, for example (it's mentioned in the post), which is probably one of the best typefaces made, often doesn't work well on the web.

Beware that designer fonts are expensive! Most people don't realize that fonts bundled with Microsoft Word or Adobe Photoshop might require a license for commercial use!

Just take a typekit account. For $50 a year, you get unlimited fonts on unlimited number of websites. There is an upper limit on traffic, but if you hit that number, you won't mind paying more.

Re: Design Secrets For Engineers

#29
post #7

I hate to be that guy, but this isn't "Design Secrets For Engineers", it's "Design Secrets For Software Engineers." (or developers/UIX/etc). "Keep visual hierarchy in check" and "Use designer fonts" isn't very useful advice in designing an instrumented hammer... "Engineering," especially in the colloquial usage of the word, covers a lot areas that have things in common, but there are lots of things those areas don't…

It should really be "Visual design secrets for software engineers."

It's kinda irksome how graphic designers try to own the word "design." Design is a vital part of all engineering, software or otherwise.

Re: Design Secrets For Engineers

#30
post #22
post #7

I hate to be that guy, but this isn't "Design Secrets For Engineers", it's "Design Secrets For Software Engineers." (or developers/UIX/etc). "Keep visual hierarchy in check" and "Use designer fonts" isn't very useful advice in designing an instrumented hammer... "Engineering," especially in the colloquial usage of the word, covers a lot areas that have things in common, but there are lots of things those areas don't…

I hate to be that guy Then don't be. It's posted on HN - the context makes it pretty obvious. If a computer could trivially work out it was likely to be about software engineering using Bayesian reasoning ("engineer" in title AND posted on HN) then a person should be able to as well.

Bayesian reasoning is actually "given the Prior X, what is the likelihood that Y is true" ?

What you are referring to is the far more simplistic Boolean reasoning.

Post reply on HN