Live data from Hacker News

Don't look for a UX guy, be a UX guy

blog.factlink.com

21–30 of 44 posts

Re: Don't look for a UX guy, be a UX guy

#21
"to step back and think about what’s most important, try to come up with the most simple and shortest path to get there, build, analyze what works and why(not), measure, test, rinse, and repeat"

This is more than just UX - you're talking about product design, usability testing, reviewing quantitative data, then reworking features & design (UX/UI + dev) - the whole thing.

Sounds like you're saying that the UX principle of, "being really persistent in iterating and discovering what works" is essential to product - yea, agreed - that's called working towards product market fit. That kind of analysis and iteration is definitely good but not a novel idea.

Also, a suggested revision to title: "Don't look for a UX person, be a UX person." There are women on here too, thanks.

Re: Don't look for a UX guy, be a UX guy

#22
post #16

> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…

It's hard to meet people like this because of attitudes like this. I have three designers on my team who are also world-class engineers, yet they often don't advertise themselves as such because they run into the "well if they do both they can't be good at either" attitude.

No-one bats an eye when an engineer also turns out to be a fantastic musician, or when an engineer drives great product decisions, yet somehow being able to code and understand design is an impossibility?

We're here to build great things - code and design are mutually-beneficial skills in your toolbox; your brain is not zero-sum.

Re: Don't look for a UX guy, be a UX guy

#23

Earlier quoted context omitted.

Seeing Google try different shades of blue automatically, just goes to show that they don't know what they are doing Why does that show that "they don't know what they are doing"?

Forgetting for a moment all the theory of color and contrast /equilibrium in a design: 1 - different people see different shades (difference in monitors) 2 - Unless there is a glaring problem with the shade of color chosen (like something most designers wouldn't approve), changing shades is one of the least important areas of improvement possible 3 - The current redesigns of GMail / G+ / GReader (among others) are ve…

Wouldn't #1 be an argument for testing to pick the best color (or at least a big part of any decision) - it doesn't matter what the designer picks, it matters what people see!

Re: Don't look for a UX guy, be a UX guy

#24
Ummm... No, no thanks. We're not all UI designers. We just hired a UX guys because I, as a systems engineer, am more valuable creating hardware interfaces than user interfaces. You still need guys like me making things work behind the scenes and that's where my time is best spent.

Re: Don't look for a UX guy, be a UX guy

#25
I think there's another factor. Even if you have talent for both programming and UX, it's hard for the same person to do both those things well on the same project. To program well you have to know the implementation inside-out. But to do UX well you need to see the places where implementation complexity is leaking through and confusing users. For that, it's helpful not to know too much about how the sausage is made (not sausage in general, but this particular sausage). Once you are habituated to the internals, many details will feel natural and obvious to you that are anything but natural and obvious to users.

The best thing, of course, is to have the program's internal model and the user's mental model be the same. Eliminate contradictions rather than hiding them with complex mappings. ("Design is how it works".) But even then, there will always be much complexity that the user should not have to know about.

Re: Don't look for a UX guy, be a UX guy

#26
So, let me quote a bit of this submission, add some facts, and then take this to its logical conclusion.

>The current meme going around Silicon Valley and startup land is that any founder needs to be a technical founder and be able to program. Don’t look for a technical co-founder, be a technical co-founder. Even more, every employee at an internet startup needs to be able to program...For those who are all-in on these ideas, I would like to raise the bar and say: don’t look for a UX co-founder, be a UX co-founder. Don’t look for a UX guy, be a UX guy.

So much for the quote, and the amount the author wants to raise the bar by. Fair enough.

But why not raise the bar to the top?

Instagram had 13 employees when it sold for a cool billion. (Thanks, Gabriel Weinberg. http://www.gabrielweinberg.om/blog/2012/04/how-many-employee...)

So, why not raise the bar to the top: single founder, no employees.

Let's say there is no aspect of founding your business that you can't get down to 30 hours per week by that role. If you are ready to commit up to 120 hours in an exceptional week (7 hours of sleep every day, but otherwise get up and work), in what way should you not be ready to fill up to four cofounders' roles?

Raise the bar? Why not do it all?

Here is one recipe.

Role 1: (30 hours) Tuesday, Thursday, Friday, 8-6. This is business development, including networking, scoping out employees, liaising, negotiating terms, finding a scalable business model, doing market and product research, finding competitors and seeing what features they have, talking to users. While the company is very small, you also do customer service. You don't necessarily have to have business experience, but you should have been involved in a small company that expanded greatly or closed a round while you were on board.

Role 2: (30 hours) This is pure uninterrupted coding, Monday, Saturday, and Sunday, 8-6. You should be a full-stack developer well-versed in databases, cloud services (e.g. amazon), front-end and back-end languages, version control, etc. Role out the features that you yourself scope out above and below (role 1 and role 3), or from actual mockups in photoshop that you design Wednesdays or occasionally (see role 3) tweaked betwen 7-11PM the night before. Liaise with talent that business development (you on Tuesdays, Thursays, and Fridays) throws your way. Work from mockups you yourself create (Wednesdays and some late evenings). Of course, you have 10 years worth of coding experience and are an expert in Git, Python, PHP, Javascript, databases, etc, and hopefully a couple of fully coded Android and iOS apps that you have done by yourself.

Role 3: UX and UI. Wednesday, all-day. (Meaning 7-7, though this is creative work and does not have constrained output, can include showing work to others, etc). This includes a break, thinking deeply about what you're really doing, looking at other web sites, and then laying out in photoshop the UX and UI that you will be coding up during the rest of the week. You are, of course, an expert in photoshop and all aspects of UX and UI design and should have a professional-quality portfolio that extends from logos currently being seen by hundreds of millions of people to animations and Cannes-festival shorts, though this can be a relatively short stint in your career due to the low amount of money that you were making. However, you should be confident in your portfolio, and be very quick and competent in Photoshop so that you can execute your vision as a visual 'spec' to code from later. Besides the 12-15 hours (loose, it does involve creative work) that Wednesday comprises, every day between 7 PM and 11 PM you should be prepared to add to this creative output, which adds another up to 18 hours. Your entertainment in these evenings should also be creative and related to your output. Whether that means watching documentories on art, or reading such books, the point is that this is 'fun' for you and your lifestyle in the evenings is somehow related to UI/UX and the types of questions that come with it.

Role 4: This is the most flexible role: it consists of counting money. The accounting role should be able to performed quickly from 11 PM to midnight every day when you don't have much money coming in (7 hours in a week), and extend up to 2:30 AM or 3-3:15 AM every day - another 17.5 to 23 hours - when you do. This extends into the hardest and most awake and alert "all-nighter" period that a coder may think is best reserved for coding. Not so. To truly grow on sales, you should devote your greatest attention with the most quiet and fewest distractions to the bedrock of your business, which is counting money. You should be very at ease with numbers, have a deep understanding of accounting, to the point of nearly having a degree in the matter, and should definitely have handled all aspects of a business's books in the past (short of being an in-house accountant). This is where having run your own business, any business, by yourself, including being a freelancer who had to invoice themselves, will truly help you. However, when there aren't many accounts and there isn't much money coming in nor accounts payable, nor a current round underway or end of the month or quarter there may not be much to do here. Get some rest.

Role 5: (And you thought I could only fit 4 roles in here!) In the morning before 7 or 8, other than Wednesdays, when you're focusing on design from first thing in the mroning, you can answer various quick emails, including non-actionable customer emails, review any news or feeds - like hackernews, have breakfast and generally start your day. Ideally, on normal days you sleep from midnight to seven, and do various quick things like this from 7 to 8, when you start your role of the day. You should be sociable and love getting a bit of time every morning to do this stuff! It hardly feels like a role, just something to break up the chore of boring stuff that you do all day every day.

Why not. Anyone who meets the criteria of the roles above should be able to get a business off the ground as a sole founder and get a very far way along as a sole employee.

As the business expands, you can get help with the accounting (to get more sleep), then help with the programming - especially after all the initial architecutre is set up and major features have been planned and begun to be roled out - a very professional designer just as you yourself are, and finally you will be left to meet with VC's all day to sell the company that you built up all by yourself.

It is, after all, the logical conclusion to the present submission :) Note: I have only proved the above possible, not tried it myself...

Re: Don't look for a UX guy, be a UX guy

#27
post #20
post #16

> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…

I think you are going a bit over the top with regards to the complexity of what it is we do. There are plenty of other careers ( http://en.wikipedia.org/wiki/Fallingwater ) that require both creative and technical thought. Does our position really require years to master? Is a java or ruby programmer with 10 years experience that much better than a java or ruby programmer with 3 years experience? What about design? I…

You're right, but let's not trivialize the difficulty of programming in general. Want to build a UI in .NET, HTML + JavaScript, or ? Sure, that sort of programming is relatively easy and not usually technically challenging. However, that is hardly all that we do.

I don't touch UI's in my day job. You make it sound as if all programmers code UI's and perform other relatively mundane tasks. That may be what you're used to, and yes, it is relatively easy work, but there are a bunch of people like me out there who design infrastructure at a low level so that you can more easily build software at a high level.

Re: Don't look for a UX guy, be a UX guy

#28
post #20

Earlier quoted context omitted.

I think you are going a bit over the top with regards to the complexity of what it is we do. There are plenty of other careers ( http://en.wikipedia.org/wiki/Fallingwater ) that require both creative and technical thought. Does our position really require years to master? Is a java or ruby programmer with 10 years experience that much better than a java or ruby programmer with 3 years experience? What about design? I…

You're right, but let's not trivialize the difficulty of programming in general. Want to build a UI in .NET, HTML + JavaScript, or ? Sure, that sort of programming is relatively easy and not usually technically challenging. However, that is hardly all that we do. I don't touch UI's in my day job. You make it sound as if all programmers code UI's and perform other relatively mundane tasks. That may be what you're used…

>let's not trivialize the difficulty of programming in general

No, let's trivialize it. What exactly do you do on a daily basis? Give me an example of a task that you worked on that took a lifetime to master. Something that you could only truly appreciate after years of focused experience.

Re: Don't look for a UX guy, be a UX guy

#29
post #22
post #16

> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…

It's hard to meet people like this because of attitudes like this. I have three designers on my team who are also world-class engineers, yet they often don't advertise themselves as such because they run into the "well if they do both they can't be good at either" attitude. No-one bats an eye when an engineer also turns out to be a fantastic musician, or when an engineer drives great product decisions, yet somehow be…

I would agree with you if these were complimentary skills we're talking about. However, programming and UX design are almost contradictory.

For programming, you need a mathematical inclination, attention to detail, willingness to sit down and focus on one concrete task at a time, etc. For UX (and any kind of other) design, you need more an ability to create art - paint with broad strokes, look at the big picture, etc.

This is my opinion, YMMV, feel free to disagree, etc

Re: Don't look for a UX guy, be a UX guy

#30
post #28

Earlier quoted context omitted.

You're right, but let's not trivialize the difficulty of programming in general. Want to build a UI in .NET, HTML + JavaScript, or ? Sure, that sort of programming is relatively easy and not usually technically challenging. However, that is hardly all that we do. I don't touch UI's in my day job. You make it sound as if all programmers code UI's and perform other relatively mundane tasks. That may be what you're used…

>let's not trivialize the difficulty of programming in general No, let's trivialize it. What exactly do you do on a daily basis? Give me an example of a task that you worked on that took a lifetime to master. Something that you could only truly appreciate after years of focused experience.

I have no example of a skill that took "a lifetime to master" as I am only 28 years old and would not call myself a "master" of anything at this point. However, I can describe the last two projects I worked on.

One was implenting an image quality algorithm for a medical imaging system. I did not do this on my own, but I will wager that it was far more complex and involved than any UI code you last wrote. I had to understand the science behind the algorithm, implement it, and then make it fast (it is run on huge images).

My next project was optimizing a heap memory manager for the device which captures these images. Not PhD level physics here, but not trivial and not something I would expect a UX guy to do.

So yeah, I take a bit of offense when you lump all programmers into the same bucket. Not all programming is engineering IMO, and to compare writing a UI to writing a thread scheduler, a memory manager, a new programming language, etc. is just ridiculous.

I'm not saying that UI work is dumb simple. It is incredibly hard to get right, but that kind of complexity is not technical. It takes a certain kind of aptitude and knowledge to do work that is closer to the metal and closer to concepts taught in CS. Creating a UI is not CS, it is wiring up bits of code that other people wrote in a such a way to be useful to a non-programmer.

So yes, a UX guy could probably be writing his or her own UI's in about 6 months to a year. I would not hire this person into the group I work on because they will be overwhelmed by technical complexity that they simply won't be able to handle.

Post reply on HN