looser
I have a different advice that will give you two important lessons at the same time:
"Sell something, as soon as possible."
If you have a product that you can build quickly. Build it and sell it, ASAP.
If you don't have a product... Good. Use the money you have and buy some product that you can sell for more... Repeat it.
Sales is the quickest way to make money and consequently will teach you about business.
PS: At this point it is preferable to find cheap products, so you can buy <-> sell quickly, until you have a good sum of money... then, you'll be able to elaborate the perfect product/business you have in mind.
If a developer has source code/projects available, why only look at his resume? Look at what he's DONE, and take your judgment from there.
America != United States We know that an "United Stater" is also an American, but there are Americans who are not "United Staters".
[Random link]: http://www.beeman.ca/sitebuildercontent/sitebuilderfiles/mob...
Evaluating a language by just reading the introduction is like reading the introduction of a book and saying that you didn't like it. Read it! :)
It seems we are focusing too much in a possible weak point and forgeting about several strong points Haskell has.
Sometimes the more you fill your mind with (judgemental?) thinking, the more the creativity escapes.
Sometimes the more you empty your mind with secondary thinking, the more the creativity appears.
Sometimes playing a musical instrument is a good thing.
Sometimes doing a query without joins is incoherent yet good results come.
1 - It seems Mauro added a new error message called ENOENT; 2 - After this change, Mauro noticed an error at pulseaudio; 3 - Linus says that always the userspace is right and kernel space is wrong in those cases and simply discarded Mauro's argument;
But thinking about this I think Mauro is not entirely wrong. Mauro's question makes a lot of sense to me: Why pulseaudio failed after just a new error code was added to the kernel?
Can't it be that pulseaudio is doing some wrong treatment that is ignoring the possibility of a new (or non-existent) error code?
Couldn't it be that software is heading a paradigm shift in the economic model?
I would enjoy dealing with indie carpenters but still can't find them :)
That's an hyperbolic statement and is not true. Brazil and USA have a similar law system regarding censorship.
Next, the author mentions about several limitations that C# has and that Haskell has a much better approach.
So, why use C#? Why not only use Haskell?