You may be interested in typing.io, which is specifically for code. I don't think it'll help much with numbers though. Personally, I've never gotten the hang of touch typing the number row, so I use the numpad instead.
I switched from typing.io to https://github.com/jankrepl/mltype. Highly customisable.
I run it from a bash script in multiple steps with custom length. First special characters only, then numbers, letters, go and finally rust.
I do this on a daily basis just for a few minutes and I could greatly improve my typing speed.
Without any headers, metadata or padding and using RLE one byte for 0 and 8 bytes for the number of zeroes: 10^15 will easily fit 9 bytes and can be used to generate a file filled with one petabyte of zeroes.
It's actually good practice to wrap a bit of code like that in a function with a name, as long as it isn't in some kind of extremely frequently executed inner loop.
'starts_with' is descriptive and language agnostic where '=== 0' is neither.
I think it does. I'm guessing most of the people who take the single outfit approach do so based on what they've heard about decision fatigue. Not because they want to save the 30 seconds they spend picking out a shirt every morning, but because that decision supposedly impacts their decision making for the rest of the day.
Just not with Xcode projects? I was looking for something like xcodebuild that I could run in a docker container and never found anything. Can you point me in the right direction?
AWS and Heroku aren't really competitors. Firstly, since AWS is IaaS, whereas Heroku is PaaS, they target different users. More importantly, Heroku is built on top of AWS, so Amazon gets paid for all the resources used by Heroku apps.
Sort of. They're still targeted at different users, though.
Heroku is for individual developers to directly develop their app in terms of.
AWS, meanwhile, is mostly for enterprises: it's a "virtual datacenter" for your (much-reduced) ops team to manage in place of a real datacenter. In that sense, Elastic Beanstalk is not a service that AWS provides developers—it's a service that AWS provides your ops team to provide to in turn provide to your developers.
Yes, and furthermore there's a very good reason to believe that this claim is true: as soon as they do, every copy of Chrome behind AT&T's network will go and snitch to Google, who will promptly investigate and get Verisign in deep trouble.
Here's what happened when Symantec issued fake Google certificates last year:
"Therefore we are firstly going to require that as of June 1st, 2016, all certificates issued by Symantec itself will be required to support Certificate Transparency. After this date, certificates newly issued by Symantec that do not conform to the Chromium Certificate Transparency policy may result in [annoying certificate warnings, just like self-signed certs]."
And that was just the work of a couple of employees who were inappropriately testing their issuance system and weren't even intending to attack anything. They got fired, which I expect is also a big part of why Google's response was so light.
