I was interning at a small startup and made some financial models in Excel (using functions like index and match together).
At the time, I told a programmer at the company that I wanted to learn programming. He looked at my work and told me that I was already doing it. I didn't believe him because I didn't think it was "real coding". I thought he was just being nice.
Yes - This book alongside one on AJAX (oh the days of ready state). I still had databases named mismatch_<x> up until about 2014 IIRC!
The book was a perfect example of frictionless starting to code, jumping over hurdles, skipping wholistic education (e.g. all column types/more than select, update, insert in MySQL) for getting something that worked simply and linearly.
And funny examples that stuck in memory (decades later as it turns out..)... like a dating app that matches by opposites between "opposites attract".
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.
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.
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.
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.
https://www.nasdaq.com/articles/warren-buffett-hosts-15-whar...
reply