407 karma · joined November 29, 2008
Dublin, Ireland.
Email: phil at domain below
www.brassy.net
http://blip.tv/carolinacon/logstash-open-source-log-and-even...
http://homepage.eircom.net/~nopatec/
Dreamweaver special :)
still can't find the geocities site I had in 1997 though...damn
There's nothing like the talent in SF and we're currently saturated with Google/Facebook/Amazon/LinkedIn/Zynga sucking up a significant chunk of the best talent here and also bringing people from the UK and mainland Europe.
This would be a significant challenge for anyone looking to push the bleeding edge of technology. There aren't many brilliant young 20 or 30 somethings willing to work in a startup environment sacrificing pay for equity in the same way as there is in SF.
Honestly, I'd see available talent as a significant struggle depending on how you're scaling and what kind of people you would need.
"We must be mindful of the precedents set" "Avoid collateral damage" "Promote innovation over litigation"
None of this is actionable against the legislation in it's current form. What you're doing is interpreting actions based on your own bias and joining the dots in your own mind as to what these things mean. You're not seeing the other side, which is frequently the problems with these debates.
Bottom line - I think his heart is in the right place, I just don't see these points as being particularly poignant given the context in which they are being seen from the other side of the debate.
It's not isolated to Mercedes either
I managed to convince them to hire me, but for a mediocre salary (for me, I was still earning in some cases twice what my fellow graduate friends were) and spent 14 months trying to get that raised (pointless at the time, but I was naive, needed a job and ultimately I loved the work and the people were cool)
My boss there landed a job with another company running the department and asked me to come on as CTO-of-sorts of the department and I got the money I had wanted, no interview (I met with the CEO) and all the autonomy I had wanted/needed.
I've hired a couple dozen top engineers since then and been part of two acquisitions (as the acquirer) and I can tell you that you don't _really_ know what someone's like until they work. What I'm looking for is character + intelligence. Smart and get things done. Whatever you want to call it. The Get Things Done part is the bit that's so bloody difficult to tell.
I've seen people who I did not expect to be rock stars come in and just kill it. They were never put in a position to succeed before and suddenly they've gotten the ball and they're just running with it. There's one guy in particular I'm thinking of who worked for a BigCo and his technical acumen was good (not brilliant or exceptional, just good). I didn't hire him, but he just got it. He does what it takes to get the job done (and then some) and figures out what he needs along the way. I've had guys with excellent references (some from people I know) come in and do mediocre. I've seen candidates that were brilliant end up being a menace around the office.
Saying that it's unfair that you're not being given a shot is not recognising what is happening at the other side of the table - a complete imprecise science of judging people's ability to be brilliant (or even good) based on interview scenarios. You need to do things to increase your value and remove as much of the unknown quantity as possible (network, volunteering, meetups, hacker weekends, open source code, portfolios - whatever is relevant to you).
As a startup - I would take a KNOWN quantity each and every time. You are unknown in this situation. If you are good, in the future the tables will be turned and you will be known. The difference is you cannot manufacture these situations easily, no more than you can manufacture who you will marry. Espouse your best qualities, do great work (which isn't just limited to the code you write, servers you maintain, designs you produce etc.) and you will be a known quantity to people in the future.
You sound like you're young (at least job experience wise), not that I'm particularly old - business is people. People are business. Reputation is everything in your circles and if you're good, you'll start to build a rep and that will become extremely valuable and open doors for you.
Many great novelists and authors have mentioned "rewriting" when it comes to their novels and books. "True writing is rewriting", "books are not written, they're rewritten". My experience is that comes with code too.
You write the functionality to do what you want, and then you keep to keep re-writing it to make it beautiful/readable.
This is a completely different scenario though:
* Transferring stuff to linode isn't generally an end in and of itself. There are far fewer use cases for it. At the end fo the day you probably need to get data back out of it.
* The vast majority of cloud hosting and hosting providers in general's bandwidth is outbound. People download from the web. These hosting companies provide a lot of the web's main infrastructure. You're probably looking at a ratio of 20:1 or 30:1 here.
* Linode doesn't pay for uploads and downloads with it's carriers / ISPs. It pays for circuits capable of synchronous upload and download speeds. Using the ratios above, if they, for example, have 300Mbps of traffic outbound, then they have a lot of spare inbound capacity.
* Abuse here is difficult. Downloading movies, music etc. are consumed at home. It's difficult to imagine so many usage scenarios where huge data volumes would be consumed so easily on a linode server without having to be downloaded again. Maybe someone can come up with some creative suggestions here though? :)
* Bandwidth allocation and contention is very different within a hosting providers access network than an ISPs access network. ISP last miles, local DSLAMs, AP's etc. are huge points of contention. Inside the data center, I imagine most hosting providers "last mile" are 100Mb or Gig/E here straight to the servers with gig or 10gig/e uplinks from access switches.
The basic crux really is though, they have shedloads of free inbound bandwidth and why not give it away for another USP.
I see Jeff talking more about "development" here - coders get better at coding by writing and reading more code. But there's no point being good at putting code on the screen if it doesn't do the thing your end users need to do.
There's a lot of transparency in a lot of contracts / arrangements. A lot of information ends up on public record. Buy a house, get married, poor credit rating etc. Most of this information is accessible in some form and these companies are simply aggregating it.
This information is generally much more difficult to collect in other countries (with my own personal experience being in a few European countries), if it's even accessible at all.
I'm sure there's exceptions but this does seem like a very American problem.