301 karma · joined May 27, 2009
Looking for a Senior Web Developer/early hires to help with our app. An excellent way for someone to get into VR/AR.
Our current stack is Rails on AWS. We do a lot of video transcoding/dealing with large files etc. Most of our tech choices going forward will be very flexible.
Seattle area or remote for the right person. fishbowlvr.com/careers/senior-developer hit me up or jobs [@] fishbowlvr [ com ]
cargo read-manifest --manifest-path .I think something as simple just monthly 3-4 novelty erasers would sell really well.
I also recall reading that paper yearly planners are popular in Japan right now.
Edit: I was thinking of these http://matome.naver.jp/odai/2135267959864327501 -- http://www.1101.com/store/techo/2014/planner/
Apparently I can't delete the comment myself at this point.
The language is actually the easiest part, the biggest hurdle seems to be organizing a complicated application to take advantage of OTP. Erlang is really about OTP; not the language.
I can't understand why you'd want to advertise that so blatantly. I'd recommend something less abstract, like a useful explanation of what your site does etc.
The title I submitted isn't great but, I can't seem to correct it.
- Long finder methods instead of using named scopes.
- Not using restful routes.
- Too much code in their views.
- After saves that should be validations or other confusing AR lifecycle mistakes/abuses.
I think a lot of people also see tests as slowing things down but, they also provide a lot of value in documenting intentions, make upgrades easier, etc.
If you find a bug, repo is here: http://github.com/jdeseno/PolyGlop, patches welcome!
r' f (x:xs) | xs == [] = (f x):[] | otherwise = (f x):(r' f xs)
or:
[(f a) | a <- myList]
- another edit -
r' f (x:xs) | xs == [] = x | otherwise = f x (r' f xs)