Yeah, this is Erlang:
fib(0) -> 0;
fib(1) -> 1;
fib(N) -> fib(N-1) + fib(N-2).97 karma · joined March 6, 2009
fib(0) -> 0;
fib(1) -> 1;
fib(N) -> fib(N-1) + fib(N-2).From my perspective, Erlang is a better fit than Node for all the problem domains that Node is good at. I understand using Node if you don't know Erlang, but do know JS, but if you're already skilled with Erlang...
As to your first question, yes I've experienced both. Not month long shutdowns, but week long ones, but it's the same thing: if it's not convenient for you to take a vacation during that time, it's pretty much a waste and it sucks. If your spouse doesn't get 4 weeks off on August, are you going to go on a 4 week vacation then? Probably not. But then you'll resent the people who do actually take that 4 weeks off to go somewhere. It's bad for morale.
I agree that a solid 4 week vacation is enriching, but just declaring an arbitrary 4 week shutdown is a cop out. Fix the structural problems that require every one to be in the office at once, and then give everyone that much vacation time to be used when they like it. I'm not saying that this is easy to fix, but if you really believe in giving people time to have significantly different experiences in their lives, this is what you'd have to work at.
Where I work even the national holidays are floating holidays, so if I want to work on Christmas that isn't a day off for me, and I can trade that for a day off for any other day of the year.
Especially for travel, it's way cheaper to do so for off-peak seasons, so forcing August or the last week of December etc. when just makes for more expensive vacations. This is one reason why I think the "French model" kind of sucks.
And I agree, SF<->LA is not a long drive.
Off interstates though, the west can get pretty empty. This is near the Nevada/Oregon border:
http://i675.photobucket.com/albums/vv114/cherokeeprogressive...
> One team that started with Erlang and moved to Java so they could find programmers. Think about those scenarios.
If the people you are hiring can't pick up Erlang in a couple of weeks of being on the job when they are doing that full time, with colleagues around who already know Erlang to help them, you are hiring the wrong sorts of people. Same goes for any other language/technology stack.
http://www.sussex.ac.uk/linguistics/documents/where_do_mama2...
I also recommend Thinkpads. The T and W series are good too.
If you look at the nginx source, that #define is guarded under NGX_HAVE_NONALIGNED and there is a fallback that does straight byte by byte comparison.
Not all trains. With Eurostar (Paris<->London) there's a security checkpoint with an x-ray and metal detector, along with passport control.
Twitter's limitation is based on thinking around SMS, but it doesn't actually match up to real world SMS, because they didn't think through all the international language considerations. It's pretty botched up.
http://www.aussieproducts.com/contactus.asp
(They do mostly mail order it seems, but they have a storefront in SJ)
Twitter started out as an SMS service, yet these days they cannot reliably deliver SMS messages. Kogi is awesome food, so whenever I visit LA, I turn on SMS delivery for Kogi's messages on Twitter. This would be a really great feature, since when I'm out for the evening I may try to stop by Kogi for some food, and it's great to get updates about where they are in relation to me, and if they're running late due to traffic (which happens a lot in LA). Except the last two times I was in LA, Twitter didn't send about half the updates to my phone. Which makes it not useful at all.
The Kogi case is a great application for one-to-many SMS updates, but Twitter completely drops the ball on that. Yet Twitter is so popular, there isn't really room for a more technically competent service to provide value. As we've seen already, merely cloning Twitter, even if you do it better, isn't enough.
The world could use a popular, reliable one-to-many SMS delivery platform. Instead we're stuck with Twitter. It's sad.
That's probably more due to the fact that Kogi made the New York Times and the LA Times, than due to direct Twitter awareness. Kogi often has long lines now, but that pretty much started happening when it hit traditional media. The first time I went to Kogi was last December, before it hits NYTimes/LATimes, and there was no line.
Definitely Twitter helped them hit their early following, but it doesn't seem that a majority of their customers now use Twitter. Last few times I've been waiting in line for Kogi, most people I talked to around me got the word that the truck was there due to their website itself, or word of mouth from friends.
> I didn't follow balloon boy but I can picture the scenario that anyone interested could follow the balloon's path in real-time
You could have also followed it on CNN. It's funny that Balloon Boy is an example. That story was not broken on Twitter, but via traditional news channels, and all the Twitter chatter was based around updates from those same traditional news channels. Except if you tried to follow the story on Twitter, you'd have way more noise to filter through, as Twitter has a lot of redundant posts (Retweets don't add any value when you're searching).
That's the story of OS X since from when it was first released. For example, you'd have some functionality advertised as being in the system libraries (like, oh, certain important pthread functions) so they'd pass the configure checks, but they would be in reality just stub functions that mean nothing. So your program would subtly fail.
That particular problem was fixed in 10.1, but it seems like every release has a few things like that: something from UNIX that looks like it's there, but actually amounts to no-ops. It's maddening.
Traffic is worse, however, around the other bridges in the area, since the interchanges to the major freeways (101, 880) at those bridges do not have the capacity to handle the offload from the bay bridge traffic. Some of those interchanges only have one lane vs. multiple for the bay bridge entry and exit points, and not enough merge distance to make things smooth.
Parking at most BART stations is also pretty much at capacity, whereas usually there is plenty of empty spaces.
5,300 had to be evacuated from the island of Heimaey due to an eruption in 1973.
What AMD did (and Intel subsequently copied) with x86-64 was to significantly drop the price of 64-bit capable hardware, to the point where it shipped on personal workstations which didn't really need it then.
-- Linus Torvalds
> If they aren't good enough for your team and your competitor ends up hiring them, what does that say about your competitor?
There are a number of reasons you may say no to a candidate who is highly qualified. They may not be a cultural fit for your specific organization, or you may have more than one qualified candidate but only one position to fill. So just because you wind up rejecting them, doesn't mean they suck.