It’s not about failing. It’s about getting feedback, fast.
As creatures who move in one direction in time, events spread across different spots of time-space could be lined up and explained with cause and effect. It’s how neurones work. Strengthen the repeated connections and destruct the singled-out ones.
Last night I flipped through his blog posts on recommendation, and it blew my mind. I might not have had this level of mind-blown-ness in months.
Seriously, go read it if you haven’t.
http://www.kalzumeus.com/greatest-hits/
Error message:
Uncaught Error: [$injector:modulerr] Failed to instantiate module x due to: Error: [$injector:modulerr] Failed to instantiate module x due to: Error: [$injector:unpr] Unknown provider: xx
If it actually works, I’d passionately take on a full-time job where I march around on the streets, wave my arms and chant “please read these books!” all day long, because the world would definitely become a better place if more people read those books, and this is the most natural and efficient approach I could come up with.
This is a weird case. Random files get clogged with localhost. Restarting the server got it right.
Say we have html structure like this:
<div id="parent"> <h1></h1> <p></p> <p></p> </div>
What would this selector have selected?
#parent{
p:first-child{}
}
Links: Github Repo / Live Demo
Angular directive, with recursive support for multiple layers of checkboxes.
For me the revelation came when I realised that they all work the same way: by running something once, storing the value they get, and then cough up that same stored value when referenced through Dependency Injection.