Data Science is a useful skillset for everyone to have, but the majority of the work in any practical data science role is in getting the data in the right place, in the right format to do the data science. This makes it such that most small companies can't actually support having a full time data scientist who can't also write code.
You have a good background in stats and ML - use that with practical experience in SWE to make your skillset more useful and broadly applicable.
The Caviar team is hiring!
We're looking for an iOS specialist and a full stack generalist to join our team.
We're building the world's best food delivery and logistics service. We’re changing the way businesses and consumers order food from restaurants. We believe that everyone should have access to the best eateries in their city without any hassles. Want your favorite burger joint, but hate the traffic and long lines? We're a team of passionate foodies solving that exact problem for your home and office.
Our software powers the entire delivery experience: we have close relationships with the best restaurants in every city, a network of Caviar Couriers and customer ordering products on 3 platforms.
The Caviar team is hiring! We're looking for an iOS specialist and a full stack generalist to join our team.
We're building the world's best food delivery and logistics service. We’re changing the way businesses and consumers order food from restaurants. We believe that everyone should have access to the best eateries in their city without any hassles. Want your favorite burger joint, but hate the traffic and long lines? We're a team of passionate foodies solving that exact problem for your home and office.
Our software powers the entire delivery experience: we have close relationships with the best restaurants in every city, a network of Caviar Couriers and customer ordering products on 3 platforms.
About to start a new heavy client-side interaction project, and I want to start it with the right structure so I can move fast and easily maintain it.I've been looking at the following libraries :Spine.js : http://spinejs.comBackbone.js : http://documentcloud.github.com/backboneKnockout.js : http://knockoutjs.comBatman.js : http://batmanjs.orgSo far, I'm leaning towards Batman, though I've used...
Also, why does everyone seem to be emphasizing this fantastic new technology, HTML5? HTML5 is just good ole fashioned HTML with a few new tags. I assume they're not calling out the header tag, or the nav tag, or the wbr tag...
When people say HTML5 do they really mean canvas? or CSS3 styles? And what does Ward here mean "nobody is skilled in HTML _5_"?
Don't be surprised when an evil company acts evil. Just don't work for evil companies.
http://harvesthq.github.com/chosen/
I'm sorry but progressive enhancement of a select tag into an autocomplete element isn't quite news worthy.
I started with the front end because I had a decent design sense and attention to detail. If you can care about pixel perfection, I think it's a good route. JavaScript, HTML, and CSS aren't the most difficult technologies to start with, and you get a little more leeway to make mistakes or write sloppy code in the beginning, learning as you go.
It's a good time to be doing this. There is need for developers enough that if you can prove that you're smart, a mid-sized or smaller startup may take a risk with you.
Try putting up a personal website. Set up your own server if you can, write your own code, and get something up showing what you can do.
At this point, do whatever you can to show that you've taught yourself a decent amount. You want to prove that you can learn, not so much that you're already a pro.
It would also be way better for developers if all computers had infinite memory.
It's just not in the cards though.
jQuery standardizes the mess that is JavaScript implementations so that developers can worry about their application instead of the browser. I don't think you should lament jQuery for being so popular, you should lament browser manufacturers (ahem, Microsoft) and the W3C for not creating and following good JavaScript specifications.
That's like blaming Dennis Ritchie for killing the Assembly community.
I'm not saying a standalone is invaluable, but if you're bragging about how it's only 7k, shouldn't there also be a 5k version for people already using the most popular JavaScript library in use today?
http://trends.builtwith.com/javascript/jQuery http://w3techs.com/technologies/overview/javascript_library/...
and, just out of curiosity, why do you say sadly? whats your HO?
http://www.thegorgonlab.com/blog/gains-and-losses
On the double edged sword of technology. Looking for feedback.