Email is one of the most critical communication channels for Zendesk. Our system sends and receives millions of emails a day and our customers rely on us to keep the processing times fast and maintain high outbound delivery rates. The email team is a core product group that does platform, operational, and feature work.
About you:
* You are curious and love solving difficult problems
* You are mature, empathetic, and have strong communication skills
* Colleagues describe your code as beautifully clean, efficient, and maintainable
* You have deep experience with at least one dynamic language, preferably Ruby
* You know your way around relational and key-value datastores
* You have experience working on large-scale, business-critical systems
Some nice-to-haves:
* You have prior experience working on the front-end (React/Redux an even greater nice-to-have)
* You have ops experience and have worked with Docker and K8s
* You are familiar with email standards (and how they’re broken)
* You understand or have worked with SPF, DKIM & DMARC
* You have a Bachelor's (and/or graduate) degree in Computer Science or related
His site definitely lacks style but I would argue the design is from that era as well. To be fair, I doubt he designed the look and feel of his site - and the truth is most great designers tend to have crappy sites because they are busy with real work and dont need to market themselves that heavily. I would guess he is probably in that boat, he doesnt really care about his web site because he has much more important things to do.
You have to remember that Tufte's area of specialty is in the area of visualizing quantitative information. He's not a designer (although he is a sculptor, apparently) or GUI guru even if he has opinions on them.
Clearly a "dated" design isn't enough to stop you from visiting a site. Hacker News definitely has a dated feel too.
Does it? I think it's the wave of the future. Or at least I hope it is. It's as close to pure content and zero chrome as I've seen anywhere. Tufte's site may look old, but it's fairly information-dense, and the comment system is the best I've seen anywhere.
Tufte's site is s piece of crap, completely ridiculous. Criticizing websites is easy, making websites is hard. You're not an expert in user interface design if you haven't done user interface design.
Sure, but just because he hasn't designed an interface doesn't invalidate his opinion. His opinions are mostly from the perspective of his field, which in some ways influence user interface design.
Many user interfaces use elements (he did invent sparklines) and principles he has talked about in his books.
I mean seriously, if Joe User criticizes a user interface is he wrong because he hasn't designed an interface before?
The difference between an interface designer and a user is:
1. The designer knows many opinions (and due to being exposed to an avalanche of user feedback over the years you really see interfaces in a panopticum). But you never get enough. It's like a drug.
2. The user only knows his opinion. Every user opinion is important--to the designer.
Tufte is just an intelligent eloquent user. His interface design competence is as weak as his photography.
Without working in the field you don't get this perspective on interfaces. Tufte has an intelligent riff, but it's always the same professoral top-down "it-has-to-be-so-and-so", and sometimes he's just plain subjectively irrelevant.
I am hoping I am not the only one who is confused with his website - how to differentiate where the article ends and where comments begin. Also took a small while to figure out how to access his book list.
The comments are an integral part of the article, since his responses to them are valuable additions to the article text. Also his commenters are very well behaved.
how would this method remove the slew of security vulnerabilities and other development issues?
there's nothing wrong with green field dev. especially in this case. fairly sure slapping on some 'federation functions' would result in a hell of a mess.
not so sure about that. If you, for example, build a google buzz interface to the facebook backend, you can take advantage of the federated open stack that's being backed big time by google itself, as well as the Mozilla project (ie Salmon protocol, etc)
I've really enjoyed this series, even with the fear of it being left unfinished. Martin's characters remind me of the characters of Glen Cook's writing - also some kick-ass dark fantasy. Check out his Dread Empire series: http://www.amazon.com/Dread-Empire-Glen-Cook/lm/R1423C8TEEUL...
I'd say Chris Wanstrath (GitHub cofounder, http://defunkt.github.com/projects.html) is when it comes to hacking on awesome OSS projects. Rip, hurl, some cool emacs scripts, hub, repl, and plenty more.
I don't know Mr. Wanstrath specifically, but it really isn't about hacking awesome OSS projects. It's about feel and attitude. _why was footloose, insane, and absolutely fun.
Yeah, I know. Chris is a lot more sane and doesn't have quite as much of a "fun" attitude, but he has a pretty cool attitude.
I strongly recommend reading his keynote from railsconf 09. The first half is him totally mocking the whole "rock star/ninja" idea: https://gist.github.com/0a2655aed6a26fa15a02
Email is one of the most critical communication channels for Zendesk. Our system sends and receives millions of emails a day and our customers rely on us to keep the processing times fast and maintain high outbound delivery rates. The email team is a core product group that does platform, operational, and feature work.
About you:
* You are curious and love solving difficult problems
* You are mature, empathetic, and have strong communication skills
* Colleagues describe your code as beautifully clean, efficient, and maintainable
* You have deep experience with at least one dynamic language, preferably Ruby
* You know your way around relational and key-value datastores
* You have experience working on large-scale, business-critical systems
Some nice-to-haves:
* You have prior experience working on the front-end (React/Redux an even greater nice-to-have)
* You have ops experience and have worked with Docker and K8s
* You are familiar with email standards (and how they’re broken)
* You understand or have worked with SPF, DKIM & DMARC
* You have a Bachelor's (and/or graduate) degree in Computer Science or related