stevekwan

7 ms·

1.
by stevekwan 12y ago
Although there is some solid advice and insight in here, there's also a lot of really questionable stuff. Following a lot of this advice, particularly around self-promotion and navigating within a company, could be very limiting in te
2.
by stevekwan 14y ago
Yes...my apologies, should have been clearer about this.
3.
Ask HN: Are you a generalist or specialist?
1 points by stevekwan 14y ago|4 comments
4.
by stevekwan 14y ago
Good catch. I accidentally JavaScript. It's been fixed. Thanks!
5.
by stevekwan 14y ago
I know...but there's actually a real gem hidden in there! The whole agile estimation thing is something that seems to trip people up all the time. If you were to blow this out into an article with specific suggestions for improving proces
6.
by stevekwan 14y ago
I've gone through and removed some of the bristly "flavour" language. If you want to scan through it again and look for more offenders I'd be greatly appreciative.
7.
by stevekwan 14y ago
I hear you completely. But understand that my intent here was not to write idiomatic code, it was to write code that an outsider to JavaScript would understand. I worry that the {} syntax, while simple/elegant/preferred, may be somewhat l
8.
by stevekwan 14y ago
I'm not disagreeing with you in any way, shape or form. JavaScript is an AWESOME language for both productivity and results. But I think we're doing ourselves a disservice if we assume that anyone jumping right into the language is going
9.
by stevekwan 14y ago
"This is totally stupid and insane and only idiots will do it." I hear your point, but this kind of language is no way to get it across.
10.
by stevekwan 14y ago
As a UX guy, the prevalence of the Pinterest layout has made me cringe a bit. But I think it definitely has a place, given a few caveats: 1) As others have said, if your site's purpose is more discoverability than navigability, then this l
11.
by stevekwan 14y ago
Most important thing is to expand your connections. You can only rely on appearing in search so much. Bear in mind that whenever you do something to LinkedIn, it gets blasted out to all your contacts in their activity feed. So the more c
12.
by stevekwan 14y ago
I think if your interview style is very Q&A oriented, or if you are burying candidates under coding challenges, you are definitely in need of some interview training. Sadly, a lot of people choose to interview this way for one reason o
13.
by stevekwan 14y ago
I'm a HUGE fan of LinkedIn. You get what you put into it, though. For me, LinkedIn is my online resume - even moreso than GitHub, because the nature of my work prevents me from contributing to open source. I also definitely care who views
14.
by stevekwan 14y ago
I understand where the article is coming from, but I don't agree with this as a blanket statement. There are way too many counterexamples of big companies doing incredible things.
15.
by stevekwan 14y ago
It is kind of funny how responsive design has become perceived as a silver bullet for web design. There are still situations where a traditional m.domain.com approach is better. Responsive is great if your site is mainly concerned with ser
16.
by stevekwan 14y ago
I love JavaScript, but there's no denying that large aspects of the language are somewhat ill-conceived. Crockford himself says this. Once you know which pitfalls to avoid it's possible to write some really elegant code, but the mere prese
17.
by stevekwan 14y ago
I did not put that there because it was the best syntax. :) I put it there because I felt it was most likely to be understood by someone new to the language. I assume you're implying I should have used {}?
18.
by stevekwan 14y ago
I tried not to get too deep into the explanations because I really, really wanted to keep this to a short list that could be scanned and grokked. Truth be told, if someone wants an explanation of some of JS's weirdness, there are far better
19.
by stevekwan 14y ago
I really didn't want to write that. Ignorance is never really a good solution. :) But from my experience, someone who is coming into JS for the first time is probably not setting up a complicated object hierarchy - they're probably just t
20.
by stevekwan 14y ago
My apologies if I came across this way. The intent was not to whine about var or function declaration, but rather to provide clear direction about a standardized "okay" way of doing these things without causing yourself undue headaches. So
21.
by stevekwan 14y ago
My only worry is how long it'll take for ES6 to get adopted. It's one thing to write a spec and implement it into the compiler yourself...it's another thing to write a spec and wait for several key browsers to implement it.
22.
by stevekwan 14y ago
Could not agree more. There's tons of value in using a standard, even if that standard is getting a bit long in the tooth.
23.
by stevekwan 14y ago
Oh, and one more thing. If you see anything in there that's flat-out WRONG - not just a preference or stylistic choice, but actually WRONG - by all means, shoot me a pull request! That's what it's there for. I see a few of you already hav
24.
by stevekwan 14y ago
Wow, glad to see this is stirring up a lot of discussion. Thanks for all your contributions guys. There are a ton of comments down below with a ton of criticisms and suggestions. I will attempt to summarize and respond to the key ones her
25.
Common JavaScript Gotchas(github.com)
81 points by stevekwan 14y ago|92 comments
26.
For JavaScript beginners: an in-code explanation of constructor and prototype(github.com)
4 points by stevekwan 14y ago|0 comments
27.
by stevekwan 14y ago
Sorry, my bad. The URL to the actual Mozilla ticket is here: https://bugzilla.mozilla.org/show_bug.cgi?id=775763
28.
Firefox 14 intentionally breaks support for CSS transform skew()(reddit.com)
1 points by stevekwan 14y ago|1 comments