HN user

hcatlin

130 karma
Posts6
Comments23
View on HN

I'm sure this happens, yes. But, that's not what's going on here, IMHO.

Asking a person to traverse and modify a linked-list (a very common problem) or to implement a B-tree are not 'tech outside their job'

Most of these interviews are more like math problems than anything a practical developer would encounter.

Shit, if these interviews were "What do you think of node?" or "What is Go's concurrency model?" I think experienced people would do fine.

When I was first releasing Haml, I remember that Ezra piped up and encouraged me. Actually, thanks to the Internets, it's still there https://groups.google.com/d/msg/rubyonrails-talk/UqYlo_N59zo...

Seeing someone as brilliant as Ezra saying he liked my project (Haml was the first thing I ever released) really encouraged me to continue on in OSS development. And, of course, we added iterators to Haml shortly after Ezra suggested it.

Also, Ezra was super helpful when we built m.wikipedia.org using Merb... helping me get everything set up so that we could scale that project to 2 billion pages a month through the three dinky machines I had!

I'm totally surprised and gutted to hear that he's passed. :(

If it's "for teams", then users seems like a better option. You wouldn't want to punish usage. Remember, you are creating value and you want to make sure that the user gets as much value as possible... and that's by sharing more often, typically. And, as the user base within a company grows (hopefully), the price should go up. This stuff is always hard to figure out and I don't think most companies are always 100% happy with how they are charging, but if you are a team-based app where you can easily measure by employees using it, then user is probably the clear winner, even with the little information you've given.

If they are promoted to CEO, then... yes. Hence why we were building apps for it knowing full-well that he was a homophobic CTO. CEO is a whole other level, and was our personal line.

This reads like "I don't like big cities" which is totally fair, but not a general comparison. To each their own. Dirty, loud, expensive: It's a big city! I personally love big cities. I grew up in the suburbs, but have chosen to spend my adult life in Toronto, NYC, London, and SF. I love the kinetic motion, the bars, the rowdiness, the closeness of social classes, the camaraderie of being 'miserable'. I love it!

But, I also see how someone who only moved here for a tech job and to be financially comfortable, who previously lived in a very middle-class suburban area, wouldn't be totally thrilled. Fair enough! Lots of good jobs in lots of decent places.

I do want to throw in one small defense item in the middle of SF hating. I didn't move here because of the tech stuff (which I am a part of) or because of the weather. I moved here for the crazy, wild, weird city that SF is without technology. For the hippies, the dropouts, the drag queens, the commies, the environmentalists, the capitalists, the techies, the artists, ... the great mashup of people that make up SF as a big and wild city.

Before anyone moves to SF, they should read "Tales of the City" by Armistead Maupin. If reading that doesn't make you want to immediately move to SF, then you'd probably do better in some other city with a decent tech scene. Or, as another reader pointed out, you'd probably be happier in the Valley if you are looking for a more NC-feel.

PS: the homeless problems being right next to the rich reminds me of the Settlement Movement of the early 20th century. check it out: https://en.wikipedia.org/wiki/Settlement_movement

Good question. I've gotten conflicting legal advice. Some say I need full signed contributor agreements for everything, no matter the license, and some say that's not needed at all. I opted for something in-between. Just a notice that could cover our ass in the future. Several big companies are working on submitting code, and so licensing there can get tricky... hence, just go overkill and never worry about it. ;)

So, when big companies like Linkedin generate their Sass projects, it can take hours on a single machine. Tons of programmers all working in Sass.

At Moovweb, some of our customer's projects can take 30 seconds just for the Sass to compile for fairly straightforward sites.

Wow, didn't expect to see this at the top of HN. Thanks kudo for promoting the project!

Aaron Leung and I have been working on this for a while. I'm the original creator of Sass and Aaron is a badass computer linguist. Hoping to announce some big new features around the end of the year.

Official site is at: http://libsass.org Or, follow us on Twitter for more updates: @hcatlin & @akhleung

You and I might disagree on tax policy... that's fine! We might disagree on flavors of ice cream too! We're still fine. But, when you say that I have no right to call my husband my husband. And the very idea that I have a loving relationship with him that the government might recognize and treat equally with a same-sex couple. That very idea prompts you to go google for "nom", then find the donation page, you then have to go get your wallet, you then have to fill out the form on the site, then you type in the credit card number (check it twice!), you then click donate. All of that action was precipitated by the very thought of me and my husband being married. Remember, Prop 8 happened after gay marriage was legal in California. I'm far less offended by Westboro, because they have no concept of what they are doing. They function in a crazy world that is separate from ours. To know that a fellow language inventor has such feeling about me... that is hard to describe... and is different than a normal political disagreeance.

I'm proud to say I've done all of these. I think the "drink with co-workers" is a super-good point and I wish more people were more honest about it!