Felix Gondwe

keep looking, don't settle

Hybrid App vs Native App dilemma — April 10, 2016

Hybrid App vs Native App dilemma

I think of myself as a fullstack developer but the stack is becoming more complex each passing day and at times am not sure what it means anymore. For instance, before mobile development was popular fullstack mostly meant a person comfortable with back end(C#,PHP,Java,SQL,MySQL…) and front end(HTML,CSS,Javascript…) hence that’s where I fit in.

However when you start talking about native mobile application development, the stack begins to change because Android or IOS or whatever you’re into brings its own stack in some sense. As such to make sure I fit in within the ‘modern stack’, I have to be comfortable with the mobile frameworks as well, at least in my opinion. If I was still in college, it would be fun to learn all these and impress companies with my application portfolio. Now I do not have that luxury, as such I have to make sure am adding as much value as I can to my current work place leaving little time to experimentation of the ‘modern stack’.

For the longest time, I have been trying to find ways to make use of my current web development knowledge to build native mobile application as quickly as possible. I have been experimenting with Ionic, Xamarin to make applications that have same feel as native apps but haven’t had much luck with that. That’s the main difference between hybrid apps and native apps, it doesn’t just feel same no matter how hard you try. Hybrid application definitely work and sometimes an average user can’t tell difference between hybrid application and native application.

Good news is the answer is here: Angular2 and NativeScript. These two will change web and mobile development game. They are both in Alpha stage but I am taking them for a drive because I am very excited what these two guys can accomplish together. So now I can just work making my javascript or typescript knowledge better and develop across all platforms. That’s a win 🙂

I will be blogging more about these two magical things; Angular2 and NativeScript {N}.


Windows path too long issue — April 8, 2016

Windows path too long issue

Spent 3hrs the other day trying to figure out how to delete folder with node_modules in a windows box. I know you thinking, why not just google it! Trust me I did, but sometimes we look into wrong places for answers and that’s okay. I learned a thing or two in those 3 hours, they didn’t go to waste. Failing forward 🙂

Long story short here’s how you can resolve the issue: Use ROBOCOPY! Its so simple. I will not go over robocopy syntax in this blog (Let’s keep that for another day)


  1. Create an empty directory in your C:\ drive, for example mkdir emptyFolder
  2. Create another directory on your C:\ drive and copy(cut + paste rather) the folder failing to delete to that folder you just created. for example: mkdir myFolderToDelete
  3. Run the following command: robocopy <source> <destination> [command]

See below

robocopy C:\emptyFolder C:\myFolderToDelete /purge

There you have it, those node_modules or any other long path folder issues won’t bother you again 🙂