Navel gazing is the best way to convince yourself that things are going great and to give you that boost to keep working on the project. At some point you will probably look back at this and think it was nothing to brag about, but it doesn't matter because you're having fun and enjoying the feedback loop between you and your users -- this is a good sign.

Gender identity is actually a quite tricky topic and should be approached carefully. I would discourage anyone from trying to use this library, the real world doesn't fit neatly in your multiple-choice view of gender. For more information, please watch this great talk: http://vimeo.com/61172068.

I can't imagine making a dating site these days: "I'm (name text field), a (sexual identity text field) interested in meeting (sexual identity text field) for the purpose of (dating/friendship/sex/swinging/whatever text field)." Good luck with that business logic. Maybe we do need intelligent agents for this stuff.

I checked how Facebook handles gender the other day and it's still either "Male" or "Female". Strange, because they return gender as a string in API calls.

Came here to say this, thank you.

I like that.

Did you actually read the link before commenting? Honest question.

It's a clever list of aphorisms. None of the qualities you desire are actually defining features of the SA, though.

Who on your team is not a student? who is not a mentor? who should gloat when they are right? who does not understand the most precious parts of the system?

I think your list is less about A Software Architect and more about people who take pride in their work.

I think you're starting to understand my points then.

If you were asking an "honest question", wouldn't you be expecting to get some further information from the answer? I don't see anything.

It just sounds the usual "Did you even read XXX?" rhetorical question. I'm not even against rhetorical questions. It's simply annoying when "honest question" becomes nothing but a emphasizer in the fashion of the common misuse of "literally" or a "justifier" ("I think you're idiot" is out of line but in our world of touchy-feely-ism, "I honestly think you're an idiot" is OK)

Edit: Instead of just "taking a shot" by saying, "did you read the article", I'd suggest saying why you don't think the comment reflects the article. Otherwise, your post says little more than a downvote.

Absolutely. And you lost me from the first point:

"A software architect lives to serve the engineering team -- not the other way around."

This implies the SA is not a member of the engineering team. Or if they are, they're "special" in a way the rest of the team isn't. And that I whole-heartedly disagree with. Most of the other things I expect every member of the team to do, anyway.

So if your point was to say - "Everyone in the dev team needs to be the SA", then yes, you're right. But that's not how it reads.

I agree. Reading through this list, I wonder what we would lose by replacing "software architect" with "lead developer" or even just "really good developer". It seems like the list would retain its meaning, without the potentially muddying effects of a word (architect) that comes loaded with all kinds of preconceptions.

You should tell us what those limitations are :)

The number of bytes in a sprited file can be smaller than the sum of the bytes of each file individually. So the best option might be to inline the sprite :)

so chriseppstein, I would be interested in what you (as the creator of compass), in particular, have to say about which would be better: a "Compass Sprite" ( http://compass-style.org/reference/compass/helpers/sprites/ ) based approach or a compass "inline-image" based approach ( http://compass-style.org/reference/compass/helpers/inline-da... )

edit: oh, so i didn't fully grasp what your comment was saying. are you suggesting that you would use inline-image AND a sprite to put all the images into a sprite AND load that sprite inline with the css?

There is a statistical margin of error. They will need to make many such predictions. Also, the act of predicting an event might cause it to become more or less likely to occur.

Make the prediction, encrypt it with a private key. Release the encrypted prediction with a "do not open till...". Release the public key at a given date. This way the prophecy won't influence the future.

What kind of cryptography do you need to use, in order to avoid the prospect of two different predictions, encrypted with different private keys, resolving to the same encrypted text?

I've never heard of anybody being able to achieve something like that. If you have some examples please share. For all practical purposes I'll say it is not possible. Especially if you are using AES.

Sass uses $ for variables, less uses @. For more differences: https://gist.github.com/674726

The real reason it's for hackers is that it uses Git and the command line to manage it. It may not be "hack-ery" enough for you, but it's certainly not software non-hackers are going to use.

Those damn marketers. Going after that HUGE hacker market again!!!

Funny and deserved an upvote, but in reality I bet hackers are more willing to invest in tools they find good. Still, it wouldn't describe the market size of course, but the worthiness of pursuing it.