gordonzhu

Joined 15 years ago

Karma
284
Submissions
57
Member since
May 2
founder @ watchandcode.com
View on Hacker News

Recent submissions

Comment · 11 months ago
Comment · 1 year ago
I was going to say this as well. If you haven't done competitive interviews, it's easy to underestimate how much prep / skill is required.
Comment · 2 years ago
I've been making algorithms videos that highlight how one could discover various solutions from first principles.

Example: https://youtu.be/54yUPn3M0ds?si=IcKpUW8NO1rqiO4S

I find it really annoying when people just present fully-formed solutions. In my opinion, this misses the whole point of problem-solving.

Comment · 2 years ago
Comment · 10 years ago
Did you try reading the ui-router docs?

https://github.com/angular-ui/ui-router/blob/master/README.m...

The "Nested States & Views" section of the README links to a full working demo on Plunker that does exactly what you want:

http://plnkr.co/edit/u18KQc?p=preview

Comment · 10 years ago
Thanks for the perspective.

This is why I encourage all developers to take some time to teach new people. The "everyone knows this obviously" attitude goes away very quickly if you start doing this.

The aim of the video was to make it accessible to just about everybody. So if you know this stuff you can watch the first minute and stop the video and get value out of it. On the other hand, if you're a beginner and you just did Codecademy, you can watch it through and follow it too.

Comment · 10 years ago
Nowhere did I tell people to write an entire app in the style of hide and vote like you're implying.

In my comparisons I mention a lot of choices people might make, like Angular vs. Ember vs. React that are ultimately meaningless to the success of your product. I think this is what's resonating with a lot of people.

Comment · 10 years ago
[I made the video]

I don't think this is ironic at all. When I mentioned "framework of the week hype" in my initial comment (https://news.ycombinator.com/item?id=11308043), I was thinking specifically about how people are handling the transition from Angular 1 to 2. I am in no way advocating using plain JavaScript to build your app. I even mentioned in the video that I rarely work with plain JavaScript.

There's a lot of distraction around Angular 2 for both existing and new developers, when it's pretty clear to me that Angular 1.9.x will pretty much look like Angular 2. If you read the release notes, this is very clear. They said the the primary theme for the 1.5 release was improving the upgrade path to Angular 2.

http://angularjs.blogspot.com/2016/02/angular-150-ennoblemen...

What this means is that keeping up with the Angular 1 release cycle will gradually transition you to Angular 2. But everyone in the community seems to think this is boring and wants to blow up their apps and go to Angular 2 right away.

This is the kind of thinking that I wish we'd see less of. Rushing to 2 when it's still in beta makes no sense from a business perspective. It only makes sense from a "I like to tinker with the new thing and try new stuff because it's fun" perspective. Some people will say it's a performance issue (since Angular 2 is better in that respect), but for the vast majority of apps that want to upgrade to 2 now, the improvements won't be noticeable.

Comment · 10 years ago
When you try to vote it will ask you to log in.
Comment · 10 years ago
YES! totally agree

For a subset of us, framework authors, open source contributors, etc. It's very useful to keep up to date on the latest trends.

For example, the Angular team has borrowed techniques from React. It helps for them to keep up with things.

For people like me though, let's be honest. I don't need to do the latest thing.

Comment · 10 years ago
The video mentions this was a dummy account created just for this video.
Comment · 10 years ago
Without JS, return false from the vote function wouldn't happen, so I guess clicking upvote would follow node.href, which would send the vote to the server. It would work anyway, there would just be a redirect that would trigger a page refresh. Pretty cool. Just tried it out and confirmed.
Comment · 10 years ago
What's most fascinating to me about this isn't the simplicity, it's that this code has lived for so long with almost no changes.

It's a great counter-example to all the recent articles about JavaScript fatigue. It's good for us to see real examples of sites that aren't caught up in the framework of the week hype.

At the end of the day we're trying to make stuff that works. ES5 vs ES6, React vs Angular vs. Ember vs. Aurelia, Angular 1 vs Angular 2, even server rendered templates vs. single page apps - it all matters a lot less than we think.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton