You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love hear a discussion about what knowledge and experience an iOS/macOS developer should have in order be called Junior, Mid, Senior or Lead developer. There are so many inconsistency in this topic. One group of people says one thing, another group has something completely different in mind. There were even attempts to define and make it more clearer for young and even experienced developers (links are attached). I do understand that differences in opinions are normal and there is nothing wrong about that.
I’m writing this, because of my own personal experience. I’ve seen so many people who simply gave up on software development. They thought that it’s endless, impossible thing to learn. And it is in some ways. Once I’ve personally defined some “borders” between different roles (so to speak, the things that I should be able to do and know in order to be competitive for a particular position) I felt much better, since I was able to define myself as a developer, set concrete goals in order to get into the next level and grow.
Since it’s a community podcast, I offer to discuss those blurry borders between the roles and name several concrete expertises for each of them. That should help everyone who is just starting out to guide them though the process of becoming an iOS/macOS developer. I hope the audience would be interested in to hear some of your own stories and thoughts related to this topic.
Hello,
I would love hear a discussion about what knowledge and experience an iOS/macOS developer should have in order be called Junior, Mid, Senior or Lead developer. There are so many inconsistency in this topic. One group of people says one thing, another group has something completely different in mind. There were even attempts to define and make it more clearer for young and even experienced developers (links are attached). I do understand that differences in opinions are normal and there is nothing wrong about that.
I’m writing this, because of my own personal experience. I’ve seen so many people who simply gave up on software development. They thought that it’s endless, impossible thing to learn. And it is in some ways. Once I’ve personally defined some “borders” between different roles (so to speak, the things that I should be able to do and know in order to be competitive for a particular position) I felt much better, since I was able to define myself as a developer, set concrete goals in order to get into the next level and grow.
Since it’s a community podcast, I offer to discuss those blurry borders between the roles and name several concrete expertises for each of them. That should help everyone who is just starting out to guide them though the process of becoming an iOS/macOS developer. I hope the audience would be interested in to hear some of your own stories and thoughts related to this topic.
The text was updated successfully, but these errors were encountered: