The long term effects of a more rapid Ukrainian victory (and a dramatic Russian defeat) are difficult to estimate.
3,932 karma · joined July 9, 2010
I'm a principal product designer/builder, consultant and founder working remotely in Atlanta, GA, (previously San Francisco and Berkeley, CA).
IF YOU... -have a dev team that needs design support -are frustrated with UX strategists who leave you hanging when it's time for implementation -see pitfalls in the split between design & engineering -want to learn a better way to design, build & test your product -are not afraid to shake things up if it means your team can ship something awesome every time...
...we should talk.
I craft UX and frontend design in the browser. Your dev team will receive clean, shippable markup & CSS that's ready to be wired up. Because handing off pretty pictures for others to build is not my style.css ;)
Frontend efficiency is only one part of a well tested process of product creation.
1) UX begins with object modeling via "Object Oriented UX" methodologies to untangle domain complexity and establish a prototype data model. "Jobs to be Done" analysis establishes users' requirements.
2) Next we'll rapidly iterate the product concept by designing in the browser and testing to get feedback from users and stakeholders. Lessons gained from each iteration inform our goals for the next.
3) Each cycle is a step forward in all aspects of design: functionality as well as aesthetics and code quality. We'll call the iteration "final" when we've reached an optimal user experience written in code that's ready to ship.
Sound intriguing? I've been doing this for over ten years and it works. If it resonates with you, let's have a chat!
---
/* I'm available to help on your project with services tailored to your needs: */
.service--sm {
content: "Design Counseling: When a design issue pops up and you just need some input from an experienced and quick thinking designer."
}.service--md {
content: "UX Audit: Evaluating an existing product or feature."
}.service--lg {
content: "Product & UI design";
&::before {
background: "UX strategy & architecture"
}
&::after {
animation: "Testing & reiteration"
}
}/* Please reach out via email if you'd like to see if we'd be a good fit for future projects! */
---
email me: scott [@] designerwho [DOT] codes
(P.S. No relation to the Rene Herse bicycle company, maker of some of the world's most drool-worthy steel bicycles. )
The long term effects of a more rapid Ukrainian victory (and a dramatic Russian defeat) are difficult to estimate.
And with the amount of ventilation needed to make a PVC lined box into a healthy living environment, your kids will be conducting airfoil research at the dining room table.
The price is higher compared to cotton or synthetics, but it's possible to find good values by shopping sales. The daily rewards of wool (in every season) are worth the extra effort.
I'd love to hear of any more issues you have with Figma or your workflow in general.
What I'm working on is a web app that serves your project's Figma designs to a focused workspace where you can code them up. Different breakpoints, states, and specs are all right there, so there's no window switching and you never have to open Figma. And it notifies you of design updates.
Still a work in progress, but I hope to launch it later this year.
[TLDR: Typing for long periods while lying down with hands elevated above heart may cause an injury.]
A few years ago I built a lying down / "zero gravity" workstation. The position of my keyboard was very similar to the Altwork station, I.E. with arms bent at about 90 degrees with a keyboard and trackpad positioned above my body.
After a couple months of using it during full time working hours I developed severe pain in my wrists and forearms. This had never occurred before when using a conventional workstation / position. I soon became unable to type, and nearly any use of my hands resulted in intense pain. Writing code using a keyboard was out of the question.
After much reading during my forced hiatus, I came to a hypothesis: elevating my hands to type while on my back caused a decrease in diffusion of fluids to the non-vascular tissues of my forearms and hands, that is, the tendons and muscle fascia. While in this unlubricated, "dry" state, the small, continual movements of the tissues against each other (the motions of typing) led to the injury. I concluded it was tendonosis. (IANAD, but had no health insurance at the time.)
The injury took six months to fully heal, during which time I self-administered massage, myofascial release therapy, and grip strength training to increase circulation around the various tissues. For much of that time, I could barely work. Truly it was hell.
As for the workstation, I modified it to use a split keyboard (Ergodox EZ) that kept my hands below my heart (basically at my sides). But ultimately I abandoned the whole thing after failing to achieve a reasonable touch typing speed with the Ergodox.
My current workstation is based on an Ikea lounge chair and ottoman. Keyboard and trackpad extend from the side into my lap on a low-mounted, adjustable arm. The monitor is also on an arm, cantilevered out over the ottoman (and my legs) at a comfortable viewing angle and distance. This setup is certainly not as relaxing for the back as the previous zero gravity position, but in approximately three years of use I've had no further injuries from typing.
YMMV.
[1] https://groups.google.com/forum/#!topic/internet-bob/bWwsR-J...
As a frontend designer, I'd been hoping for some mention of faster SASS/SCSS compiling, but it looks like it's the same asset pipeline for that. Can anyone recommend a current resource for decreasing compile times?
I love designing in a Rails app, but my non-Rails projects all seem to inject CSS changes into the browser almost instantaneously, whereas with Rails there's often a wait of up to 10 seconds. The lag is pretty disruptive to the design workflow. I'm pretty new to Rails so any tips on what I might be doing wrong would be appreciated :)
In the case of plastic bags, they seem to be commonly mistaken for squid and jellyfish, eaten by the albatross and sea turtles, to name just two species.
So while the bag-free aesthetic on land is an improvement, the potential for downstream benefits is even greater.
I'm working on a product in a similar space, and struggling with the question for our own marketing materials. Amy Hoy's material [1] on audience "worldviews" has been helpful so far. (No personal affiliation.)
Best of luck with your launch!
At least for me the net emotional effect of the "For Desigers & Developers" section of the homepage was a strong impulse to bounce. (I'm in the target market.) Ultimately for the sake of research I clicked through to the ~/product page, where I found the diagrammatic graphics much more compelling.
Frankly, it's a broken system when it comes to politically fraught topics.