OO is when you really love objects, you put objects in objects.
FP is when you really love functions, you put functions in functions.
Of course, if you like both, you can put functions into objects and objects into functions.
232 karma · joined April 25, 2011
FP is when you really love functions, you put functions in functions.
Of course, if you like both, you can put functions into objects and objects into functions.
Broccoli is a build tool and not a task runner. You can use Grunt or Gulp to drive it. Heck, you can use make if you want.
First time users often found there's a steep learning curve to get started. But the effort is well worth it because of its architecture and philosophy. The problem with Grunt and Gulp has always been trying to combine incompatible plugins together. This never happens with Broccoli plugins.
I have found the unicorns like to hand out RSUs like candy.
I would say networking is less about meeting people and more about building a reputation. Commenting here on HN is one way to build that reputation. You can get go to meet ups to meet people, but giving talks is how you get reputation. The same applies to conferences. At work, especially in larger companies, you can build reputation as experts in one particular technology, lead brown bag sessions to demonstrate that expertise.
You sometimes notice other people that have good network. It's also important to stand out in front of these people to get second degree connections. If you also have good network, these people would gladly be your best friend.
It's also important to note that ISO 8601 format is the default format that Date object serialize to. Try it new Date().toJSON()
This problem is not Ember but JavaScript in general.
> ...can also represent infinite sets
This is the highlight.
[1]: http://vimcasts.org
"C'mon faster!!"
Can be a bit frustrating actually.
I guess the reason could be that because Sublime edits are slower, as the live coder explains things, he/she needs to pause the explanation to finish editing before resuming the explanation. This interrupted flow is what actually causes the frustration.
But if you can do that...
d3.select('.foo').append(d3.functor(node));
Event listeners in d3 are not delegated listeners. Implementing this feature actually is not an easy matter as you need to preserve the d3 data binding context and also attach to the nearest svg element because svg events don't bubble through it.
In a private office, I wouldn't have to worry about this.
Looks like it's in the work.
Most knowledge in this area is scattered is varies blog post, tech talks, and maybe some framework guides. There are a few published as GitHub gists and readme. Occasionally, you'll find some comments in framework source code that reference some reading material
But yes, it would be nice for someone to put together a book.
Some example of frontend pattern: - promise - data binding - FRP event stream
None of these are exclusively frontend, but you'll see them more often in UI development.
I, for one, don't.
Why install a 500MB Facebook app when I can get the same news feed with a 1kb bookmark?
To me, rockstar does not equal to 10xer. Rockstar does not necessarily perform better, but they have gained enough (positive) reputation within their domain that they now have fans.
In other words, hiring rockstars means you get to hire their fans easier. It's a personal network thing.
That's medical ID and SSN
Changing too often can be perceived as unloyal, but changing not often enough can be perceived as unable to adapt to new technology.
Database? Network protocol? 3D graphics? I tend to put these in the same league as web programming, they are job skills. Yet there are plenty of university course on these subjects. So why not have web programming?
So what's left is that those that work in web development are either self trained or goes through one of those dev bootcamps. But people that goes into these programs does not necessarily have a CS background, and to be a "good web programmer", you do need that kind of background.