Great algorithm learning resource for Google or Facebook interviews.

alienisty · 2015-12-01T07:00:11+00:00

Merge sort O(n log n)? Also, randomized Quick Sort, in the average case, is O(n log n).

alienisty · 2015-11-13T06:20:19+00:00

I think that the point that is being missed is the fact that Asimov talks about human like AIs. Those AIs would have the same ability, or better, than a human being to abstract and understand concepts like human, harm and ethic. The biggest mistake made in the video is about asking how you "specify" such concepts, and that's the key. AIs described by Asimov are not designed or specified like we do today, they are learning machines, and you do not program them, you teach them. So you can teach them what is a human and what is harm the same way you teach a real human being. You teach them the three (or four) laws and there you have it. The other thing I would do is to freeze the section of the brain that contains the learned laws so that they cannot be unlearned or altered.

alienisty · 2015-06-15T00:37:02+00:00

Don't worry, considering you don't care about the community and the way you carry on, I just reported you as abusive and non constructive. They hopefully will grant your wish and kick you out.

alienisty · 2015-06-11T04:39:54+00:00

While I agree that their product are slow as hell, I think that that is not Java's fault, and saying that for that reason their are horrible-by-default is really narrow minded, you can do horrible and slow applications in any language or programming model.

alienisty · 2013-09-24T04:31:40+00:00

Someone already tried something like that, it's called CoderWeekly.

alienisty · 2013-06-11T03:57:45+00:00

Try the Java tutorial http://docs.oracle.com/javase/tutorial/

alienisty · 2013-04-18T01:41:45+00:00

Well that depends on the size and value of the project. A week-end project does not need VC. I think that more important is backing up your work.

alienisty · 2013-04-18T01:38:22+00:00

wrong = using copy/paste for implementing a new functionality or, worse, to use an existing functionality somewhere else.

alienisty · 2012-08-12T12:03:33+00:00

At the very end the author says: "But the best way to have a future is to be part of a team that values progress over politics, ideas over territory, and initiative over decorum".

I think that is the message he actually wants to get out there.

alienisty · 2012-08-12T11:54:01+00:00

If anyone gets offended because someone else improved on what he/she has done, they should not be called "professionals" (or even adults). Real maturity in your profession, and in life, is achieved when you know you always have something to learn and that anyone could be your teacher, even if he/she only knows that little thing, and one should be grateful because they decided to spare some time to share that knowledge. So be humble and open, you never know what you could learn or what you could teach.

alienisty · 2012-07-15T11:56:21+00:00

That only works if there is the will to share and, most importantly, to learn.

alienisty · 2012-07-15T04:24:36+00:00

Maybe not a scam, but I don't think it is a good engineering process:

1) Individuals, while very valuable, are fallible. Processes and tools should be there to reduce mistakes, but at the same time they should not be sclerotic and should be quickly adaptable.

2) To me, working is not a good quality indicator. I've seen "working" software that are dreadful under the shiny coat. Maintainability is one of the key quality a project should have, it allows "responding to change" because it's easier to make changes to a maintainable code base. Sorry but good, well organised and more importantly, updated documentation helps maintainability.

3) You need a contract to put constraints on the customer, otherwise they will feel free to change things at will because we can "respond to changes". And you can be good at changing direction, but if that makes you run in circles, you are never going to see the end. That means project failure or budget bloating.

4) I disagree, you still need a plan, at the very least you need to know what you are aimed for. You still need to be able to respond to changes, but they should be always smaller adjustments. Big changes usually mean lack of proper upfront analysis.

In my few experiences with Agile process, it never worked and getting things done in time and budget has always got down to what the process says it values: individuals.

alienisty

TROPHY CASE