How? Why?! How???

Now, I’m sure Microsoft wouldn’t intentionally sabotage popular iOS open source libraries just because they own GitHub now...

Then again, I can’t say I’ve ever experienced an error like this before ... 🙃

Dear reviewers, feedback givers, coworkers, clients and critics...

There is a subtle difference between constructive criticism and just spewing hate!

One offers advice & points in the direction of a better solution, while the other one makes me value you less, as a human being...

If your comment/review/feedback is:
“I don’t like it, I don’t know why, I just don’t” - please keep it to yourself because it makes us less likely to listen to you when you actually have something worthwhile to say...

Yours,
Any and all creative professionals,
including developers.

Shame on you Facebook Developers!

I’m neither messy or anal coder, but whenever I push something to production I make sure to handle all debugger warnings... I don’t think it’s perfectionism, rather good practice, makes important bugs easier to find. ;)

A single Facebook SDK Framework has 70+ unhandled warnings, trivial things, could be fixed in a half day...

I had to use ‘inhibit_all_warnings!’ flag literally for the first time, not to get frustrated every time it gets updated :/

P.S Not to mention I had to change the dependency manager because (with the newest update) they have written themselves out of compatibility with the one I was using... C’mon guys. Not cool.

After a particularly social weekend it’s important to have a motivational buddy to get you back in the game!
You all heard of the debugging duck, meet the motivational duck...

“If your duck can see its reflection - your not developing enough” ;)