278 karma · joined December 10, 2013
Our institutions were more stable before because people were more dedicated to maintaining them. They were created because overt pain or death was the alternative. But then they began to protect us from discomfort. Then from fear of discomfort. And for discomfort that exists in the mind. This was bound to come apart around the time some people asked to be afraid simply said “meh”
Will this go badly? Certainly from the perspective of whether people feel safe and content. But we have had 10,000 years of self generated strive from humans. It is our fuel.
I’ve loved Slack for a decade, but today I have to plan to exit.
I would argue. They don’t have the right to change these terms on prior conversations. Only new ones.. Because I have a lad slack to hold my companies, important conversations under the belief that I would have access to them later.
I’m sure there is fine print somewhere that says this is not really legally true.
For what?
I ask questions and get wrong but “convincing” answers …that is way worse than wrong answers that are obviously wrong.
The functionality looks so smart because it skips reasoning and goes straight to “plausible imitation”. But the latter isn’t actually a path to the former.
If it were reasoning, and merely had errors the problem might-course correct. Even if the errors were huge, and reasoning was poor, it could eventually learn its way out.
It’s not intelligence. It’s a very good simulation of the superficial trapping of intelligence.
I would: 1. Get it in source control without “fixing anything”. 2. Get a clone of the prod server up and running, vs a clown of the db. 3. Put in something to log all of the request/response pairs. 4. Take snapshots of the database at several time points and note where they occur on the log history from number 3.
You now have the raw material to make test cases that verify the system works as it did before, but for bug, when you refactor. If the same set of requests creates the same overall db changes and response messages, you “pass tests”.
First thing to refactor is stochastic code. Make it consistent even if it’s a little slower so you can test.
Once you can refactor, you can do anything. Including a full rewrite but in steps that don’t break it.
If you try to rewrite it from scratch it will probably just never be deployable. But you’d an rewrite it safely in chunks with the above.
This is quite possible, if you write the "spec" in a programming language: i.e. write a test case. The problem is that people imagine a formal proof in, for example, English, being simpler or easier to think about than in, say, Python or C. In general this is not true. In general, moment you expect your "spec" (code) to be sufficiently precise for a machine to act upon it, the simplest way to describe it is a programming language.
And if you can invent a better way to describe it, and it is unambiguous enough for a machine to act on it, you've invented a new programming language.
But more sad than that, to me, is that creative energy on both sides isn't doing something more novel. A company doing something an intern can clone. An intern facing a sea of unsolved problems that chooses a space that is covered, as he points out, many times over.
If copying is the highest form of flattery, why flatter your former boss so much?
Then a second complicating factor comes in: most people interpret egoic/social peril like physical peril. For most of human history being ostracized by the community meant death. So we are willing to believe whatever we can get away with in a social context ...but not more. And the winners of a social egoic competition benefit from this. Competitors self-limit.
There is an illusion that confidence confers skill when what is actually happening is that a diminished ego has impeded basic functioning, and artificial self-estimation counteracts that somewhat.
Even if you aren't in the top 10%, you may be able to solve the problem b/c the average person is impeded by an artificially diminished ego.
Seems clearly that if youtube authorizes downloads, then people shouldn't put things on youtube they don't want downloaded?
The takedown notices should be going to youtube. But of course they want to use youtube to promote themselves.
Take the example of storing a continuous series of date ranges. If I only store the first date of each pair, I can never accidentally have an overlap or gap. But if my code has a logic error that incorrectly calculates a range, being able to represent it could throw an error. If that code error translates to an incorrect break-point instead, I haven't prevented a bug, I've hidden it.
It seems they should have just had the cops hide and wait until he actually tried to make a move on the undercover "girl" cop. Him showing up out of curiosity, perhaps even concern, is impossible to distinguish actual willingness to hurt a child if the jump on him immediately and arrest him.
The subject of child rape is so terrible, we give a pass to shoddy police work. One would think that a lack of child porn, or overt sexual conversation from the guy would have made the judge think he didn't actually intend to take advantage of her without more evidence.
The plot loophole in Minority Report is that they could have just stayed near the victim to protect him/her and waited until the perpetrator actually crossed the line of making an attempt, and arrested the person for attempted murder. Forget the whole central dilemma of the movie.
Mandatory minimum sentences have the same effect. The prosecutor uses the fear of the sentence to get a guilty plea and negotiates a plea bargain. This means people who should have gotten a fair trial in front of a judge and a jury are scared into pleaing guilty and letting the prosecutor decide how much time they will do by framing the plea offer. We bother to have judges to prevent this stuff, and should use them.
Mandatory minimum sentences have the same effect
We have been predicting machines would not need programmers since there were programmers. It is true for a _given_ task at a given complexity level. But overall the demands on, and for, a modern programmer have only gotten higher, because the demand of all business and human activity is to offer more than we might have otherwise.
Just wait until, for an app to differentiate itself in business, you have to create intelligent responses in a variety of augmented reality interfaces, correctly predict human behavior, and interface with the physical environment in a routine and nuanced way. And the companies that can do it well are suddenly dominating the ones who do a sloppy job.
Anthropologists estimate that the work week was at 20 hrs at the end of the Stone Age. We have been inventing new problems in the vacuum created by our successes for, literally, millennia.
But that is way different than Embrace, Extend, Extinguish from MS. I would not trade, say, Chrome for the world of IE. the tension between Google and Apple is far healthier for developers and consumers.