What you need to become a developer.

     Becoming a developer has been one of my fantasies as i was growing up, I've always been this guy who spends so much time in my head trying to explain to myself things that should be occurring around me and how they should occur. So in other words i would describe myself as a schemer. This isn't the main reason am a developer today in case you're thinking it is, though its one feature that makes me a little bit good in my development career.

Let's talk a bit about schemer behavior I've always had. 

So this schemer behavior  i have been having at my young age was simply the tendency of visualizing stuff in my head and pretended that the stuff is really going to happen someday so i have always had to provide mechanisms of how these things are going to happen with proper controls, it's stupid but don't forget i was just some random kid exploring my kid-hood. One practical example of this is the times during which i used to travel with my dad across the Ngorongoro national park on his vacations. So during these times as i was in the car on our pretty nice vacation voyage i always visualized some kind of a drone on top of our car following us really fast and accurately, me being the commander of the ship 😎, the behavior lasted as i grew up.

Relationship between being a good schemer and development

With my experience as a developer, i have come to see this job as a complete scheming thing. You always have got to find a problem and scheme a solution for the problem. Simple as that. Facts like being competent in a certain programming language are simply qualifications that a real developer has to be entitled with, but not every guy who is good with a certain language has to be a good developer necessarily.

 Qualities of a good developer

1. You are the first quality you need to become a good developer. 
2. Try and get competent on a certain marketable programming language
3. Build a consistent behavior of learning
4. Be ease with changes

 

1. You are the first quality you need to become a good developer. 

The ability to figure out problems that occur around you and provide them a skillful and best possible solution isn't just a thing anyone is capable of, am not sure what you are capable of,but you of all the people should be sure of that. Anyone can provide a solution but if you can attend a problem with the best solution available then you are good to go as a developer.  Computers are designed to be able to solve problems efficiently and super fast with very minimum expenditure of resources as possible, and so you need to be able to build algorithms that require less resources to solve tasks.

2. Try and get competent on a certain marketable programming language

Leaving out the first part,let's speak about this part. You can have the most fast and super efficient ways to solve problems but still fail to express this electronically , and so this brings us to the part when you need to be competent in a certain programming language. This will help you express your ideas inform of code when is then compiled into an executable program. There are pretty many and lots of choices you can have for a language, i use Kotlin for my android apps development and am soon starting to learn C# as am so attracted to making of games with Unity. I code in C++ as well as Visual basic and PHP. You can have any language of your choice and all you need to do is master it.

3. Build a consistent behavior of learning

 Algorithms to do stuff  change daily, recently i have been struggling with my coding as most stuff i learned are getting deprecated and newer ways get introduced performing the same stuff as they used to but smarter and more efficiently. Guess what am trying to say is that coding isn't static, your ways of doing stuff may work but doesn't mean they are the best. So you need to have a behavior of looking up on the world and improve your attitude and approaches daily

4. Be ease with changes

So this last point supplements the other one above there. Sometimes it gets very difficult to switch to newer stuff which perform the same tasks as the present does. For example not so long ago we had Kotlin extensions working to link the layout views with their Kotlin files and some times later this thing is deprecated but still usable. I was left in a dilemma thinking of whether i should migrate to view binding which is the newer and more efficient technology of binding views but then i did, the point am trying to make here is that you do not need to take so much time deciding like i do. You need to make the decision simpler

Stay awesome,

Sam.