rkalfane

Yes, you could write a proxy auto-config file[1], host it somewhere and have it rewrite the urls you want.

I think that's how an ad-blocker worked on iOS before they enabled the functionality.

[1] https://en.wikipedia.org/wiki/Proxy_auto-config

There's https://vim-adventures.com/ although I never really enjoyed it, it was a fun game for the first 15minutes.

It looks like the 3D renders display a bit too many dots.

When you look at the picture of the man holding a prototype, you have 4 cells with no split.

I honestly didn't see the same thing as you, my understanding is that using the Lagrange Interpolation is the "clever" choice, but when you add more points, you'll end up with a higher order polynomial and widely different curve which is probably not what you wanted in the beginning.

I read the piece more as a reminder that most specs are usually incomplete/too specific/not conveying what is actually needed, and a warning against cornering oneself with a too clever solution. I also didn't see any big issues with their stance on FP, except maybe that they dismissed the Monoid solution that someone posted down in the comments that looks both robust and readable.

I really disagree with thinking about the interactions that late into the process. I think that, today, interactions are at the core of an application instead of just being eye-candy.

Putting your wireframes in a prototyping tool allows you to quickly test and figure out if the interactions that will drive your flow are good or not. You really don't want to know this only when you're done choosing your fonts/colors and aligning everything.

With the "wireframe prototype" you get a good idea of the structure and the main interactions. The mockups can give you the look of the app. The final high quality prototype is also not always super useful, and should be used, imho, as a communication tool with the clients if they need it.

(Disclaimer: I'm a designer and I'm probably very biased about the matter)

In my opinion it's very often a matter of expectations.

When a lot of design decisions are taken by a bunch of people, from management, engineering and marketing, including a designer would simply mean having one more person to compromise with. Companies working this way tend to have designers focus more on making the product look good, thus this dribbblisation of design. On the other side, engineering has historically been expected to deal with design when building products, and nowadays a lot of engineers have learnt how to design on the field. This reinforces the view that designers are only useful to make things look good. Lastly, the tools we use in design are really easy to use, anyone with a couple hours to spare should be able to create some stuff with most of the available tools. With that, it makes deciders think that the only difference will be a matter of taste.

A lot of designers can actually do more than that, the basis of their job is usually to question things with the perspective of the user: "Does it make sense to do this? Is it really useful to have that amount of customisation? How much information do we need to see?" Most of the time the solutions are stupidly obvious, or they're chosen based of how complicated it makes the system, or how costly it can be, and that's where experts add a lot of value.

All in all, if all you need is to make stuff look good, sure a dribbble designer is probably a good fit, just don't expect them to automagically make the product usable. If you want someone to work on your experience, you should probably have your designer work on the problem instead of having them "upgrade" your solution.

Just like how the engineering field is, the design field is really diverse with people doing different things, differently.

(Wow, that was a long rant, sorry about that.)

But then, fax machines are still the fastest and most usable way to transmit paper documents.

It's way easier to fax something, than to scan and send it, then having the others print it. I think that we haven't found a good replacement for the fax machine.