Monday, November 23, 2015

If you invite a developer to a conversation about a dev opportunity at your start-up should be willing to have a conversation. Do not do the hr-recruiting drive-by-shit as its somewhat rude and disrespectful !

Saturday, November 21, 2015

Okay, a little background the java.util.Observable has a flawed mechanism.   Oh gosh what could it be?

Facebook was talking about recently byte code weaving callbacks. But in that clear-as-mud post they did not state why other than the implied speed boost.

If you look at the code behind the new definition of Observable that Google's data-binding library uses you will find that the callback mechanism was rewired(not rewritten at the framework level but the array/collection of was implemented differently). That is where the speed difference is coming from when you compare speed of the data-binding Observers callbacks to a regular android callbacks as far as having a collection of callbacks that are called in a group.

In short words, even if you do not adopt using Google's data binding library and may not tackle rxJava right now, one should re-use the Observable classes from the databinding library and the rewritten and rewired callback mechanism.

That way one would have some of the benefits without fully tackling Rxjava right now.

Thursday, November 19, 2015

GWSGarlic is very small library to help you put up another roadblock to those who would download your app and decompile it and upload to another app store under their name.,

Monday, November 16, 2015

Do you as android developer realize that all those neat tools like scalpel, madge, etc can be implemented as viewgroups and thus can in fact overlay on the debug variant of a product flavor?

So now you know..:)

Saturday, November 14, 2015

Once again, a CTO of start-up contacting me about leading a team who obviously did not do any homework and just search for dev terms. And to top it off my profile kind of screams intermediate android developer not team lead.

CTO, if you cannot do basic reading to determine whether I am intermediate or a senior android developer why should I talk to you, you stupid fuck?

Thursday, November 12, 2015

Now the fun part of my new GWSJinn build system, android code qa. I should route it so that I can always get code qa via the terminal but only code qa reports generated when product flavor prodRelease is built or when the project is executed on a ci server.

To complicate things I never use product flavors on my library modules, only the app module. And that is not even the real fun part, which is doing some fancy xml parsing to come up with an Android Code specific QA dashboard.

Wednesday, November 11, 2015

I have to rant about something that has been bothering me for awhile. I am not sure how to present it so it may not seem as clear as I think I am making it.

Apple's recent design revamp and Google's recent design revamp in their respective mobile platforms was not started by a 'design'. Apple and Google were collecting data and observing patterns in that data concerning User-Interfaces in-general. But where or how did they know to go to data and its collecting in user labs to get the new design approaches?

It happens to involve a certain philosophy revolution in the 9th century that affected every hard and soft science known to mankind. CI Lewis in the early in 19th century came up  with a theory of knowledge, in his work titled..Mind and the World Order.

Basically, we can gain knowledge of how the world works by examining data and patterns in data. In the Mobile  User-Interface context we are re-organizing data for a smaller screen size and other factors that demand that we cast the UI into a new form that is easier for humans to grasp and use right waya without an instructional manual.

Even with International Design(Swiss Design) it was based on some new human knowledge of how our brains work and how our eyes work and transforming that new knowledge which had some new data and patterns basis into  a new design process. No-one realizes that all that data and its patterns are somewhat engineering based, not design based.

We keep hearing start-ups and other firms make the same mobile developer mistake of insisting with the lack of senior developers around that its the one-app portfolio of visually stunning ap that indicates the mobile developer needed when in fact according to both Apple and Google within their own hiring funnels its in fact the strong engineering software engineer that happens to do mobile applications that is in fact the choice that should be made.

Or to put another way, the short-term gain in getting that visual stunning one-mobile app-portfolio mobile developer is soon displaced by a medium-to-long-range loss in that the strong software engineering skills are not there to plot a long-term course of successful additions to that mobile application and surrounding services it uses.

Engineering in its practices of data collection and data analysis to determine patterns drives design not the other way around.

Subscribe to RSS Feed Follow me on Twitter!