2,817 karma · joined December 16, 2014
> His next thought was utterly predictable: "I remember thinking, I'm gonna be rich! I'm gonna plunder the lottery!" he says. However, these grandiose dreams soon gave way to more practical concerns. "Once I worked out how much money I could make if this was my full-time job, I got a lot less excited," Srivastava says. "I'd have to travel from store to store and spend 45 seconds cracking each card. I estimated that I could expect to make about $600 a day. That's not bad. But to be honest, I make more as a consultant, and I find consulting to be a lot more interesting than scratch lottery tickets."[1]
If I remember correctly, thr Warby Parker storefront near me accepted a glasses prescriptions given out less than either five or ten years prior.
Fine for startups I guess. For the use case of someone who wants a CI server that, say, runs tests on their Project Euler private repo it's a no-way-no-how price point.
I assume they've thought this through and it's done purposefully. Still, side projects tools are a gateway to real project usage.
As an embellishment by the trolls, it would probably move any authority figures from a position of "let's figure out who got this dumb kid mixed up in these terrible things" to stony indifference and something closer to "serves him right." It also alienates him from his family so he has nobody in his corner any more.
Consider your own reaction as a viewer. Think about the other person who was involved in the last task of the episode. Did you feel any sympathy for him?
I wish the problem was being solved the way I think it should be solved, but I'm still happy it's being addressed. "Don't look a gift horse in the mouth" applies; we should encourage good behavior rather than taking the chance to be mildly upset about incentives and taxation and all the other angles from which one can be mildly disconcerted by the situation surrounding the action. I'm lacking an idiom here, but I feel like what I want is something like "snatching defeat from the jaws of victory" but for mild disappointment and good news, instead.
Waiting for a case where the FBI bangs down Google's door to get access to a locked Android phone before I make any assumptions about the security implications of that though.
Have you put this into practice? It'd be a nice contingency to have in place but seems like it'd put a damper on the tone of the negotiations ("I'm already thinking about being let go and want to make it really expensive for you to do so").
Even if they nailed the form factor, how many people are really willing to switch? You see some people swearing off a brand (on the internet, anyway) when something egregious happens but there's definitely inertia that keeps most people firmly in one ecosystem or the other.
> 196. If a superior man should blind the eye of another superior man, they shall blind his eye.
> 198. If he should blind the eye [...] of a commoner, he shall weigh and deliver 60 shekels of silver.
> 199. If he should blind the eye of a slave of a superior man [...], he shall weigh and deliver one half of the slave's value (in silver).
[1]: From page 106 of "Sapiens: A Brief History of Humankind" which I was just coincidentally reading on the bus and would def recommend.
I've been a 95% happy Containers user since it was a Test Pilot experiment but there are certainly cases where it's not enough. In my case, not being able to use the mobile device emulator in a container tab was a big pain.
There was an article in the New York Times in May, titled "How 2 M.T.A. Decisions Pushed the Subway Into Crisis" that claimed higher ridership is not the main cause for the recent decline:
> For years, the Metropolitan Transportation Authority told us that rising ridership and overcrowding were to blame. Yet ridership actually stayed mostly flat from 2013 to 2018 as delays rose, and the authority recently acknowledged that overcrowding was not at fault.
That statement doesn't contradict yours (shakes fist at well-qualified statement), but I found it surprising when I came across it and I imagine others might as well.
[1]: https://www.nytimes.com/interactive/2018/05/09/nyregion/subw...
Consider holding a referendum that specified nobody who hadn't yet been born as of the referendum date would ever be allowed to vote.
It's a purposefully silly example (HN isn't for political debates!) but broadly, it's a democratically made self determination that reduces or precludes the ability to make democratic decisions in the future.
It seems like the sentence would make more sense if it was talking about TypeScript and Kotlin instead.
The generated JS is readable and well-commented when for instance a record is transformed into an array. Just opening up the generated JS and reading it made for a nice self-check mechanism when I was starting out with the proof of concept.
Stubs with TODOs for staking out an interface to be implemented later and the like. Almost always doing "git add -p" is a good way to jog your memory about these. They can be committed but probably shouldn't survive until a merge into master.
A todo file entry for items which are heftier and/or not likely to be returned to today. My todo files are date-based so I try not to add todos for items with a time horizon beyond about three days in the future. I also try to keep these files small enough to actually get through in a day.
A single wish list/ideas file. Keep it in approximately priority order and pull items from the top when you finish your daily todos. This is also often feature-based so a single line might generate a bunch of tasks. Biased towards a personal backlog instead of "just add to JIRA/Trello/whatever" to avoid eternal agile deprioritization hell.
Works fine for me, though of course I'm not out here writing Redis either.
It's just someone trying to build an email distribution list for their (side?) gig. Feel free to enjoy the content without opting in.
The whole article is a good read but the thing that feels most pertinent is the idea of dynamic zoning; instead of zoning an area for single family residential you'd essentially zone areas such that new construction rules would be:
- allowed_height = max(2, ceil(avg_area_height * 1.5))
- allowed_occupancy = ceil(avg_area_occupancy * 1.5)
And then without the need for zoning exemptions and political zoning fights, you let neighborhoods up zone themselves organically based on demand. Average building two stories? You can build a three story low rise. Average height three stories? You can build a five story replacement.
I think lowering the barriers to higher density in-fill would effectively accomplish what you're aiming for while side stepping some of the political issues you've foreseen with raising taxes on people until they're forced to leave their homes.
[0]: http://urbankchoze.blogspot.com/2014/05/how-to-make-urban-ho...
Building Affordable Housing: Where Has the Entry Level House Gone?
http://urbankchoze.blogspot.com/2016/08/building-affordable-...
To paraphrase your question, you are essentially asking: "Why should I use language Y instead of X when X is fast enough for me, easier for me to read, and based on experience I like it better?" My immediate thought is that it sounds like language X is working quite well and aside from satisfying your personal curiosity there's no imperative to make that switch!