277 karma · joined August 17, 2011
also, any criticism of a woman in tech is automatically labelled "misogynist" by the internet hate machine known as Tumblr (which Yahoo owns), so where she might get more criticism, people are giving her a free pass.
So really, the problem _is_ solved :) It's just that the threshold and effective doses for cannabis mean that mg-specific dosing really isn't that useful.
The last I heard, they basically downloaded the android OS, and re-wrote all of the system UI framework components. Of course, this meant that most android apps broke because they failed to make all of the options functional, so they spent somewhere around twice the time fixing issues as they did writing them.
1. Needs to have great design 2. Needs to be rock-solid in terms of stability 3. Needs to be snappy to use 4. Needs to be able to handle a Reddit traffic swarm 5. Needs to have individualization and customization 6. Needs to play nicely on computers, tablets, and phones
The person (or people, more likely) who is good at all of this just isn't available at rates the companies want to pay. This is the important distinction. Hiring somebody for 100k/yr is pretty much the minimum ante for a good developer in a tech city. But these "entrepreneurs" and "founders" think that is too much money, and instead claim there's a shortage.
In reality, if you're competing for top talent, 150k/yr should be your ante, and be prepared to go well into the 200s. This shouldn't be a surprise. To get even average talent from a consulting/contracting company, you're paying about 125/hr (of which 60-70 goes to the developer). That's 250k/yr. So why are companies freaking out at paying over 100k/yr for a full-time person who they can invest in? Hell, cut out the contractors and pay your people 200k/yr, and watch the good people come talk to you.
This is what Amazon and the like are doing now. I'm hearing 22 year old kids who haven't coed a line of code in a professional capacity, getting offers of 120k/yr with a 20k signing bonus. Netflix pays a significant chunk of its engineers over 200k.
The only real problem is that it's getting more expensive to do business in a tech world. But compare the skill sets that used to draw 100k/yr, and the skill sets now required to get 145k/yr (100k/yr in 1998 dollars = 144k in 2014 dollars). Before, you could just know HTML and some shell scripting. Now, you need to know multiple frameworks, how to deal with scalability, multiple data stores, "full stack," etc.
If anything, the good talent in this industry is still dramatically under-paid. A common metric is that the company should make from you about 7x your salary to justify your position. So if a company is making 2.1 million, you should be getting 300k. But we all know that's not what's happening. Instead, our wages are being capped and forced down due to illegal collusion between the top tech employers.
This all comes down to the people who own the businesses wanting to treat tech people as interchangeable cogs, despite all the evidence to the contrary.
If your point is salient, you won't have to insult the very people you're trying to convince.
Since you're doing research, I'm sure you've seen the Lytro cameras. Maybe if they manage to get that technology into phones, it could really change the world. Samsung is already doing some stuff like recording photos several ms before/after the button was pressed, so you can do minor time-stream corrections. It's not long before DOF corrections through hardware or software comes along.
Currently, we estimate that your browser has a fingerprint that conveys at least 22.16 bits of identifying information.
Well, shit. I'm a snowflake.
- We all believe we're above average in our field, and unions would hold us back.
- We all know people who have skated by on incompetence, and wouldn't want a union to protect their jobs.
- Our field moves quickly, and we don't want a union that would hamper our ability to make quick moves.
- Union is a dirty word, especially when the mind disease of libertarianism is more prevalent among tech workers.
I think the easier way to solve this is for IT/computer workers to stop being paid salaries, and get paid hourly. If it weren't for a special exemption from congress that was passed in the 90s, we would be paid hourly as a matter of law. I know I've been treated MUCH better since I switched to consulting.
Employers value your time when they have to pay for those extra 2 hours of meetings each day, when they have you work a Saturday, or stay a couple hours late to push to the finish line. In addition, things like software efficiency upgrades where I can show 10 hour savings for 3 hours of cost are suddenly on the table, where on a salary you're not a "team player" if don't just put in the extra hours for free to save the company some bucks.
Why spend so long worrying about your Hammer of choice when they are all effectively glorified Rocks?
that said, netflix seems to have solved the IO issue with ec2. I'd be curious to know more about their findings.
With StringBuilder: 2.61 seconds With String Concat: 3.03 seconds
I have to assume there's another loop running these, but I'm not seeing it. Each dictionary has 1 million elements at the end.
I just implemented it inside a junit test, here's the class:
Turns out java performance isn't bad at all.
EDIT:
I'm a dumbass, was converting nanos to full seconds. Post has been edited.