Andrea Buran’s Site ^5.0

And if you think about that even further, this “cycle of redesign” makes design less valuable. In other words, if design is only valuable when new, it isn’t very valuable in the first place.

If your app gets too complex, think about unbundling. Look at what Facebook did with Messenger. They broke out functionality around key actions and put it in their own separate app.

Thanks for your email. I’m very interested indeed. I have nothing against an interview. However, there is one condition: I have to be interviewed by the person I will be working for. By my future direct manager.

I think copywork is subject to diminishing returns—so, no, you don’t have to copy perfectly. But (and this is important) you can’t copy it worse than the original. You have to achieve something that you view as equal or better, even if the details don’t totally line up.

To be effective, I believe designers should be spending around 50–60% of their time on a single (but big and impactful) project in order to really focus on it. With too many projects, you’ll be rushing your process, and likely making incremental progress in 50 different directions.

But I also didn’t have too much time. I couldn’t afford to overthink things or get caught up in urgent but less important issues, the way I often did on normal workdays. And the people I needed to help me—engineers and product managers—were also focused on the project.

If you can’t stick with your idea long enough to do some research and run some experiments, why should anyone else?

Being able to stop someone and say “hey, what does that mean?” is a super important skill.

[…] we would create folklore and write songs and tell stories about these “ray cats,” the moral being that when you see these cats change colors, run far, far away.

“They sure do look nicer to old people like you and me, but frankly do they actually add any magical semantic value to a given text? Not really.”

However, after the Trespasser experience it has become clear that just as there are no successful anarchic world governments there can not be any successful development teams without management.

Q: Trespasser is unfortunately known for not bringing in the sales it deserved. If you could change one thing about the production what would you do differently?

A: I would have assigned the 25-year-old Seamus a strong producer, who would have bullied him to restrict the scope of innovation to something manageable.

Gall’s Fundamental Theorem of Systems is that new systems mean new problems. I think the same can safely be said of code—more code, more problems. Do it without a new system if you can.

I want you to know that no matter how invested, how entrenched, how indispensible you might feel within the tech industry, it chews people up and spits them out every day.

I prefer the fixed-gutter approach instead. One of the things I learned from typography was the importance of ensuring whitespace remain consistent. This leads me to believe that gutters, which are whitespaces that separate columns of content, should be kept the same.

You can’t get comfortable if you want to work with JavaScript but you don’t have to know everything.

[…] be careful with humor because it may not always be appropriate to use in your error message; it really depends on the severity of the error.

[…] and I have never really understood that. You know, to me that’s not what success is about. To me the success is about making great watches, really great watches.

Web animation can be so much more than just decoration, but only if we make it part of our design process. It can’t be a meaningful addition to the user experience if you don’t include it in the early conversations that define that experience.

For existing projects that already use animation, you can start with a motion audit to find all the instances and ways you’re currently using animation.

If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve.

[…] certain pieces too easily fall into favor and repeated use. They quickly become fix tropes of a specific mood or environment, so much so that eventually there is no room for mobility and experimentation.

[…] You’ll be asked to design things counter to goals. You’ll be asked to design according to whims. All those things will fail. And those failures will be on you. As a designer it’s on you to do the job to the best of your ability. Learn how to protect yourself by saying no.

[…] You are really good at what you do, and if you stay in the weeds on everything, you’ll keep things going perfectly, for a while. But eventually two things will happen. One, you will burn out. And two, you will eventually start to seriously piss off your team.

Why do products sometimes label things as my stuff, and sometimes label things as your stuff?

Refactoring is a second chance that most industries don’t get.