I remember years ago going on dates to fancy lounges with beautiful girls and telling them about how I used to spend hours practicing video games to compete in tournaments when I was a teenager, that this was the highlight of my social life in high school. To my surprise, they often became more attracted to me.
The self-awareness makes it cool. Knowing that you’re not always awesome counter-intuitively makes you more awesome.
There are two requirements to achieve meta-awesomeness: self-awareness and vulnerability.
In light of rapid advances in the fields of Artificial Intelligence (AI) and robotics, many scientists discuss the potentials of new technologies to substitute for human labour. Fuelling the economic debate, various empirical assessments suggest that up to half of all jobs in western industrialized countries are at risk of automation in the next 10 to 20 years. This paper demonstrates that these scenarios are overestimating the share of automatable jobs by neglecting the substantial heterogeneity of tasks within occupations as well as the adaptability of jobs in the digital transformation. To demonstrate this, we use detailed task data and show that, when taking into accounting the spectrum of tasks within occupations, the automation risk of US jobs drops, ceteris paribus, from 38% to 9%.
So, I’m going to leave this here for a later date…when I feel like purchasing the study to investigate further, but that is an intriguing claim.
React is a library for building performant interfaces for the web and other platforms.
You should use this guide as a companion to the official Facebook documentation for getting started. While the official docs are great, the React ecosystem includes many other important projects which are outside the scope of the React docs.
I love techniques that allow designers and developers to “break” the boxed in nature of web design in a general sense. As a micro trend, non-rectangular headers have become one of my favorite techniques to accomplish this ask.
So, how do I do this?
Per CSS-Tricks, there are several methods available to accomplish this particular task:
Background images, which appears to be one of the weaker methods
Inline svgs, which can be modified pretty well, and reduce the load on the browser
border-radius, which allows for the more convex circular look
clip-path, which appears to have browser compatibility issues
And my favorite, transform: skew
The Stripe home page using transform: skew.
As mentioned above, my preference in this case is transform: skew, although it introduces extraneous elements to the page–a seemingly forgotten rule is to not do so for presentational purposes–but this can certainly be accomplished with pseudo elements.
The article referenced above uses an extra element in the document to create the effect–which is perfectly reasonable–as does the stripe website.
Stripe’s homepage design uses this method, and even more brilliantly, they include a few children spans (each is a block of color) that get skewed with the parent element, creating a more complex and colorful effect.
I don’t entirely know that I like the extra elements, but I come from a slightly different era of development that saw this technique of creating decoration-only elements as heresy, while still using it regularly.
Anyway, I enjoy looking at the sorts of things that front end devs do to accomplish what UX/UI designers come up with.
I think in our tech heavy world we really don’t do the vast majority of what’s being suggested here–I struggle personally with 1, 6, 7, and 8–and connection with our fellow humans is a struggle as a result.
Use open-ended questions.
Go with the flow.
If you don’t know, say that you don’t know.
Don’t equate your experience with theirs.
Try not to repeat yourself.
Stay out of the weeds.
Watch the video to get an expanded look at each of these points.
I’ve been toying with a total and complete rework of this site for a little while, but to be honest I’m not sure what platform to pursue. Do I chose a new CMS? Do I go with Jekyll or some other static file variant? It’s difficult to decide–I know I’d like to learn a completely foreign and new skill set. For the time being, however, WordPress is my home. Fam.
My hope for this workflow–and it appears to bear out–is that I can rapidly design, develop, and deploy my updates and changes. I have been using Grunt for task automation for a while now–and that required a bit of command line knowledge–but I wasn’t initially using a git workflow. I mean, it’s just me, right? Well, I found that not using a git workflow made deployment much more difficult. What do I upload? What did I change? How do I undo this change?
I’ve really just begun to do personally what I do professionally–it just makes sense to introduce efficiencies into my personal workflow when I’m so used to working this way–and I’m not really sure why it took so long.
I’ve setup a Bitbucket repo and maintain a feature branch workflow while doing development work locally with a MAMP install. I’m not currently tracking my entire WP install, only my theme, but I do my best to keep the environments similar to one another. I completely skip a staging environment for this site–I feel like it’s overkill–so it’s not a duplication of what I might do in a more important (client) setting.
I don’t really have the money for a commit-to-deploy sort of environment, so I deploy using GitFTP-Deploy to deploy changes from my ‘master’ branch.
I am still using Node/Grunt for task automation…in spite of how quickly devs seem to have moved beyond it, but whatever.
This is a bit experimental on my personal work, but something I use in my day-to-day client work
Typically we’ll track the entire site, WP install, plugins, etc.
I am introducing this process into my freelance work as well…git repo and all
For now I’m working on a minor redesign/refresh and I’ll be doing that in real time
Guys, if you’re not already aware of it, you should learn now: Figma is a powerful alternative to Sketch. It’s collaborative, browser based, and highly flexible.
Well… I loved Sketch.
Until I started working on a cross-platform design system. Until I tried to implement nested symbols to keep my UI consistent. Until I tried to work with Sketch files in a team environment. Until I tried to hand off Sketch files to developers and had to pay for an additional subscription to a different tool. Until I had another sketch plugin or program that I rely on a little bit too much forget to update itself with a new release. Until I tried to figure out how to design with constraints in mind.