HNHacker News
TopNewBestAskShowJobs

eflowers

712 karma · joined November 7, 2012

submissionscomments
eflowers··on WrapBootstrap is offering bounties
I can't do the math on how $200 for a theme could appeal to anyone who has the ability to do it, unless they make one theme and push up 20 slightly different CSS versions of it. $200 is approaching maybe 90 minutes of contract work, and 4 hours of day-job work.
eflowers··on The Dribbblisation of Design
I can't tell if you're saying that visual/graphic designers are saying they are doing "UX", or if "UX" people are really just hand-waving visual designers?

I got lost around "wank word" and UX being the "Web 2.0 of the design world." Most UX people I know are focused on user research, usability, information architecture, and interaction design. I'd say maybe, 1 in 5 are visual designers, and maybe 1 in 3 have any passable graphic design skill at all.

Maybe you're saying that people will be just called "user researcher", "information architect", etc etc and not use the word UX. But I think "wank word" is a tad inaccurate.

eflowers··on Bootstrap 3 Grid Introduction
I would like to hear it. Post in my comments thread on the page and tell me what you think and find out, I could add a revision and expand on the mixin and semantic naming part to help address some of the pros/cons.

(im the author if that wasn't clear)

eflowers··on Bootstrap 3 Grid Introduction
Can you elaborate on how the "full mixin" approach in Bootstrap 3 isn't as sufficient? From what I can tell, you can leave markup completely out of your HTML, and even go so far as to use pseudo classes to designate where you want the grid created. Honest question.

Unless you just want a grid and no other part of the Bootstrap styles. I think if you only include the Bootstrap grid in your compiled CSS, it's pretty lightweight. Not as much as this, but you don't need to include everything else.

eflowers··on Bootstrap 3 RC2
I've been using the WIP for a few months and the changes in RC2 are looking really great. I am curious as to what the ramifications will be on the learning curve of people really making the most of the new grid system and how it can be way more dynamic by calling different columns at different snap points. I didn't really "get it" right away, but after figuring it out I can see how it's a huge step forward.
eflowers··on UX is not UI
Outside of places like HN, most people don't. I am trying to think of a hacker analogy, but can't.
eflowers··on UX is not UI
I have definitely been a UX PM, even having a former VP of Engineering saying that the 3 "UX people" in the company were the only people providing the "tactical PM role" since PM's were stuck writing PRD's (waterfall product requirement documents). Maybe that's part of my skew as well is that I've always been a primary (diluted, overextended) stakeholder in design, PM, research, and development.
eflowers··on UX is not UI
I would say 95% of initial impression I've had is that I'm a "look and feel" person. Even after long, very specific conversations, it still comes out as "look and feel." And honestly, that's what most people care about since they can see it. As long as that doesn't impeded the work that goes behind it, I don't think that will change. You just need your boss, and bosses boss, and maybe an executive to understand what you're doing so you don't just look like a wasted headcount that should be doing JUST look and feel, but isn't.
eflowers··on UX is not UI
That's a good way of putting it. I would add that someone, a UX role perhaps, also has to have researched/figured out the answers to "A cake for who?" "What is the occasion?" "How big does this cake have to scale?" "Do we know if this certain bride has any certain preferences" "Wait how did we determine this is a wedding cake?" "My bad, it's a birthday party. But this was a pretty dope wedding cake we built don't you think? Tastes great!" "But it was for a 6 year old boy's birthday" "Look we don't have time to muck about with look and feel. It's a cake. It's a birthday, just fucking ship it." =D
eflowers··on UX is not UI
I agree. That's one of those places where being in a UX role is way outside of UI design, and I'm taking the apps on-site with customers (I am mostly b2b) and observing and testing them as they use it. Recording their responses, as well as the applications. When logging in to the system takes 40 seconds because of database performance (or lack of), that's a UX insight that needs to be observed and reported. That's not something I can control but it has a huge impact on the user's experience.

There's an element of user-advocacy that I'm doing where I take the experience they are having and translate it back into business, design, and development goals as when someone is trying to use an enterprise piece of software and the experience is terrible, that is going to fall on designers, developers, PM's, and all the other people involved in the creation of the "thing" which becomes the user's experience.

That's another ambiguous situation. I go spend 2 days with users out at a company HQ, and I come back with tons of data that now has to be consumed by devs, designers, pm, marketers, executives, QA, customer service etc etc. The experience of what we build is a collection of every role in the entire company as far as the user is concerned, and all those various business roles need that UX information brought back. So at this point I'm so far from UI and visual design I'm closer to a PM or product owner now, but soon will be jumping back into the design an development realm to start to fix those experience problems.. unless the problems result in bad business drivers or invalid use-cases, so then I'm back at the PM and management table,

I still can't find a clear distinction about what I'm supposed to say I do. I just know that there is a certain disservice to just tell people "UI design, look and feel."

eflowers··on UX is not UI
Being an internal consultant is often what happens. It's a horizontal role that might look like it's owning a bunch of things, but really it's support various needs in various domains that have a touch on the user/customer "experience."

So yeah, I'll be in a PM meeting and then leading the PM meeting. Then I'll go out and into a meeting where we're analyzing analytics on the website, then to a meeting with devs on how we're implementing the interface literally, and getting me set up so I can run builds, edit the html/css, write all the front end views while devs create the models.

And then the CEO pulls me aside and wants to know what 'I'm doing to help turn this company culture into one that is user-centered and customer driven."

So it is like being a consultant on this huge spectrum of "customer/user experience" touch-points, and it's way more than just 1 or 2 people can do. And then all of this is rolled up into the perception that you're there for "look and feel" which probably only takes up 15-20% of your actual job.

You've made a really good summary of how I feel often.

eflowers··on UX is not UI
You get it more than most. This is right on target.

It goes from 50/50 one day, to 90/10, to 10/90. And yes, often as I have lived and witnessed, UX is set up to fail through that structure, especially when they don't actually "own" anything.

eflowers··on UX is not UI
I think UX often is a thin, horizontal role across many others. My personal experience has been that yes, there are significant aspects of PM, UI, marketing, development, data analysis, etc that are thrown my way and I am supposed to "help shepherd" them. It's not that I demand those jobs, but they just become part of the horizontal UX ambiguity. In the last 3 places I've worked, part of that horizontal role has been just what you describe. There are other people there too, but as the "UX person", I was expected to be involved in all of that. And sometimes, even expected to own it.

"Company Culture evangelism" is a funny one because yes, at 2 companies part of the "UX" job, by request of C-level execs, was to work daily on spreading and educating on a "user centered culture" throughout the company :D

eflowers··on UX is not UI
Hello, I wrote this article. I can check one thing off my bucket list - an article of mine on the front page of HN (spot 28 as I write this).

Reading the stuff here in HN, I agree with almost everything said. My intent wasn't to take a hard line tone, and in retrospect after getting tons and tons of feedback, I'd write it differently, but I'll take this chance to clarify some things, both for myself and for others.

It is not written in a snarky or superior voice. It wasn't a rant. If it sounded so, I apologize. It also comes off as a list of "this is what a UX job title should be", which also wasn't my intent. The simplest way to say what I was trying to convey is that if you label yourself as anything "UX whatever", it is perceived as "graphic artist for interfaces."

The article often seems to convey that UX "owns" all these different things, like it's a panacea role above all others. It's not.

It's not something that I can clearly define. On the little 2-column lists, the things on the left were supposed to be things that I/we "do" in the sense of what often becomes the reality of the job, not in the sense of responsibilities that should be granted to use to be accountable for. And if that large list does become the reality of the job, it's more than anyone can or should do. It was intended to be a "these are some of the things a UX person might be responsible for." And yes there are some silly ones on there.

I don't think UX is in a position of being a land-grab of everything that isn't writing code because "it's what we do", but it's more of a "this is what we are often doing" list. And some of the things on it should be owned by other discrete jobs careers. The motivation to write the article came from being in role after role where that list on the left was the list of things I was inadvertently responsible for, but "graphic designer for interfaces" is all that is seen by others, which isn't fair to UX people who don't focus on interface design, and isn't fair to interface designers who don't focus on the UX work that isn't based on UI or visuals or interaction.

It's sort of just a response to the introductory conversation I have the first few weeks at any job. "What is your role here?" "Well I'm the new UX guy." "Great! Our stuff is ugly, you're gonna give it that sexy look and feel?" "Yes, but I am going to be doing other things that sort of result in that look and feel you want" And then when I list off some of those things, typically the other person looks at me like I'm a lunatic and we both end up confused on what I'm actually supposed to be doing, and the disappointment that I'm not just there for look and feel.

But for sure, the article is not meant to be a land-grab or king of the hill situation of "UX OWNS EVERYTHING", but just a glimpse into the terrible ambiguity of what UX is and how the very common initial perception of "graphic designer for interfaces" makes it even more unclear.

eflowers··on Ask HN: What's Your MacBook* Desk Setup
11" Macbook Air and 2 27" Thunderbolt Displays.

Staples folding banquet table, 72".

Full size apple keyboard.

Microsoft Intellipoint Optical Mouse, 1.1 (USB/PS2)

eflowers··on 3px of padding makes all the difference in the world
I am glad you pointed this out, your premise is a quintessential example of "UX is not UI."

It's not the visual or web designers primary job to A/B test or step into the users shoes on every detail, that's what a responsible and valuable UX person should be doing (note I didn't say UX designer).

eflowers··on Why Startups Should Create Customer Personas
I can see what you're saying, and I don't want to belabor it to death. But as the UX guy, a persona is what nails down the problem before ever coming to a solution.

Maybe we're talking about different types of personas. The question I'd ask from the very beginning is "who are we building this for and what problem is it going to solve?" And adding a little definition to the "who" and what problem they have is the first step in building anything, and making sure you don't waste time.

In the end, from day 1, from the first utterance of what your startup is about, you're building something for a human. Without empathy, you can't build the right product. And you can't empathize without personas. It's not even really a question of user experience, or user interface, it's just about nailing down the human problem.

eflowers··on Why Startups Should Create Customer Personas
Creating personas on what people say is bad UX, and not a flaw in personas. Knowing what a user behavior based interview/persona is the job of whoever is in charge of the startups UX process.

I don't see how you can "know your market" without some sort of idea on who your user is, what their behaviors are, and have some sort of empathy with them.

Regarding pivoting and "throwing out" the work... each discipline of a team would do that. That's your UX designers job, just like a programmer would have to throw away code or a graphic artist would throw away design collateral for the new direction.

The "realize nobody cares" is exactly what good UX personas prevent. I guess if a startup doesn't know how to incorporate or conduct good UX you could run into those problems.

I guess I just don't agree with your premise. You're basically describing what happens when something goes wrong with your UX and personas - so of course your argument makes sense since you're highlighting a worst case scenario. But you're neglecting to acknowledge that every day, many startups effectively use and get tremendous value from personas and UX, and you can't do real UX without personas.

eflowers··on Why Startups Should Create Customer Personas
I have a hard time believing that Microsoft is the best example of persona usage.
eflowers··on Why Startups Should Create Customer Personas
Just like any development or UX tool, personas can be dangerous or super effective. It has nothing to do with the concept of personas, it's just how people choose to research and use them. The intent isn't to design for a specific customer, it's to give the UX and development teams a common user reference point to validate their assumptions against through user interviews and continued research, iterating on the personas.

I'm sure you know about Alan Cooper's books, but another that I've found helps maximize the benefit, and minimize the danger, of personas is Tamara Adlin's "The Persona Lifecycle" : http://www.amazon.com/Persona-Lifecycle-Throughout-Interacti...

Plus, Microsoft isn't exactly known for it's effective UX.

eflowers··on Bootstrap 3 preview
This is the key to Bootstrap (or similar css frameworks). It's not intended to be a theme. If you want to just have the css/html ready for you to do some documentation or a project that has no need for any visual differentiation, then go ahead and use vanilla.

When used to build something that should be visibly unique, the visual design and appeal is something that should be created aside from bootstrap, maybe with the grid in mind, and delivered as mockups or pattern guides.

eflowers··on Ask HN: What are the cons of the Seattle area?
I've never heard of the Seattle Freeze, but upon reading about it, it can't be any worse than the Salt Lake City freeze if you're not downtown. Interesting, I wonder if moving from Salt Lake to Seattle would make the "freeze" feel like nothing.
eflowers··on Wizard Modals for Bootstrap
I really like this. I had done something similar in a project, but this execution really ignites my imagination. Really well done. I am curious if chosen.js would have to be modified to handle backbone style async, I know it's been strange in cases like that.
eflowers··on Practice typing for Code
I just learned that I am such a sloppy coder since I hit semicolon with my index finger apparanlty, and my right hand only uses my thumb, index, and middle finger.

No wonder I can never hit the semicolon or parens/braces/brackets. I use my index finger...

eflowers··on Show HN: Vinepeek - watch the world in realtime in 6 second snippets
Having to constantly remind yourself that, more or less, "this is happening right now" is a surreal experience. It feels like the cheesy curated montage at the beginning of a smarmy independent film - but it's not. It's just random, unfiltered views into things people are filming all over the world.

I had no idea how many of us could connect over our love of filming coffee preparation, or cats, or traffic, or terrible attempts at stop motion. Hey look another magic trick!

Seriously though. Fascinating and, for now, quite engaging. I vote against re-wind or links to previous clips though. Keep it ephemeral and impermanent. Like real life - a moment is here, then it is gone.

eflowers··on Ask HN: How do you stop regretting?
This may seem cheesy, but damn. It's 4 minutes long, watch it. You think you are more convinced that things can't get any better than this guy was?

http://www.youtube.com/watch?feature=player_embedded&v=q...

eflowers··on Show HN: Greater Peace of Mind Guaranteed, or Your Money Isn't Refunded
I am going to give it a try, and my evaluator is an orthodox buddhist practitioner. Without criteria for what constitutes a success, do you realistically thing people will qualify for the "Refund" level of completion?

I guess, what is the plan for people who do complete the 30 days and try their best, get a positive evaluation from a peer, but then don't meet your criteria? "Sorry you did your best, but I'm keeping your 20 bucks."

I already paid, so you'll be hearing back :)

eflowers··on The Ouija Toggle
The "spiritual communication and summoning device" toggle!
eflowers··on A new UI annoyance
Quija sliders are perfect for this ;) http://shaunxcode.github.com/ouija/
eflowers··on Sucking at Retina
I have a little retina less mixin I use (when using bootstrap mostly) that I modified from the retina.js solution. It's the same solution with additional parameters. I've found it to be useful when doing retina projects.

I put it up on github here: https://github.com/erikflowers/retina-mixin

← PreviousPage 3 of 4Next →