matejlatin

Most of the laid-off designers were either senior or lead designers, had been with the company for 2 years or more, and were high performers. One-fifth of them think that getting laid off was retaliation against them and 72% don’t believe that “overhiring” was the real reason for the layoffs.

More than 200 designers voted in a blind test — the result is not what you’d expect.

It's time to make typography on the web more exciting. Huge type is a way to do that, but when and how can it be used?

Why did you quit your last job? This was the main question in my recent study I did with designers. I received 156 responses to my survey, most of them were from Product/UX designers, second and third in number of responses were graphic designers, and web designers.

I'm so excited, the book is finally all I wanted it to be from the start. I also launched an updated website with it, so I'd love to hear your thoughts about it and about the book if you decide to buy it. Cheers!

Thanks for sharing this, will make sure to use PNG8 in the future!

That's so cool, I didn't know that. Thanks for sharing!

Thanks, a lot of effort is needed to get things to look nice on different devices these days. It's a challenge.

>And I would prefer “practically useful” over “typographically correct” every time :-).

That is a good guideline.

Yup, that's a great point. This article is based on a chapter from my book but this is chapter 6 out of 13 already. In earlier chapters, I discuss how we need to know the content, the goals of the text and what are the user's goals (read, skim, search etc.). Of course, we can't be 100% sure on their goals but we can take an educated guess based on the content we're designing with. Decisions like these should be based on that (+ personal preference of course).

That's ok. I actually wanted to include such note about the units in the first place but forgot (in the book I use REMs and pixels only as fallback but changed to pixels in the article for simplicity). Your comment reminded me to add this note in. And I know how frustrating it can be when working on typographic details on the web. Are you having any specific problems?

That's ok, it's a matter of preference and how emphasized the bullet lists need to be. I even mention this somewhere in the article.

This sounds like a comment based on your personal opinion. That's ok, we all have our preferences when it comes to fonts.

You're right about the pixels. I used them because the examples set in pixels are the easiest to understand. I added a note that outside of these examples, the units used should be EM or REM. Thanks for the feedback!

That's really cool, but when I want to print it, it doesn't keep the business model canvas layout :/

That's a great resource, thanks for mentioning it. I might add it to the page :)

Thanks. Go ahead, you can share it with anyone you want :)

No problem, I'm glad you found value in it.

Thanks, I'm glad you think it's well designed :)

Hey, Matej here, I'm part of the UX team at GitLab. I understand that it can look like we don't spend much time polishing the user interfaces and experiences that much but I can assure that we do. We don't have a split in % on how much time we should spend polishing existing things but maybe it's something we should consider doing.

Just to give an example of a recent redesign of an existing feature that I was involved in, it can be found here: https://gitlab.com/gitlab-org/gitlab-ee/issues/6089

Our application covers the whole DevOps lifecycle which means it takes a lot of effort to upkeep existing and constantly ship new features, but we always strive to do our best.

Thanks for the feedback, I think it will trigger internal discussions on how much time we should spend polishing existing features and experiences.

This is really useful feedback @Karunamon! I see Sarrah already addressed it so I just wanted to add my bit: I also think that the approach we used for designing settings pages isn't optimal and suggested improvements in a discussion on a related issue:

https://gitlab.com/gitlab-org/gitlab-ce/issues/45219

After seeing your feedback (and confirming my assumption) I decided to open a new issue to specifically address this and would love to get your feedback on the proposed solution:

https://gitlab.com/gitlab-org/gitlab-ce/issues/47405

Thanks again for taking the time to write such detailed feedback down. It's really helpful to us. Cheers!