240 karma · joined March 1, 2012
I was in high school when the movie came out, and we were on a 6 week road trip all over the USA that summer, so I couldn't see the movie. Those days they also published books for a lot of the popular movies (sold at gas stations), so I bought and read the book. I only got to see the movie a month or 2 after release when we were back home in Baton Rouge. The book was the director's cut, and to this day I seem to remember that the version of the movie I saw also had that ending (my brain playing tricks on me). There's also the scene where they cut open his skull to put his cpu in learning mode in the gas station. I don't know why they cut that, it works so well with John asking "are we learning yet" in a next scene.
We're trying our very best to support and guide without shaming. The difficult part is the influence of friends, specifically a boyfriend, that were convinced led to much of this. Forbidding the relationship is not going to have the right effect. So we're trying to manage it with rules to try and prevent the opportunity to make bad decisions. And talking a lot about honesty, values and respect. There's still respect in our relationship, and I feel that's the key for us to be able to support her.
How dangerous can this be in the wrong hands? Seems like it can significantly lower the barrier to entry for someone wanting to gain unauthorised access to many buildings that use remotes or RFID for access control.
>having or showing an obtuse insensitivity or lack of perception particularly in matters of public sentiment, opinion, or taste
Having read that I stand by what I said. In my opinion he has shown "an obtuse insensitivity or lack of perception of public sentiment" on more than one occasion. The Minsky message being a very good example. Whether you agree with the sentiment or not is seperate from clearly being obtusely insensitive about the public sentiment I think.
Seriously?
When things don't work out according to the schedule, there are generally two reactions :
1. We didn't estimate well enough, we need to estimate better next time.
2. Maybe this estimation thing is impossible to get right, let's not put too much trust in being able to estimate accurately, but rather find ways of working that don't require estimating all work up front.
I've seen that 1 gradually becomes 2 with experience (the experience of getting the estimates wrong every time).
Senior iOS (Swift) Developer
We're a company with a remote first culture, building mobile products for startups and enterprises in Fintech and IoT. We have clients all over the world.
More info : http://www.polymorph.co.za
Interested in working for a company in one of the best cities in the world in terms of natural beauty, food, things to do and cost of living[1]? Mail us at {info at polymorph dot co dot za}
1 : http://traveller24.news24.com/Explore/SAHolidayGuide/cape-to...
We didn't even make the development cost back. We actively fought against the idea of IAPs and trying to hook whales, even though it would have been easy to introduce mechanisms to do it (on the hardest level it's almost impossible to beat).
[1] iOS: https://itunes.apple.com/za/app/fleet-of-one/id580453079?mt=... Android: https://play.google.com/store/apps/details?id=za.co.polymorp...
Selecting the team to build the product on price is often a bad idea, and that's all fixed cost gives you above agile (the ability to select on price).