What I don't understand is why can't somebody love to code and not maintain a public github repo? Sometimes you want to keep things private-- it shouldn't have to mean the best stuff you developed has to be on github in order for you to get a good job as a programmer. It's on the technical interviewer to test out programmer's skills. Too many non-technical recruiters these days are passing on candidates because they don't have a big github repo. That's a cop out and an insult to the profession.
No joke. If I code for a living, usually I want to spend my free time doing something OTHER than coding. The projects I DO work on in my free time are for me - usually silly little things (maybe in a new lang that I'm playing with), and not indicative of standard of code quality I produce in the "real world."
In my opinion most programmers who use github should have at least two accounts, one carefully crafted to match some tradeoff between their current work environment and future work aspirations and heavily linked to their real name, and the other pseudonymous with no real name containing their real hobbies and code.
There is a substantial danger in being pigeonholed and eliminated because of some weekend hobby project three years ago "Oh we can't hire that guy, he does low level hardware driver work on microcontroller RFID devices and we need a DBA" Outside SV and NYC there is no shortage of coders and you'll get rejected for nothing.
I personally like to do gardening, home improvement, spend my time with my family over the weekends. My normal work time keeps me deep into coding and I just don't want to do 100% of my week.
I saw an interview once with the producers saying that 1955 was not that much in the past had changed. So for some of the things (like the gas station attendant scene and some of the cars) they had to go back into the 40s to make it look 'older'.
> Flash still has limited write cycles. Its for data you probably wont write more than once an hour, but not virtual memory.
You can write data to SSDs a lot more than once an hour, even virtual memory. The drive's firmware (assuming it does its job) will do wear-leveling and spread the logical writes across different physical locations on the drive.
If you write 20GB of data per day to a modern 480GB SSD you can expect 25 years of service. (Realistically, something else will probably fail before then)
I've been dying for a thicker phone in exchange for better battery life for quite a while now. Seems like this phone might negate a lot of that benefit with the much larger screen, but I wish more phones were willing to make that trade-off.
