The biggest gain for me came from using a split keyboard. I had some bad habits where my dominant hand was crossing the keyboard to hit keys that my non-dominant one should have been hitting, and this was impacting my speed. By using a split keyboard, it forced my hands in to the correct posture and didn't allow one hand to dominate because the other side of the keyboard was too far away.
I was tracking my progress on typera.net, which is quite dated, but seems to have a nice balance of challenging words and phrases.
Thanks for the thoughtful reply. I am working at my office and your assumption that the sign up flow is blocked is probably true. You may want to fix that though, because my company has 75,000+ employees, who would probably sign up or investigate this service while at work.
How do I sign up? Where are the prices? Your landing page sent me in loops when I clicked Get Started.
I'm curious who you're targeting with this product. Wealthier families tend to have nannies, who will match expertise with implementation. Middle class send their kids to daycare or after-school programs, who also match expertise and implementation. Since this service is just expertise, who are the families that a) can afford this and b) have the time/energy/money to do the implementation?
My partner is in to the things that the Neumann’s are in to. As strange as their beliefs are, they are pretty much harmless. It’s easy to take on this belief system because it doesn’t ask much of you and doesn’t take much.
Haha, fair criticism, but don't miss the forest for trees. My point was about simplicity - I don't need to worry about this when making a website, but there's this new language and now I have to worry about this? It just feels like a step backwards.
And there is no such thing as a slow Java app? Or a slow Objective-C app? Just because it's compiled, doesn't mean it's better. Some websites turn your phone into a space heater because the developer is shit, not because the tech is bad (HN doesn't make my phone blow up...). Dart will suffer the same problem - shit developers - so developing all this tech mumbo-jumbo is pointless.
AMP, in my opinion, was a step in the right direction. AMP is google's way of saying "you're all shit at developing on the web, use this very restricted way of developing a website and watch how fast it will go".
That's what we need. Don't put developers closer to the computer by giving them compiled languages. Move them as far away from the computer as you can. Languages should be moving in the direction of requiring the developer to do as little as possible. I need to import a package to make HTTP requests in Dart; every fucking app makes HTTP calls these days, how outdated is that? HTTP requests are baked in to javascript, I don't even need to think about what I need to import, I can spend mental cycles on real shit.
Because what's "required" for the job is way too complex for the perceived payoff. That's why the JS/HTML is winning - the time investment to "do something" matches the outcome.
This is ridiculous, these bikes are a fad. The company will get sold to a gym or furniture giant for pennies once people get bored and realize they paid $2,000 for a clothes hanger.
I will say it's an interesting take on an old business. Furniture and exercise equipment manufacturers have this problem where everybody buys their stuff and they go bankrupt because nobody needs new equipment after the initial purchase. So attaching the subscription business model to this might give them a bit more longevity!
With Native ios/android, you get a selection of UI components to use. If your designs don't fit any of those components, you either have to build something from scratch or alter to the design to fit the Native UI language. Usually the prospect of 'building from scratch' is enough to deter people from building components that don't fit the device's interface. So you generally end up with apps that all fit the native design language.
With React-Native, it's really easy to be lazy. If you want to be on Android, but you don't want to change your designs to fit Android's UI standards, screw it, just write a wrapper around some of the iOS components and call it a day.
The issue is the developer. React-Native as a tool allows you to make poor design decisions, but it does nothing wrong itself. We need to be vigilant and remember to stick to native interactions.
Yes! I've been working with React-Native on a side project for a few weeks now. WHAT A GODSEND! Before this, I was using Titanium, which is heavy, slow, and difficult to integrate with. React-Native felt like home.
On a related note; Why is it up to Facebook to develop something like this? Why aren't Apple and Google making it this easy to develop apps? ObjC is a nightmare, 90% of apps out there don't need that level of control.