I tried out Stitch Fix expecting to return everything, wiling to eat the $20 fee. I have to say I am surprised with how well they have done, I have ended up keeping a fair amount of the stuff. Most impressive is how they can find pants that fit me.
Of course I've been wondering the entire time how their data operation works behind the scenes, so this post is really enlightening, cool graphics too... and only some minor scroll jacking.
ChefSteps is dedicated to putting the kitchen back in the heart of the home. We do that by getting people cooking, and we need your help.
Data Scientist:
You will be part of a small team that works across the entire organization to help coworkers use data effectively. You’ll use data to help us make decisions about what kind of content we should make, whom we should market to, what our next product should be, and what features we need to add to our current products. Note: This role may be combined with the Data Engineer position depending on experience and level of interest.
Data Engineer:
You will work with the data science and software engineering teams to empower your coworkers by giving them reliable access to data. You’ll help us make key decisions about infrastructure and capacity planning, and you’ll be responsible for ensuring that we can store data at scale with testable integrity. This role may also include other backend and operational responsibilities, depending on experience and level of interest
WebRTC seems like a really cool opportunity to rethink certain kinds of services. Video is an obvious candidate, I've also seen a bittorrent client that uses WebRTC. What are other interesting peer to peer applications that WebRTC could enable?
I also saw that triangle shaped plot and had the same thought. I read a great paper about this recently [0] with some of the same examples as the link in the parent, but going a little further in depth.
I originally got on this topic when reading Bayesian Methods for Hackers [1]. I am still hunting for a good method to correct/compensate for this when I am doing these types of comparisons in my own work.
I was using Baobab in production at my last job and really enjoyed it, part of the reason it went so well was Christian Alfoni's blog posts and contributions to the project.
Boring has its place, and certainly can add a lot of value to a project. If everyones goals are aligned in creating a rock solid web site or app that never needs refactoring and has 100% legacy browser support, then boring is great.
Some of us are attracted to new technologies, and appreciate learning the lessons of what advantages or disadvantages come from building the same type of site or app with a different framework or technology stack. Especially those of us who aren't yet mature enough to write our own apps without the guidance of frameworks, and have not had a chance to work with all of the different possible approaches.
I think a healthy balance can be struck between the type of stability gained from the 'boring' approach, and the types of gains that can be realized from newer 'non-boring' technologies. Sometimes supporting IE6 is not a concern at all, and learning new language features from ES6 is an attractive proposition.
If doing front-end development were boring, I don't think I'd be as interested in doing it.
I earned a PhD doing biology research with automated microscopy and high throughput data analysis. I love visualization and building web apps that enable communication and collaboration.
This is a good list of things to avoid when presenting. I'd like to add another that I've commonly seen:
Don't give up control of the presentation until it is time for questions.
Sometimes people will butt in with questions, and you should answer them quickly and minimally. I've often seen this kind of thing fluster a presenter, and sometimes the presenter will say "okay, is there anything else? any other questions? " as if to invite more interruptions. This is a mistake, you should quickly address the person who interrupted and then get back into your flow without allowing others the chance to also interrupt.
Another one, that maybe only I am bothered by, is don't start every single answer with "That's a good question..."
For those interested in a practical method to cook steak with a perfect char + medium rare inside (no lava required), check out immersion cooking (aka sous vide). You can cook a steak edge to edge to exactly your desired doneness, cool it down, then char the outside with a hot skillet or open flame.
Sitting in my fluorescent lit white walled office, about to pump out some code for the day, this article put a smile on my face and made me think about different options for life some time down the road aside from programming.
The article was well written, wasn't judgemental, and provided some lightness to my day and to others.
This article does not actually address the cause and effect relationship between equity and employee motivation. From the title and introductory paragraph, it seems as though the author will talk about what actually motivates employees, and how common perception of employee motivation is a myth.
However, the article simply does some math to show that equity SHOULDN'T motivate employees, and never talks about whether or not it DOES motivate employees. Even if the numbers don't work out in a developer's favor, that doesn't necessarily mean they do the calculations up front and and totally rationally.
People still buy lottery tickets despite the poor odds, and developers will continue to be motivated by equity even if it is irrational.
Very cool, and interesting to see the results. I immediately looked for a 'trends' feature to see how cities rank change over time, or maybe this could be plotted?
I am in Seattle, which does not have the thriving biotech scene of the bay area or Boston, but thankfully the cost of living is significantly lower than either.
I had essentially zero chance of landing a biotech position, similarly because my niche was not in demand by any local company. Even the positions I did see were not very desirable and the competition from other PhDs and postdocs was fierce.
I was lucky to have some extra time toward the end of grad school to pick up some coding skills. The labor market for software developers is ridiculous in Seattle, and it took me under 2 weeks to find a full time position. I considered bootcamps also, but decided to give it a shot trying to get hired with just my existing experience. The though of starting a bootcamp where my 6 years of research experience was all for naught was pretty depressing, so I really feel for your sister. I have another PhD friend who is in the exact same boat.
My conclusion was to not fight the tide of the labor market. I think in the future biotech will be really profitable and there will be a lot more jobs, but right now all of the jobs are in software, at least around here.
I was a Life Sciences PhD student for 6 years and started a postdoc, but then jumped ship and became a software developer for a non-science company. My salary is more than 2x as high as what I was making as a postdoc, and 3x greater than what I had been living on as a grad student. The salary thing is huge. From my point of view, research science was becoming a luxury/hobby profession of people whose spouses make a lot of money or who are independently wealthy.
The only two solutions I see are either funding for NIH and basic sciences drastically increases (my preferred solution), or there is some breakthrough which makes biotech and life sciences industry more profitable and able to hire all the entry level PhDs.
Notice how the engineering and physics PhDs make up only a small fraction of the donut chart? That's because those folks graduate with skills that are desirable to industry because they can translate into profit. The biotech industry does not need smart and inexperienced idea people. The biotech industry prefers very senior level scientists with proven track records of profitability, and worker drones who have bachelors or masters degrees who are not on the scientist track.
has anybody actually used Fuse for a real product? we could not find anyone to talk with about it and that was a deal breaker