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.
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.
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_"?
Exactly my thought. Chosen has the advantage of working moo tools, jquery or prototype. There's also a drupal plugin. It doesn't have alternate spellings support, but that should be really simple to add.
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.
So, one thing I don't quite understand: If I have jQuery on my page (which I imagine now at least 50% of websites do, though that's just a guess) why would I want to add another script that redefines a bunch of jQuery functions? If you had a jQuery compliant version, wouldn't it be smaller, faster, better?
Not everyone does, but it is used by over 49% of the 10,000 most visited websites making it the most popular JavaScript library in use today.
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?
I might be wrong but I believe some parts of the JS community resent jQuery's ubiquity (which has arguably reached the point where people think jQuery is javascript).
That people are now taking the time to create pure JS solutions is nothing but a good thing, and there's certainly no reason why people should have to depend on a third party library if they don't want to.
Finally, your latter point about filesize is a false economy, because a 5k version still requires a 30kb DOM abstraction as a dependency. And since the thing has no external dependencies, why on earth would you want to hobble it with one it doesn't even need?
All these pure JS scripts and utilities get a nice new home in my bookmarks bar, because they're a lot more valuable to me than a shoddy jQuery plugin.
If you use 1 JS script on your site, i'll agree. What happens when you include 3 of these though? 10? 15? Suddenly you have tons of duplicate code, trying to implement getAttribute across browsers...wouldn't it be better if they all used the same DOM abstraction library...if only something like that existed...
Helping jQuery monopolise the JS space even further doesn't strike me as a good idea or beneficial to the community at large.
The main drawback is that it doesn't help people learn Javascript at all. And then it's hard to get information and help with JS because practically every result returns a jQuery plugin or something that uses jQuery. And as a result of that people think, "oh, I need jQuery installed to do some javascript on my site." And then other people complain, "this script isn't jQuery I can't-" ... oh.
Wouldn't it actually be better if JS implementations were actually standardised so its behaviour across browsers was totally predictable and reliable?
> redefines a bunch of jQuery functions
Just clocked this. jQuery redefines more than just a bunch of javascript functions as well as then redefining its own. It's a bit of a mess.
I totally agree. It would be way better if JavaScript implementations were standardized.
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.
Or maybe I use a different library? Maybe jQuery is not to my liking at all? The convention of writing libraries as jQuery-specific is a cancer in the community right now. Making a library specific to a particular utility should be a secondary project goal.
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.