knivets

This. Often, you can't find where this variable or function comes from. You read the sources only to discover that there is no trace of this variable and it is probably defined dynamically in some callback. You can only find this kind of stuff with the help of debugger. The dynamism, which allows one to create beautiful interfaces, and is often advertised as a programmer's friend, is actually the enemy of the programmer who is going to read the code afterwards.

Banking run by humans has fundamental problems as well, that's why things like bitcoin come to existence. It is just a matter of tradeoffs.

AFAIK, most of the errors happen because users mistype the address or confuse the commission fee/amount fields, etc. UI could possible introduce some validations for fee/amount issue and probably require to retype the address or something else to avoid the other issue. Another issue is fraud, but it is a unavoidable product of such system, otherwise we end up with same problems traditional banking has. Fraud check means someone might deny the transaction even if your transaction is completely legit, for example, just because you are a citizen of a blacklisted country (my experience).

It is easy to dismiss bitcoin when you are a citizen of 1st world country -- because you are insider and have full privileges, but when you are outsider, it gets very complicated and things like bitcoin give some promise.

Well, we could try to create infrastructure around bitcoin which would solve the problems related to human error, something like delegating sending/receiving to 3rd party which has nice UI and double checks everything. It could also store your private key. You might say that this 3rd party can be hacked -- true, but the same applies to traditional banking.

Well, I'm not 100% sure if it's a monopoly because there is still freelancer.com, but I can't say anything about it.

Rails is nice, at least in the beginning. It's easy to pick it up and build something trivial, but it's pretty hard to solve some non-trivial issues -- you have to learn the framework internals. While, "frontend" side in Rails is pretty easy to grasp, internals are much harder, in my opinion (due to a very large codebase and Ruby's flexibility).

It is definitely a convenient tool, designed with programmer happiness in mind -- so there're a lot of things which will make your life easier. Although, sometimes this UX-centric model backfires and we get such things as RSpec.

Finally, it depends on what you are trying to achieve. If you are into money-side of the question, then maybe JavaScript ecosystem might be more worthwhile. Although, I believe that it is possible to bootstrap demand around tools that you are passionate about if you convince others to think the same way. My point being, that maybe you should look at the technologies that you love instead of following the market hype, but this is more harder and also means more time investment, but it pays off in the future.

I think procrastination has to do with mental award system — we tend to choose tasks which will bring the award as quickly as possible. But those tasks are usually not very productive, while those that are productive require significant time investments. Basically, it is about instant/delayed gratification. So the answer, I think, is to pick jobs/tasks that are more balanced (average time to achieve gratification, average productivity). I think this is what "job you enjoy doing" should look like.

> If I had been a black kid? No way. I can’t imagine that the teachers of a white, white, white suburban Boston high school would have patted me on the head for all of that. Opening unlocked doors would have been taken as breaking and entering. If I told them that I’d put in a lot of time to decipher the mechanical workings of a common school lock and how to exploit its weaknesses, they’d have assumed the only reason I’d have gone to all of that trouble was because I planned to steal stuff, not because I was intellectually excited by an intriguing puzzle.

Too polarized and emotional. There is a problem, yes. But that doesn't mean that all teachers will treat a black or brown child differently from the white one. And also America is not the worst case. Here in Ukraine almost everyone hates black and brown people.

If their profit has decreased by 51% in this quarter, there is a chance that they will have even less profit in future, which means that they will need to lay off even more people than 3k. That's why they need to take measures now.

Looks great.

Recently, I was trying to wrap my head around eigenclass inheritance mechanisms and it was pretty tough. Not to mention the object model, where classes are also objects and the Object - Module - Class relationship. I wouldn't recommend Ruby as a first language to anyone — it may look easy at first, but to grasp it, you need to invest much more time in future.

It is the same guy who wrote this — http://www.washingtonpost.com/blogs/wonkblog/wp/2015/01/14/b...

It would be cool if Tesla could also come up with something to improve batteries used in portable devices, so we can use phones or laptops more than 1-2 days without recharging.

What service are you using now?

The url leads to the home page of the blog, this should be instead - https://mitchkirby.wordpress.com/2015/04/21/where-does-weigh...

What's funny is that he was also promising to not put any ads at VK (russian social network he founded) ever, but pretty soon he acted in an opposite way.

That you are the villain type (from the article)

Why is it a bad choice? Why does it need reverse proxy functionality? Why not use some reverse proxy software (e.g. HAProxy) in order to follow the UNIX modular principle? I'm not trying to argue here, but rather trying to understand.

Read at first as GitHub's IPO.

As far as I understand, you need interpreter only if you want to run file as a script, but if you compile beforehand, you can just use it, so no need for Haskell to be present in an operating system.

Looks very interesting.

Make for building — interesting.

Frameworks are also good in a long run. When a new member on the team starts to work on a project, it is much easier to pick up on some popular framework like Rails than your own one. First, because you can easily find a guy who worked with Rails framework and knows it inside out, unlike yours custom-written one. Second, the whole infrastructure, like regular updates, documentation and community is also a major factor.

> "secure" (it really isn't)

There was a contest held by Pavel, with $200k prize who will break this "weak security". No one succeeded.

The main conclusion you can draw from this story is that you should read, learn, research and think more before doing something, not after.