I could still be attached with the project in order to bring the quality of the work during development.
I could have a better overview of the project.
I could keep my head cool when it comes to the term of negotiating.
I could juggle more happily.
And this is a time saver.
I decided to stop making this app in java as native one for android, and switched it to html5 app. I’ve been on and off, trying to make this children app for my kid. It started as simple flash card. However, as time pass by, the project had become a giant snow ball because I wanted to put more interactions and animation details into the app. The other usual work was already coming up to my neck, and I still didn’t see much chance I could ever finish this project in time with the current direction I was going.
The pride is making me holding on to the thought of not giving up the time I’ve invested in the project and the fun of making animations in java. Learning was fun. Even the chaos created by this fun was amusing. However, what would it do me any good if the snow ball is becoming too huge and useless for the toss?
I think people who are on the journey of pursuing an inquiry are blessed. Especially if his or her inquiry is the kind that helps him or her accelerate the personal growth. This kind of journey may not seem to be as exciting as traveling around the world and incredibly slow, but it awards you every moment. Even you may not see it. Even if you fail in the end. The real reward is learning to grow.
Just got off a long conference meeting with a client for troubleshooting the project deployment. The truth was there had something I could have done to improve the efficiency during the meeting and that was to be honest.
Say stop, if I see the client is going into the direction of misunderstanding. Say no, if I’m absolutely know the approach won’t work. Say give me a sec to think if I really need to.
It turns out the debugger not just helping me identify the errors, it also helps me learn lots of things under the hood. Pocking around the Framework sources, navigating through layers of layers of objects, traveling in and out the virtual machine etc.
It never ceases to amaze me that so much code on the web does not work. It number of coders who persistently post unworkable code also continues to surprise me. We even find this on Stackoverflow. Links to code, working or otherwise, also have a tendency to become broken; or it becomes unusable when newer versions of libraries become available. There is a lot of unworking and potted code on the web.
Or…sometimes I find the solution inspired by those comments under the unselected answer. I intend to think that it’s just hard to find this one particular missing puzzle piece without seeing the whole picture.
RequireJS is the best loader because:
- It manages dependencies.
- It loads text into strings.
- It has an awesome compiler capable of minifying and concatenating your JS and text dependencies (templates).
- It works great with non-AMD modules via the
- It works in node.js too
- It can be subbed out with another, optimized AMD loader for deployment e.g. Almond.
Managing dependencies…..I think you’ve just given me another notion of having some experiments!
Github - software engineers will pay monthly fees for the rest of their lives in order to create free software out of other free software!
LinkedIn - how about a professional social network, aimed at busy 30- and 40-somethings. They will use it once every 5 years when they go job searching.
Instagram - filters! That’s right, we got filters!
Facebook - the world needs yet another Myspace or Friendster except several years late. We’ll only open it up to a few thousand overworked, anti-social, Ivy Leaguers. Everyone else will then join since Harvard students are so cool.
Dropbox - we are going to build a file sharing and syncing solution when the market has a dozen of them that no one uses, supported by big companies like Microsoft. It will only do one thing well, and you’ll have to move all of your content to use it.
PayPal - people will use their insecure AOL and Yahoo email addresses to pay each other real money, backed by a non-bank with a cute name run by 20-somethings.
When you look at the sample codes, imagine what you’d do without the reactive.js. Global variables? A simple class, prototype in this case perhaps? Or you want some more permanent handy tools, so you start thinking about building your own library? Boom! There you see the reactive.js