That's exciting, we've found design sprints work very well for our company.

The few tips I have:

• don't be afraid to tweak the format of the design sprint if you find that certain steps or activities don't work for you
• make sure all relevant stakeholders are involved early in the process
• bring a developer or two, not just stakeholders and designers
• have fun! :-)

I use two matte 24” Ultra HD (3840 x 2160) Dell monitors at home and couldn't be happier. I run them in @2x so it's like having two 1080p retina screens.

Just double check that whatever computer you're plugging the screen into has sufficient specs to power it. My late 2013 mbp can handle it though so I'm sure you'll be fine :-)

I work on a lot of React powered applications where we use Webpack to bundle and process assets. Webpack makes setting up so called "loaders" for different filetypes (even different filetypes in different locations) very easy.

Gulp and grunt work great for these things as well though so it really depends on the needs of the project.

I did see them, what I meant by my original comment was mainly that it'd be nice to have a sentence or two in the summary mention that compression often happens at build or that it can be added to the pipeline for web.

I also agree that lossy techniques should be completely avoided for UI assets and photos would probably work better as lossy progressive jpegs.

A lot of designers aren't in charge of the deployment pipelines of the projects they're working on, but if they're aware that compression of UI assets could be automated there I think they could pressure whoever is responsible to implement it.

I like to think that as designers we're responsible for the end result a user gets in their hands, that includes the poor impression caused by assets that load very slowly (thinking primarily web here).

Haha, yeah! Lt. Surge was sort of what I was going for when I made it, nice catch :-)

That's true, occasionally you'll run into assets that don't compress well with a lossy compression library but the space saving tips primarily do stuff like remove colour profiles and the like which is entirely safe to automate unless you're using a non sRGB image.

You could for example have different compression settings for assets that are in different places or different filetypes (progressive jpegs for example). That way you'd be able to deploy almost any image knowing it'll be handled appropriately without you having to worry about it.

This is a really cool article with a lot of research behind it! However, I think it'd be helpful to add a note regarding image compression as part of your deployment pipeline instead of worrying about how different people and teams are exporting assets.

I'd second this, I track what anime I watch already but definitely not by manually maintaining a txt file using notepad. So initially I was vexed as to what you meant by tracking with notepad.

Great, just checking ;-)

If it was intended as a joke then indeed "whoosh", but I wasn't sure if they do indeed think it's biased due to nuts being slang for testicles or not so figured I'd ask :) The use of nuts to mean crazy is incredibly common and actually predates it meaning testicles so I'd argue that it isn't very biased.