Is nice to see a forum member taking a piece of a pie
Keep the good work!
Well, when my former company tok the "all should go mobile" hype that was spreading around 2009-10, i was forced to jump "into the fire" in less time as possible. The first moment i was introduced (in deep) to Apple technologies was at WWDC10 in SF. I was really amazed of the community that was so pumped up with all that shinny and buzzwordish stuff, jingling around with all those iPhones and iPads and shiny applications ... The thing that shocked me the most was the amazing developer support we got downstairs in the workshops ... From the surface scratching of basics to the most complex stuff like graphics and advanced OpenGL programming for games .... for every geek there was an support person that answered all smart and dumb questions you thrown at them ...
Coming back form WWDC10 and calming down, i was in the moment to write first lines ... in those moments i wish i never sign myself to the mobile department I had some C and C++ background, but Objective-C was really something new for me. With the help of really extensive help and examples library i was able to go steps up every day and relatively quick.
The thing that bothered me the most was the "manual" idea of memory management. Those retains and releases got me shizling crazy so much i wanted to pull my hair out. You don't own the object don't release it .... or if you take ownership of the object take care to release it properly, those words seems really easy to understand on paper, but when you do it in practice and without experience you can end with an really ugly and nice memory leaking piece of code
I was so afraid that my app will crash, umm not crash .... that the phone will explode ... i ran Instruments after every few lines of code i wrote, to see if i had memory leaks. That was scary, tedious and somewhat weird experience.
The two most important things concerning generic Objective-C concepts, that i learned at WWDC was, 1. Use the (Cocoa) frameworks, like Apple said - we built those frameworks for you (and obviously from a team of top-end coders), so don't reinvent the wheel 2. Don't extend everything and with this statement go to the point 1. That helped me a bit, and after some time of adaptation i was able to do something useful with all this nice development ecosystem ...
Well, when my former company tok the "all should go mobile" hype that was spreading around 2009-10, i was forced to jump "into the fire" in less time as possible. The first moment i was introduced (in deep) to Apple technologies was at WWDC10 in SF. I was really amazed of the community that was so pumped up with all that shinny and buzzwordish stuff, jingling around with all those iPhones and iPads and shiny applications ... The thing that shocked me the most was the amazing developer support we got downstairs in the workshops ... From the surface scratching of basics to the most complex stuff like graphics and advanced OpenGL programming for games .... for every geek there was an support person that answered all smart and dumb questions you thrown at them ...
Coming back form WWDC10 and calming down, i was in the moment to write first lines ... in those moments i wish i never sign myself to the mobile department I had some C and C++ background, but Objective-C was really something new for me. With the help of really extensive help and examples library i was able to go steps up every day and relatively quick.
The thing that bothered me the most was the "manual" idea of memory management. Those retains and releases got me shizling crazy so much i wanted to pull my hair out. You don't own the object don't release it .... or if you take ownership of the object take care to release it properly, those words seems really easy to understand on paper, but when you do it in practice and without experience you can end with an really ugly and nice memory leaking piece of code
I was so afraid that my app will crash, umm not crash .... that the phone will explode ... i ran Instruments after every few lines of code i wrote, to see if i had memory leaks. That was scary, tedious and somewhat weird experience.
The two most important things concerning generic Objective-C concepts, that i learned at WWDC was, 1. Use the (Cocoa) frameworks, like Apple said - we built those frameworks for you (and obviously from a team of top-end coders), so don't reinvent the wheel 2. Don't extend everything and with this statement go to the point 1. That helped me a bit, and after some time of adaptation i was able to do something useful with all this nice development ecosystem ...
_________________
-----------------