Thread by @_larikraun

Great. Thanks for this opportunity. I hope we all learn things from this interaction.

#TweetChatWithOmolara

https://twitter.com/_Ingressive_/status/1070378050930520064

I will be sharing my personal experience on the subject. I will also answer all the questions you may have concerning this topic. This will tilt towards Software engineering but you can pretty much apply some of the lessons to other fields. #TweetChatWithOmolara

I build Android (Java/Kotlin) and iOS (Swift) applications. I had to also jump into Objective C at a point. I also write PHP. Slim is my go-to framework. Then sometimes, I help my team members fix some simple JS stuff when I have to.
#TweetChatWithOmolara

I listed all these because I may touch how and why I picked these languages/frameworks. Before I continue, I will like to state that my experience doesn’t have to be the same as yours. That’s why we are different humans. Right?
#TweetChatWithOmolara

I learnt each language for different reasons.

#TweetChatWithOmolara

I started learning how to code in a language that is different from Fortran just immediately after my 200L final exams. I started with Java. So the question is, why Java?

#TweetChatWithOmolara

I learnt the basics of Java, netbeans shortcut, built GUI apps e.g basic calculator, GP calculator (if you did this, do like this 👆 ), applets, then J2ME apps that did 'things'.

#TweetChatWithOmolara

It was quite easy to start learning and building Android apps because I had learnt Java. Udacity, Study jam and the need to solve some problems helped me on the Android Journey.

#TweetChatWithOmolara

I picked up PHP because my first Job required it. I had to learn this because I wasn’t ready to disappoint my team lead. W3c schools, PHP documentation and stack overflow were my great allies. It was a perfect picture of learning on the job.

#TweetChatWithOmolara @_Ingressive_

I started learning iOS development because my team needed to build an iOS version of a completed Android app. Then my company there is a need to have an iOS team. I jumped at the opportunity.

#TweetChatWithOmolara @_Ingressive_

The previous tweets were just to highlight why I chose to pick all these languages. Each decision to pick up a new language was for different points and reasons

#TweetChatWithOmolara @_Ingressive_

However, there is one thing that was common to all the processes - opportunities. I was at the stage where I had to learn new things and join new teams. I mean I had to sample different fields before I conveniently settled (not really).

#TweetChatWithOmolara @_Ingressive_

The following tips have helped me through all these processes:

Resources - there are several places you can get information about a subject. Documentations, detailed answers (and questions) on StackOverflow, Youtube.

#TweetChatWithOmolara @_Ingressive_

Know the kind of resources that fit your style and subject - There are some topics that may require you watch videos, read plain articles and sometimes combine both

#TweetChatWithOmolara @_Ingressive_

Share your learnings and victories with people. This could be via knowledge sharing at your work place, articles, answer questions on stack overflow etc.

#TweetChatWithOmolara @_Ingressive_

Read personal stories of how people fixed some certain bugs/errors. There is a kind of feeling when a solution has a personal touch. I cannot explain ;)

#TweetChatWithOmolara @_Ingressive_

If you are still at the phase of trying things out, you can see to joining different teams in your company. This gives you understanding of the languages/stack you enjoy working with.

#TweetChatWithOmolara @_Ingressive_

You should also subscribe to newsletters, channels , publications, watch repositories. This helps you stay informed about changes, trends, approaches.

#TweetChatWithOmolara @_Ingressive_

I will refer to myself as a Mobile Engineer because that's what my day-to-day looks like. That's my core. That's not to say I can't wear other hats when necessary

#TweetChatWithOmolara @_Ingressive_