At least that's how I interpret Vinhboy's comment.
2,040 karma · joined January 4, 2011
At least that's how I interpret Vinhboy's comment.
I mean, job interviews are very competitive, they are time constrained, and they result in a binary decision made by some external authority, just like competitions.
> Video: 73k
Yes, but with some loss of quality http://imgur.com/1qkJYEA
(not as much as I thought, though)
It may be true for short time blocks (days, maybe weeks) but I don't think this is the case for longer time blocks (month, years).
- If you do the same thing every day, years will pass by very fast.
- If you move to a different country for a couple of months, afterwards, it'll feel like you've been there for years. It's because you seen/learned much more. I've experienced that a couple of times, it's a strange feeling.
I believe that this is because our perception of time is nothing else but perception of self-change.
Elaboration tolerance is the ability to accept changes to a person’s or a computer program’s representation of facts about a subject without having to start all over.
This could make a good definition of what is 'good code'.
[1] http://jmc.stanford.edu/articles/elaboration/elaboration.pdf
On the other hand, I don't see enough information to discard this hypothesis.
I'm tempted to believe the author of course, but I don't think this is not plausible as an explanation for this truly crazy story.
A bias has to be in favour of some people. Those people are usually the ones who include their photos.
E.g.
$> perf stat echo "hi"
Performance counter stats for 'echo hi':
0.718209 task-clock (msec) # 0.595 CPUs utilized
2 context-switches # 0.003 M/sec
0 cpu-migrations # 0.000 K/sec
59 page-faults # 0.082 M/sec
844,067 cycles # 1.175 GHz
561,879 stalled-cycles-frontend # 66.57% frontend cycles idle
<not supported> stalled-cycles-backend
611,918 instructions # 0.72 insns per cycle
# 0.92 stalled cycles per insn
127,740 branches # 177.859 M/sec
7,279 branch-misses # 5.70% of all branches
0.001207821 seconds time elapsed
For more stats, check perf listIf you don't work with private branches, it's not surprising that you don't see any value in rebasing which is mostly useful for private branches.
In fact, if you don't have private vs. public scenarios, it's not really clear whether you need a distributed version control system. But that makes sense, DCVS were developed for OSS after all.
The other thing is that FOSS projects typically involve contributors from all around the world and cultural differences are always very sneaky, it looks like everybody is a hacker, but in fact most share completely different cultural codes. For example I've noticed that people from the US are used to cheer a lot, that definitely not the case everywhere. So for US contributors, I'm guessing working with people with a different mindset with respect to criticism can be quite a shock.
So the beauty of FOSS is that it kinda works despite the extreme work conditions (distributed / remote / every body is allowed to say whatever / people work when and if they want / etc.)
I've heard several poker players saying that it's hard to play against novices, because they do nonsense.
Surly there is some game theory that says something about this. Anyone?
The blue lines are not trends, but prayer times plotted on top of the graph.
Clearly advertising works, so some people must be exposed and influenced by it. This product is useful for those people.
Do you have a reason to believe that you are less exposed or influenced than the average person?
(I can't find a way to phrase it in a non-jerkish way, but it's actually a genuine question)
One of the implicit point of the article (that maybe shouldn't be implicit) is that these issues are not, in fact, orthogonal.
For example this:
Most of the computer languages used to write web applications such as DCMS systems contain a feature called eval, where programming instructions can be deliberately promoted from data to code at runtime.
In other words, proper input hygiene is a problem because you're dealing with a language that allows execution of data (i.e. a dynamic language).
His claim is that the mere fact that the language contains an "eval()" function (which is a feature of dynamic languages) inevitably increases the risk.
Quoting: Most of the computer languages used to write web applications such as DCMS systems contain a feature called eval, where programming instructions can be deliberately promoted from data to code at runtime. [...] but when it is left accessible to unskilled or malicious users, eval is a recipe for disaster.
> A TLDR of the original article: "Handling user input can be dangerous, it's safer if you don't." But we already knew that...
I would say:
1. DCMS are bad for public facing webserver because they process user inputs with a language that supports function as powerful as "eval".
2. DCMS are bad for public facing webserver because they run slow interpreted which is "1000 times" slower and enable DDOS
Lisp code is the stereotypical example of a dynamic programming language because it can update its own code while being executed.
On the other hand, compiled C code is static because the code is loaded into memory and cannot be changed during the execution (as a matter of fact, the memory pages holding the code don't have even have write permissions). Btw, you can make it more dynamic by enabling dynamic libraries or modules which make the whole thing less secure.
In a static program, you can only execute code that was originally provided (at least in theory), that makes it harder to accidentally execute a piece of code provided by the user as input.
Back to our problem: A dynamic website will typically take user input (e.g. the user name) and build a personalized view of the webpage for the user. To achieve this, the page will probably contain a SQL query with a 'name' field. If the inputs are not properly sanitized, the field can contain anything including SQL code. If the user is malicious, you have a SQL injection (i.e. the user can execute an arbitrary query). What happened is that you've executed code provided by the user.
> Sure, but guess how those pages are returned? By running code on the server..
Yes, but by running static code.
> > The web server executes no code on behalf of a viewer until that viewer has logged in.. > 1) Of course it does, 2) How do the site check your info without executing code? :)
Again, static code.
So his point is not that we shouldn't run code at all, but that we shouldn't run code that heavily processes user inputs, or worse, evaluate generated code as DCMSs sometimes do.
Of course you can argue the no code is truly static, because it depends on the user input, but I don't think this is what you're arguing here.
Usually people that work at night, how much noise they can make when they came back home early in the morning? What about people practicing music instruments? Can students party at night if they have neighbors, just once in a year? once in a month? Is it ok to bring a stroller in crowded areas? etc.
I don't think it's possible to give an answer to any of these questions that will get more than 60% agreement in any sufficiently diverse community, even given the full details of the situation.
Waking up 2 or 3 hours before the sun rises in winter, or 2 or 3 hours after the sun rises in summer isn't very natural. Daylight savings reduce the gap by one hour.
Recognizing someone is a hard problem that most humans can do efficiently (except me maybe)
Yes, but taxes and regulations are meant to exert a control how much more you can consume as a rich person.
Now, taxes are fine in many cases, but not always. For example, you probably wouldn't want to live in a country where you can pay for a (taxed) killing service. Hopefully, we agree that this would be "odd".
The problem here is precisely to decide whether it is odd or not to let people emit as much as CO2 as they want (provided that they pay for the tax). Or if we should put a hard limit on it (i.e. a regulation).
I personally think it is indeed a bit odd.
Noise is a mechanical wave produced by something vibrating. If you can hear it, it means that thing is vibrating quite hard inside your monitor.
This is important because if you want to decode a hashed password using a rainbow table for example, you still have to hash the entire keyspace, not just half of it.
Edit @sp332: Exactly. That was my point.
[1] The practice of officially examining books, movies, etc., and suppressing unacceptable parts. (www.oxforddictionaries.com/)
Edit: (Trying to be more factual) NYDailyNews removed unacceptable parts, which is censorship according to [1]. I'm not claiming this was a good/bad decision.
My feeling is that we've been enjoying this wheel technology for quite a while already :/