102 karma · joined October 4, 2011
"Noticing a lack of significant public response to the visible nature of geo-location data on Facebook Messenger, despite media coverage dating back to 2012" - http://jots.pub/a/2015081101/
My parents also limited the time I could spend on a computer... and I ended up writing programs on paper while I waited for the next day :P
I'm tired of this stereotypical judgement that poor people are so bad with money that we'd be better off generously making purchasing decisions for them.
The big downside for me though is the login requirement just to watch - I don't think I'd watch Twitch if I had to login just to see streams. I think getting rid of that would really help you guys grow - code streams are pretty addictive once you start watching.
The idea that under privileged people can simply work and save their way out of poverty is naive and dangerous.
We used to think so."
The internet isn't about "don't take my stuff", it's about spreading that stuff around. I'm confused by people who want to make their data public, but want to control exactly how people access it.
"Such systems make it impossible to intercept
and read messages sent over a network, because
the very act of measuring a quantum object
changes it, leaving behind telltale signs of
the spying.
'It’s unlikely everyone would need this type of
technology...'"
I wonder if they're saying it would be impractical at a large scale, or that it's not necessary because it's not like everybody is being spied on or anything :)I'm tired of constantly being screwed over by any company that I'm not paying directly.
Now I just have to resist getting a peltier module and making one of these before 2015...
B does not follow from A. Just because your team is not producing "fast enough for the business" does not mean they are complacent. It may simply mean the business has unreasonable expectations. Outsiders (especially non-developer outsiders) cannot really give you any insight on this, as all codebases are different, and the time it takes to fix a bug or add a feature will vary depending on the amount of technical debt and complexity that have accumulated.
Your team however, is in tune with your codebase, and appear to be able to tell how long things will take (you don't mention that their estimates are inaccurate, just that you dislike the estimates). If you would like the amount of time it takes to be different, perhaps instead of assuming they are complacent, it would help to ask what needs to be done to make changes to the codebase faster. The answers you get (such as a higher level of test coverage to increase change confidence) might surprise you.
Of course then you can just block that other service as well.
But even if the law is on the side of the students (which I believe is obvious), that doesn't necessarily mean much if they don't have the same level of legal support that the state has at its disposal. This is why MIT fully supporting their students is so vital.