The more I type the more I realize how pedantic this is, but we're emphasized in stats to pay extra attention to the conclusions we draw from the data we analyze.
52 karma · joined April 8, 2013
Website: stevenwu.info E-mail: steven.wu.work at Google's e-mail service . com
The more I type the more I realize how pedantic this is, but we're emphasized in stats to pay extra attention to the conclusions we draw from the data we analyze.
Is anyone else bothered by the claim that there "is a 100% chance that the new version is better than the current one" shown by using bootstrap? Maybe I've just never come across such a use of bootstrap through my encounters with statistics. I know it as a tool for resampling from a population to build up properties of your estimator (mean, variance, what have you) when all you have is a dataset and no clue about the actual distribution. When I saw bootstrap with that probabilistic claim, I thought the author would calculate a bootstrapped (100-x)% confidence interval for both the current and the new weights: and if the intervals didn't overlap with one another then you can claim with (100-x)% certainty that one is better than the other. But the author creates a new statistic that is a function of both datasets; Z_i = 1 if new is better than current on iteration i (on a random subset of data) else 0, and for all N=10000 iterations Z_i = 1. The chance/probabilistic claim made of new being better than current is based on the fact that no variation was seen on Z_i (I'm also kind of skeptical that out of so many iterations with random subsets that each time the new weights were better than the current). I think at most you can say that you simulated subsets of the data and 100% of the time new > current; the current claim leads me to believe there's inference that isn't there.
Maybe I should just ask one of my past stats profs. Open to someone enlightening me.
Blog was posted early enough to have a high likelihood of response if you ping the author with follow up questions
I remember seeing that they had a position open for a software engineering role. If I remember the job description correctly, they've built out their own online store?
I recently saw that you can buy their products through Amazon - I wonder if it was money well spent to roll out their own web store versus using Amazon/Shopify. As a past customer I don't remember seeing any particularly unique feature that made hiring in-house staff for this aspect necessary.
Isn't it equally as likely that in the alternate universe where you pursued Physics that you would have either been unhappy with the realities of a job in the field (maybe too much scut work, lab work, what have you) or even been facing unemployment?
I ask this because I know a lot of people on the other side of the green grass (people who pursued something not as employable as CS for reasons of passion and have displayed regret about not diving into technology for the ubiquity of it in our present day-to-day)
Fresh, organic, local fruits and vegetables are great to have on-hand, so we'd also like to offer a CSA membership to you. Finding a local provider will be up to you, but you can expense the cost of a seasonal or annual CSA share as an employee benefit, up to $1,000/year.
Count that as a perk I've never heard of before.
Cool peek into how a company that works remotely can function successfully. This handbook could be a blueprint for that model - are there any other examples of remote companies publishing their internal handbooks?
Going to local meetups helps but it's probably leaving you unsatisfied due to the low frequency. Some suggestions that worked for me:
- Keep an eye out for local tech companies you want to work for or just like: some might host open houses, or sponsor hackathons. You may hear about this through Meetup.com but not always
- I'm betting Chicago has a Slack dev group. I'm in the Slack dev group for where I am now and where I'm going to move, and it's a good way to stay connected, ask questions, and absorb discussion that you want but aren't getting in your day-to-day
- If you have any interest in volunteering, look for things like Ladies Learning Code and the like going on in your area. Usually the mentors there who want to help young kids are established in the industry. You can go, help younger generations with what you know, with an added benefit of getting to know other mentors, who may help you down the line.
This is a phase in your life that will pass once you start working in the field. I know it may feel hard right now, but hopefully this piece of advice helps (which I found true for me, and I hear from others in the industry): your "outsider"-ness can be spun into a benefit. You see the tech world through different eyes, you come unhinged without biases. And, being fresh and without experience, you will be hungrier, more persistent, and more willing to learn something new than somebody who has roots and comfort zones.Once you pass through this phase and "make it", don't forget to give back when called upon; you will now be "that" person in this network comprised of non-tech people, in a world that is ubiquitous with tech.
To add personal experience to this comment, I've worked at two places before landing such a "dream" job - a < 50 person startup, and a company with businesses around its satellites that employs ~5000 people but I guarantee your average citizen hasn't heard of it. Some former coworkers at that startup were there as their first job, and went on to work for Google/Palantir/themselves. These less sexy companies and startups are waiting for great applicants.
So OK, let's talk about your main question: where to begin to command interviews and ultimately a better salary? The advice here so far has been standard: (a) look outside of one area (b) do side projects and (c) talk to recruiters/network. This is fine advice, but IMO, not the most helpful. Advice like "find your niche" is better... but that is a difficult task on its own, to decide on one path that is by definition obscure.
Again I will draw from personal experience to try and share what I've learned. What worked most for me was to aim for a dream job, and to do things that would lead to building skills that would make me qualified for this dream job. I was in my 3rd year of undergrad - at the time, it was to work in an NBA front office - I was studying stats, and didn't have many interests besides having fun and following basketball. In following this pursuit to its limit, I learned many skills along the way that I didn't have until I decided what I most wanted: web scraping, web development, databases, scripting, algorithm development, computational statistics, explaining statistics to non-technical users, trying to build a business, etc. Side projects, building a network (both local and out of town), and finding my niche (data science + web dev + product skills) resulted from this goal. They would have never happened on my own initiative - I would have been one of many people dreaming of app ideas and side projects to start but never finish. This has a nice benefit that comes for free: you are now different than the rest. Your perspective to solving problems and your experiences will be unique (to what degree, matters based on whatever it is you choose).
The downside of my advice is that it is not a short fix: myself, I am now 3-4 years from when I started this story, as I am soon to graduate from my MSc Stats. But you can accelerate this process, and I can tell you it works: applying to jobs coming out of my undergrad, I only heard from companies that you wouldn't recognize. This year, I got on-sites at Amazon and Capital One before deciding to accept a dream job offer at Shopify. You can do it - and I hope that this is an answer and story that can help you in your search of where to begin your change in approach.
P.S., when you get there, do not underestimate the truth behind how useful resources like CTCI, whiteboarding, etc. are for the interview stage.
In general it's best to compound your current skills and not go in a completely perpendicular direction to where you are going now.
Given that: - you are good in JavaScript - you haven't provided much filter of criteria - you mentioned a curiosity in machine learning - you care about job prospects and want a skill that will stay relevant
Have you considered data visualization? If you become a master at that, you can break into the higher level parts of machine learning/data science that require visualizing results to end-users/interested stakeholders. I'm good enough with D3.js to understand examples and create my own modified graphs, but I wish I had the skills to recreate all of the cool visuals you can see in their gallery.
In my city's (Vancouver) Slack chat, a lot of the most knowledgable participants in data science discussions are physicists (and they're proud of the fact that they're physicists). Check out the Director of Data Science at Unbounce, who published papers and worked as a postdoc as a physicist before starting in industry data science at PlentyOfFish. Worst case scenario if you find yourself pigeonholed, find a home in Vancouver with like-minded people.
I'd say finish your PhD, skip the AI PhD and go for your ultimate goal ASAP!
I didn't know anything about programming until university - I took the courses CS majors had to take in my stats degree until the end of 2nd year, and I definitely wasn't "passionate" about it. Actually, I was quite convinced I didn't want programming to be in my career whatsoever. But after my first co-op term in a start-up where I got to see what actually could be done with a team of people who knew how to code, coupled with 3rd year classes being more interesting and relevant than the fundamentals, I gained my passion. I now run a SaaS that combines programming, statistics, and other passions.
If I read your article after 2nd year while applying for my first jobs and taken this advice, I would have said "screw it, life's too short" and not be in the situation now where so many more doors are open compared to my classmates. I'd be on track for pigeon holing myself into boring stats jobs that need SAS certifications, with none of the skills I have now for a career in modern data analysis in the tech industry.
Side note, I hate reading about developers who lament about the career trajectory compared to being a doctor/lawyer. Most good developers are smart enough to genuinely believe that being a doctor would have been attainable if you just switched another lever earlier in life. I think this is a valid regret if you had actually always wanted to dedicate your life to legally/medically advising people, but you chose programming for the money. But for almost all of these developers, the decision to choose their career wasn't 100% about money and being a doctor/lawyer was never a serious consideration past wishful thinking. You're just viewing the grass as greener on the other side without considering the cons and consequences of actually being a doctor/lawyer, and that type of negative mentality is not healthy.
https://github.com/nasa/api-docs/issues/63
I sent an e-mail to their Contact Us mailbox with no reply. I'm kind of hoping someone who works there sees this, because getting an image larger than the default size would be really cool.
Think about it this way: in your case, you have it easy, in that you have the skills to be doing what it is you want to do. I have plenty of non technical friends that want to make an app, but at the moment they're not capable. You're equipped to achieve your goals, so harness that internal motivation and act on it. Write instead of reading. Be a social media presence instead of following social media.
>> Honestly i think i'll only be contempt when i cut off everything non work related from my life to be more productive
FWIW I've had those thoughts, and it was a factor in my decision to leave home where I was comfortable with great friends. IME I am more productive as a whole because a big chunk of social time has gone into work time but I feel like I do less work per hour, if that makes sense. Everyone is different and I think you owe it to yourself to find that out (either you end up truly content or you realize what is important in your life, both of which are great destinations to find yourself in)