I'm definitely a designer first, so I see things through a design lens. But I think that taking the time to truly understand your users as best you can—whether you're a designer, developer, PM, support, sales, etc—is the first step to building a good product and being able to identify these high impact areas.

just to be clear, when I said you were a designer rather than a dev, it wasn't intended to denigrate you, just to correct the inaccuracy in the "other devs" phrasing.

from your writing, it was very clear that design was your priority, whatever other skills you might also possess. so I feel a bit vindicated seeing your username.

Hey, the first tweet is mine. Codespaces work pretty great on an iPad. We're going to be making improvements to the experience here as we get to GA but we know it's a scenario everyone is really excited about.

Is the screenshot of Codedpaces from your iPad or macOS? Because that looks a lot like safari on macOS.

https://mobile.twitter.com/notdetails/status/125807069916558...

It's a mockup in macOS safari, but I'll tweet a video of it running on my iPad at some point

It speaks to the intention behind the design, which apparently isn't user value.

Many thanks :) I'm glad it resonated.

Also: http://h1bdata.info/

Seems to have more data.

You're welcome, thanks for reading :)

Read this a few weeks ago. Really useful advice.

I have a similar engine up at http://joelcalifa.com/colors

Mine can also do colors like "banana" or "bubblegum". Pretty simple to put together actually. Rather than manually putting together a list of colors, I just use the ColourLovers API. You can also use up and down arrows to move between results or the return key to "make a poem," which I fully agree was a weird feature to add.

The best thing touch screens have going for them, though, is direct interaction.