Tungsten Innovation

If you are working in a team building a product you should be reading this...

empathy-driven-development.com

Also this...

https://ashfurrow.com/blog/building-compassionate-software/

If you want to build your team productivity, it has to start with your communication.   if you want to build better communication it has to start with you how you treat each other in the group.  Pay attention to how you react to others and the words that you use.  It helps to ask questions.  If you have a comment that people might perceive as rude or aggressive, try phrasing it as a question instead. 

“You should of.....”

Should turn into “Have you considered...”

It also helps if you let everyone get their thoughts across in meetings.  That means not allowing one person to dominate the conversation.  That takes more work as you as the individual need to make sure your not the dominant one and you also help to get other’s voices heard.

This is a good summary of what the current state of swift is in Linux.  It seems like there are a lot of people trying to port it over right now, but it doesn’t appear to be ready to do anything with just yet.

So I realize that this should be filed in the category of done a while ago....but I never bothered to really pay attention to what the $(inherited) value means in Xcode until recently.  

With the current iOS ecosystem you have the ability to write for many different devices and package it all into 1 IPA (iPhone, iPad,  watch, Today Extension, etc...).  While that brings a much better experience for the users of your products, it also brings complexity for you.

One of the ways that you can make it a little easier on yourself is to make use of $(inherited).  If you have project settings that you want to share with your different targets, then you can use $(inherited) in place of that setting and it will refer to the matching setting on the Project.  That way you only need to set it once and it will proliferate through the rest of your targets.

I am still getting the hang of how to properly use the new `do { try something } catch { }` statements in swift 2.  what I find myself running into is a lot of nested do try’s because usually i’m not just doing one do try catch.  I find it hard to believe that is what Apple intended for the use of this, and I’m curious if there are any better ways to do multiple try’s?

Update: After consulting with some people about it i think the conclusion is that instead of nesting do statements, i’m better off putting all of my try’s in one do and then handling the different catch of errors appropriately.

Much like what they say in this link...  http://stackoverflow.com/questions/34147474/how-do-i-handle-consecutive-multiple-trys-in-swift-2-0

Swift has open sourced itself.  I imagine thats how it works being that swift is written in swift so then swift must be the one that open sources itself

As I’m staring at a codebase that i have had a part in making for the last 2 months, the quote “Your code is a reflection of your team communication” is something that is triggered in my mind.  i don’t remember who originally said it, or where there’s a reference to it on the net, but it really is true.  If the front end team is not on the same page as the backend team, and if they aren’t speaking the same language then the code becomes more cumbersome because of that.  

This is something that i wind up setting a lot and always find myself googling it for the answer so I thought I would write it down.

If you want to see hidden files in the mac finder as its easier to find stuff when your doing all sorts of devv’y things then open a terminal and type this in:

defaults write com.apple.finder AppleShowAllFiles YES

killall Finder

....and your done!

if you use cocoapods use_frameworks! to import an obj-c library into a swift code base then you no longer need to declare them in the Briding-Header file.  In face you don’t need that file at all.

This was given to me recently by a friend and it helps me enormously in my daily life at working playing an engineer.

If your computer is managed and won’t let you turn off Gatekeeper on the new version of OS X (el Capitan), even though your and admin, and even though your trying to download something from APPLE’s website, don’t fret there is a workaround.

hats off to the 5 minute watchkit post on this solution to making openParentApplication method stop being so shady.

http://www.fiveminutewatchkit.com/blog/2015/3/11/one-weird-trick-to-fix-openparentapplicationreply