I read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.
Seeing high garbage collection with ElasticSearch?
Seeing high garbage collection with ElasticSearch? My team was seeing periodic 300ms+ garbage collection pauses. We found out that we had misconfigured our ES instances.
Moment.js instantiation slowness
Was doing some test speedup/performance improvement work recently on the search API and found out something; the moment.js library takes around 100 microseconds (or .1 milliseconds) to create a new instance.
Performance improvement via babel tranpilation removal
My team at work recently upgraded our codebase to use to node 6.9, as node 6 has recently gone to LTS.
Superagent/Request Memory Leaks
The last several weeks Thomas Hunter and myself have spent some of our nights and weekends trying to track down memory leaks in an API we both work on.
A note for the upgrade from Node 4 and Babel 6
I upgraded a heap of projects I was working on to node 4.2.3 and babel 6.
Guide to upgrading from Babel 5 => 6
There have been a bunch of guides on upgrading to babel 5.
Move your Open Source work to Node 4
Now that Node 4 has been released, isn’t it time you upgraded your OS (Open Source) projects to use it?
Figuring out JS quirks
Was looking at some decompiled code from ES6 the other day, when I saw a line that looked like this:
Replaying changes from one git branch onto another
Where I work, we use git (like everyone else), and we follow this common pattern for development:
Code coverage for CoffeeScript and JavaScript using gulp and istanbul without pre-compiling
If you’re not aware of your code coverage when building a serious application, you’re not building a serious app.