bitcrusher

Excuse me, but I believe you are very much mistaken. Those places are as much or MORE expensive than most places on the peninsula... In fact, the reality is that prices have almost normalized across all of the cities from SF to Los Gatos.

It is becoming increasingly hostile to any new arrivals as the barrier of entry is skyrocketing to the point of being out of reach even for "rich" people.

*This observation was used to pursue hypothermia in other causes of anoxic injury, which is clinically used today.

With pretty astounding results, honestly. My son was born having been without oxygen for at least 6-9 minutes. He was immediately put on a "cold blanket" with his temperature maintained at 92 (F) for 72 hours to prevent brain damage... He has since made a complete recovery with no physical neurological issues present.

This article might be complete bunk, but the hypothermia treatment protocols definitely are NOT.

Meta Note: If you don't read Oona's blog regularly, you're really missing out on some great stuff. Even if you have little interest in sound processing, her discovery processes are more than worth the price of admission.

Here is just one great example of many:

http://www.windytan.com/2013/11/decoding-radio-controlled-bu...

I don't mean to belittle you either, but this is hogwash. Of course a Rails or Node developer wouldn't be able to write Postgres without ramp-up time...

Maybe what you're saying is that the ramp-up time would be LONGER for someone starting from Rails or Node only knowledge to being an infrastructure developer?

Any highly sophisticated application ( Postgres, LLVM, etc ) requires some advanced levels of domain knowledge but they aren't impenetrable fortresses of skill that no mere mortals can access.

I think, somewhere along the way, a lot of developers started believing this fantasy that they were the keepers of secret knowledge that only a few select individuals knew... GOOG and MSFT perpetuated that with esoteric interviewing processes and cult-of-personality style branding. The truth is... the fundamentals of CS aren't terribly difficult nor are they even terribly exciting. You can absolutely learn them on your own or even as you go.

or even:

[Esc] :x

to save and exit.

This is the same alarmist outcry that happened in the 90s... "India has a billion people who are educated and cheaper! Outsourcing will kill all the tech jobs!"

I think the thing that folks keep missing is that technology isn't a zero sum game. So what if there are a shitload of people in the east doing programming cheaper? 9/10 of the 'type' of programming they're doing is grunt work that no one really wants to do anyway.

Will some people feel the 'crunch' from this? probably, in the short term. But technical acumen doesn't sit still. We're not all languishing on our laurels with technology from the 90s while the Chinese are gearing up for total war.

A much BIGGER problem, IMO, is our social policies tending towards overt xenophobia. THAT is what will kill the US and the Western European countries if we don't get off of this nationalist bandwagon that we find ourselves on.

And so the debate rages on...

There are two sides to this, illustrated by the parent post and you post. Ultimately, it comes down to style preference and his little actual tangible TECHNICAL benefit. The benefits to team process/organization can definitely be argued for ( or even against ) but, that is why the debate will rage on for eternity, IMO.

Depends on the company; My current employer added 2 times my annual in RSUs.

Yes, it is insane. It's a pressure cooker, which induces personality traits in folks that are undesirable at best. People figure out how to game the system, squash the less assertive/aggressive/self selling types and keep fighting for another day.

Amazon has this same problem.

Contrarily, the special snowflake and myopic individualism is what MADE the tech industry. The hubris to say, "I see a better way" or "I can do it better than that person" is how we got here. In point of fact, this entire thing is basically another form of "snowflake individualism".

I am starting to think the giant problem in tech is really attitudes which are dismissive of our differences and our experiences. Tropes about "tech-bros" and "millennials" are rooted in the very same biases that they're railing against.

It's just another face of tribalism.

I think the issue is not to invalidate your specific experience, but to highlight that your experience is pretty atypical and further that your experience should not be the norm. For every person like yourself that had a great experience in this mode, there are 500 people who are having a very BAD experience.

It's fantastic that it worked for you and your team, in that time and space, however, the combination of factors that created that were unique and not easily repeatable. So, in absence of a formula to replicate that, we should instead be working to normalize a baseline that is conducive/comfortable for most folks.

I agree. In a lot of ways, in the areas that I have been exposed to, SV culture IS intellectually bankrupt. It's a sad state of affairs, honestly.

In some sense, I believe this stems from being afraid of 'not knowing'. Especially in the current SV culture, it's really anathema to say, "I don't know". "Not knowing" something is frowned upon, especially as you get deeper into your career (more senior, etc.) and it is really shameful that we have created this atmosphere for ourselves.

Being unafraid to say, "I don't know" is a really powerful skill. Now, for me, being surrounded by people who know more than I do, is actually a win. Now, "I don't know" turns into "Show me". It's an opportunity to learn and to grow.

That's not really true at all. Basho (makers of Riak) have a multi-paxos implementation that is used in Riak. Riak_Ensemble:(https://github.com/basho/riak_ensemble)

I've literally seen the opposite interviewing as distributed computing person, most people ask for a distributed engineer and then want someone to stitch together Hadoop and Spark or how to effectively leverage HDFS. When you start talking about concurrency issues, Lamport clocks, consensus algorithms, etc. their eyes glaze over and they ask how to efficiently rotate an array. Clearly something is broken but I'm not sure it is how we use language.

I think the big problem with the microservice movement is that it is easy to understand but difficult to implement. It reminds me of when OO was new on the block and people designed these really elaborate OO hierarchies only to have them break down over time. Then came "OO SUCKS" because there was a level of experience required to understand what level to take your modeling to.

The same thing is happening with microservices. Engineers are microservcing ALL THE THINGS at such a fine grained level that it becomes a nightmare to maintain, orchestrate and manage. Therefor "microservices suck!".

Most of the time, you can model your domain into a few key areas, say 'customers/security', 'interface' and 'processing'. That's a good 3 service start. You may never need to go beyond that. However, as your needs grow or change, you can start to refine your model based on changing business needs or scale/performance/infrastructure issues.

In my experience it's a completely logical way to design a system and is really no different than making 'libraries' of code all housed under a single master application. The only real difference is the underlying communication infrastructure.

If you're talking about raw performance, I'm afraid you're mistaken. If you're perhaps referring to the 'aesthetics' of the language syntax, that's pretty subjective, in which case you're right for your tastes.

"Android developer talks more trash about iOS.. Film at 11."

yawn

For me, what's maddening is people claiming 'cognitive dissonance' when the Federal Government does the job it is supposed to do, which is make sure 'states rights' don't get out of line with the constitution or the bill of rights. In my experience, the people shouting 'states rights!' are generally the people who are doing something completely hideous ( violations of secular principles, human rights/liberty, etc. ).

I believe, the reason there seems to be a push to do everything at the 'Federal Level' these days is because extremism in political views is really LOUD and the more people are getting into a frenzy by living in communal echo chambers. The more people believe that the 'world is ending RIGHT NOW' the more urgent and forceful the 'solution' becomes.

This is only partially true. You are 'strongly encouraged' to enforce your patent violations, for after a period of years (6) they basically become unenforceable. This is to prevent things like 'patent bombs'.

In practice it doesn't always work this way ( see patent trolls ) but it can be a BIG issue for people looking to enforce their patents.

Here's an interesting example:

http://www.ipwatchdog.com/2010/05/26/estoppel-time-bomb/id=1...

No, that ALSO applies to patents, though the term is actually 6 years rather than the standard 3. Your 'confused' comment is a good example of why the FSF should encourage educating ones-self instead of trying to play semantic games with the english language.

ALL companies are aggressive in litigating against anyone who they feel borrows their ideas via intellectual property laws. It's basically REQUIRED (by those same intellectual property laws) to maintain your 'intellectual property'.

Now, one could argue that there shouldn't be such laws or that they should be shaped differently, but that's a different discussion, in some ways.

Bo Jackson was both an NFL and MLB player.

http://en.wikipedia.org/wiki/Bo_Jackson

Maybe you're right; But something feels a bit out of focus for me, only because they're only 'involved' from the standpoint that they're selling software. If their software was called 'seed' tracker and they didn't mention Marijuana overtly, would it still be an issue?

I get that Stripe can (and should) do business with whomever they choose. This guy's rant aside, I think the fringe business issues surrounding emerging industries are really interesting.

Here's another example: Technically Uber has been operating in a legal grey area for a while (not unlike this software). What if companies like Stripe refused to do business with them because of their quasi-legal business? AirBnB?

From the top of the page:

"There is! For readers not already familiar with first year calculus, this post will be a lot of non-sense."

FWIW, it is a pretty straight forward explanation of 'half-integrals'... which by induction means there are 'half-derivatives'.

You have some interesting points, however Eric Brewer isn't just 'some Google guy discussing CAP'. He actually invented the theorem... It's also known as 'Brewer's Theorem'.

FWIW, CAP is not about NoSQL or the 'NoSQL movement', it's about distributed systems and distributed shared memory, which applies to a whole range of computing problems.

It really depends on where you live. In places like Arizona, this unit could pay for itself in a matter of a few years. Even if it is only used as a load shifter, it could generate great savings during the summer/hot months.

As I understand it, Graal+Truffle is basically the DLR. This has been around since 2008 from Microsoft.

Both IronPython and IronRuby have used this for years.

The "Day 1" comment was specifically pointed at the read-between the lines for Graal, which is basically to create a real IL for Java instead of using the InvokeDynamic semantic that is currently envogue for Scala, Clojure, etc. .NET has had the multi-language one VM paradigm since day one.

Except, in both of the examples you cite, .Net has had those features since day 1 ( more than 13 years now ).

I think it's pretty disingenuous to say those things are hard to measure or even estimate. Java and C# are close enough that you actually CAN measure them in a pretty useful way.

Java has been behind the curve for YEARS as compared to .Net with perhaps the exception of the cross platform aspects and the more permissive licensing.

I think you're mistaken on a couple of points:

- VCs aren't interested in "revenue tomorrow" unless you mean a 10x+ exit multiple. VCs want you you to focus on your product because there's an invisible( and sometimes not so invisible) clock running as soon as you take the investment.

- VCs aren't interested in 5-10 year tails on their investments. Most are looking for an 18mo.-3.yr ROI. If you can prove revenue and 'market traction' they'll extend your runway accordingly, however that's a constantly moving target and generally the types of VCs who are interested in the 'long tail' aren't the same that want to give you money at the infancy of your company.

- There is definitely a big difference between a traditional consultancy and a product focused organization but only in the sense of the 'end goal'. If your entire plan is to bootstrap your company by building a consultancy, it's easy to keep a separation of concerns between the two halves of your organization. Usually the "clash" that you're talking about is when a consultancy based/focused organization decides to build a product, not when a product company decides to do some consultancy.

Developers (in fact, all of technology) are considered cost centers at ALL businesses. There's not an MBA on the planet that wouldn't jettison the entire technology cost-center of their business in a heart-beat if they could figure out how to do it and still achieve their monetary objectives.