Just some random thoughts / stuff I've bumped into recently. Enjoy.
Interweave tests in support
I love this legacy code rule (it's supposed to help fighting the technical debt):
When you touch any existing piece of code, always leave it in at least slightly better shape than it was before.
It makes sense, sounds golden, but it's quite intangible (or ephemeral) by its nature. What
JS, JS, JS everywhere
Few days ago I had a short discussion about an idea for a webapp (publicly available, commercial, you know - all the usual stuff). As I am doing a lot of stuff in web nowadays & I've made few SPAs with different libs recently, I was asked:
"Which SPA library / framework would you use today?"
My interlocutor was utterly surprised with my answer:
The waiting is over, it's already here. Maybe it doesn't resolve all the concerns (yes, concerns, I wouldn't even call them issues), but 1.3 is a major update that was supposed to prove that Angular.js is evolving & community's voice is being taken under consideration.
If you want full list of changes, you have to check here. Below you can
I've spend some time on prototyping a modular SPA hub that meets the following core requirements:
- from users perspective - it all looks like one app (seamless navigation, same looks, shared layout, etc.)
- it consists of independently developed (by different people) modules, BUT these modules may use other modules' presentation elements (on some established level)
- modules are supposed to be automatically testable (incl. presentation
The number of awesome libraries for HTML5 + CSS3 + JS is overwhelming. Pretty much every day I find something absolutely awesome, that I’d like to give a try the very second I spotted it. What is more, the vast majority of those are free, so personally I see a very little justification for buying expensive widget libraries like KendoUI (http://www.kendoui.com/