Since I like using AngularJS and the current client project and the last few client projects I’ve been on use AngularJS, I realized there may be others out there who want to start learning AngularJS or enhancing their current AngularJS web apps. So I started a newsletter where we post the newest books, tutorials, articles, modules and code libraries that AngularJS developers should check out.
pretty much the same experience I’ve been having, at least the documentation part. it’s almost non-existent and single sentences to explain options in the query DSL are useless, there aren’t enough examples either.
what’s with JS and newer developers completely forgetting to write documentation? It’s strange and unfortunate.
Originally posted on Sammaye's Blog:
After hearing all the raving about Elastic Search and how it was awesome and “rad” or whatever “hip-young” programmers want to say I decided I would give it a go.
To get the point since this might be a bit tl;dr: I am not overly fond of it. I am unsure what companies like GitHub see in it.
It has a queue, no need for a river
Excactly that, implement it into your active record and you don’t need to river.
I would in fact advise agains the river, it ues the oplog which can be slow and not only that but you are adding yet another lock on top of the secondaries that are trying to read as well, which may increase your chances of replication falling behind, this is of course dependant upon how often the river pings your oplog and how many new ops you have in…
View original 1,689 more words
I also started exploring three.js, a WebGL library.
The macro I wrote simplifies the render loop, you supply the scene and camera object and the body of the loop and you’re set. The macro sets up the renderer.
Again, not the most appropriate use of macros but it was a nice small way of getting used to macro definition syntax and to explore how much potential power there is.
There’s also a Grunt task plugin to run sweet.js which automates the whole macro compilation step. Just add file watching and reloading and the experience is pretty much the same as developing with CoffeeScript.
Hope this encourages other JS devs to check out what sweet.js can offer and maybe one day we’ll have a nice set of macros to simplify the common JS frameworks out there.
PHPUnit Essentials would have come in handy while on a
recent contracting gig and on all the other PHP projects I’ve worked
on. The book is published by Packt Publishing who seem to be the new
O’Reilly, the last book I bought from them was on AngularJS and it was
a great guide whereas as the O’Reilly book on AngularJS was outdated.
Overall the book was a good read and it’s worth getting as both a guide and a reference.
Trying to figure out how the whole consulting business works out. Finding new clients is going well right but it’s the whole mindset of offering a recurring service using retainers or offering productized consulting which has me scratching my head.
Glad to have experienced the joys of being a pet owner though it’s only for a little while.
Trying to speed up the first generation Nexus 7 tablet and the only luck I’ve had is with disabling syncing, disabling Currents and removing games and apps that I’m no longer using. Keeping old games around can especially drain battery and kill speed because they’re running in the background sometimes. I’m not sure what else can be done to improve.
Using Google Play Music to store part of my music collection. Not sure yet whether to sign up for the monthly unlimited streaming.
Listening to PSY + Snoop Dogg – Hangover, and listening to Kygo: https://soundcloud.com/kygo
There was some discussion a while ago on the Libreplanet mailing list about creating a wiki called the GNU Developer Network, somewhat similar to the MDN (Mozilla Developer Network) and the MSDN (Microsoft Developer Network). I think it’s a great idea, free/open source developers need a wiki for more discussions and a general place for free software developers to find more info.
Someone suggested that the GNU Coding Standards point the way and that a wiki would just be duplicating whatever information exists in the GNU Coding Standards.
Using a wiki lets developers suggest proposals in a forum other than a mailing list, which tend to be a little more exclusive. Using a wiki makes the documents living, and people won’t be afraid to spark a discussion about how and why sections of the standards need to be kept the same or updated.
Originally posted on GoAugust:
Today we’re proud to release angular-google-experiments v0.0.1, it’s a library for AngularJS which lets you use Google Analytics Content Experiments in your web app. Content experiments are useful for A/B testing and optimization.
You can install it like this:
bower install angular-google-experiment
However you’ll need to use something like Angulartics or some other Google Analytics library in order to send events otherwise the experiment will not work.
We hope that this library encourages more AngularJS developers to use content experiments when designing sites for their clients or for themselves. The value of experimenting is that you can increase CTR (click through rates) by changes in the text or images or colours or layout that are used.
It’s very simple to use as well and the simplicity of it is such that you might be tempted to insert a lot of variation directives for your experiment!