Protip from my side if you're crashing Airbnbs full-time: bring a knife sharpener. I've yet to see the Airbnb that actually had a usable set of knives. Typically all dishes are whatever cheapest you can get at IKEA.
I would write and share more, but the HN tribunal is just too bitter and merciless to expose your weak and vulnerable self to – as the comments on this post perfectly illustrate.
I don't even get why people wouldn't use normal GPT API (OpenAI completions) instead. Isn't it exactly the same except that ChatGPT is primed to be more conversational (which in many cases as the one in the OP is just noise anyway)?
Basically an approach that leverages the advantages of utilities and blocks and embracing the `Cascading` in CSS instead of working around it, like BEM et al. likes to do.
I'm three months into colemak now, together with learning touch typing (and switching to vim as main editor).
I've managed to get up to around 50 wpm coming from 75 wpm with normal qwerty without touch typing (just 6 finger freestyle). I've still some time to go to get over my initial typing speed. A really cool thing about colemak for me is replacing caps lock with backspace, which in itself is getting rid of so much finger/hand-travel, but that can obviously also easily be hacked into qwerty as well.
To this point, I don't know if I would recommend switching to anyone for the following reasons:
- You will slowly use muscle memory of normal qwerty, which can become quite awkward whenever you forced to use another computer. It's not like you cannot type it anymore, but you will be quite slow and inaccurate when typing. However, these situation barely exists for me in everyday life.
- Learning the new layout is quite a feat that takes time and daily dedication. I decided early on to use the new layout in my job (frontend dev) which definitely speed up adoption for me but also slowed me down considerably for some days. Even then it will take quite some time to get back to your initial speed.
- Depending on your profession, typing speed may not at all be a bottle neck. This is true for me as a software developer, where you spend the most time thinking about how to solve problem before typing them in small chunks.
- Wrt touch-typing, I weirdly found out for myself that it can actually cause some wrist and hand strain rather than protect from it. To me it feels that by using a lot more muscles to type it also increases chance of wear-and-tear. This is especially true for the pinkies for me, which I never used much for typing before.
Good thing about colemak wrt keyboard shortcuts is that it only changes letters (no symbols, punctuation, etc.) and then as few letters as possible to still achieve the best finger travel. In practice that means that many shortcuts stay the same, e.g. the common ones as CTRL-Z/X/C/A/Q/W etc.
I sort of did the switch as a self-experiment after being intrigued by all the science behind optimized layouts, and also to challenge myself to learn a new skill for the new year. I wanted to learn touch typing after decades of freestyle typing which I increasingly noticed was very error-prone. I figured that learning a new keyboard layout at the same time is a very good opportunity.
Not sure if I will stick to colemak permanently but so far it's still fun to try to gradually improve on it.
Being able to calmly and piecefully experience the many cultural heritage sites, temples and gardens of Kyoto without any foreign tourists was one of those once-in-a-lifetime experiences for me (among others).
I guess if the original design was flawed enough to begin with, then obviously people catch up on proper redesigns a lot easier since any good UX work will naturally make them feel more understood by the product.
Win3.11 to Win95 springs to mind here.
In contrast, going from "good UX" to "better UX" is a whole different endeavor since you'll have to fight against the friction of people having to give up routines and flows that they have been sticking to for a long time. A thing which no amount of thoughtfulness and consideration of a redesign will be able to make up for – that is, initially.
Interesting to finally see some criticism about hooks.
The biggest problem I have with Hooks is readability. IMO, functional components with hooks are harder to reason about since they obfuscate logic in a weird react-specific contract.
Class components have a much simpler, contract and syntax. They also felt much more natural since they picked up on familiar concepts of JavaScript, albeit with a couple of drawbacks.
I get the advantages of hooks, but in a way, at least to me it seems like they, at substantial cost, solve a problem which I barely ever encountered, even after building react apps for many years.
Fellow (German) Kevin here. I like how this topic is frequently being brought up again in loose intervals as if it is important to remind everyone every once in a while.
I can confirm that there is indeed a stigma associated with the name. As a white young male though, being grumpy about such thing would be quite disproportionate. In that sense, it sort of makes me get an idea of what it could be like to be ridiculed for something one has no control or responsibility about.
Been using this for a while due to student-related poorness. Gotta say it does what I want and has helped numerous times also in bigger projects. The low fidelity helps you focusing on gui structure.