As a front-end developer, I was always curious about mobile apps and wanted to build one. In the last years, I was testing multiple frameworks from Ionic to React native and to be honest, I was never satisfied. Until one day by accident, I tried FLUTTER and this happened:
Flutter is Google’s UI toolkit for building beautiful, natively compiled applications for mobile, web, and desktop from a single codebase.
From Flutter website
Just reading this sentence blew my mind and I was in. After two months playing around with the framework, I would say it’s the one that will take over in the next years for sure. Let’s jump and see how to start with it.
1 – Download the Flutter SDK
Download the stable version and put it in as a PATH environment variable. The download link is here.
2 – Run Flutter Doctor
This command is the most important one as it checks your environment and displays a report of the status of your Flutter installation. Do not forget to check the output carefully, to be able to know what is still missing.
https://www.north-47.com/wp-content/uploads/2020/07/Unbenannt.png3281024Youssef Idelhoussainhttps://firstname.lastname@example.orgYoussef Idelhoussain2020-09-10 07:49:262020-09-10 07:49:274 steps to start building apps with Flutter
You decided to start learning programming. You have started to learn programming concepts, you have decided which language you want to learn, and everything looks great.
Except it isn’t.
It’s frustrating; it’s boring; it’s painful. I am not here to make your life easy, but I hope that I will make it a little easier. Here are the 5 things that I believe will help you to become a better programmer.
Find the right source to learn from
I had a professor who said:
“It’s better to spend more time researching where to learn from, than actually learning from one source.”
And this is gold.
Let’s say that you have found a great book or a great video course that everyone is loving. You think that you will love it too, every word that you read/hear in the book/course you will understand, and after you finish it, you will become a master of the things you will learn (at least, I thought like that).
And maybe you will, but probably you won’t. Most (or let’s say, some) of the things you won’t understand, and it’s natural. You will try to read/watch again and again, but it’s not getting any clearer.
My advice is, try to find a great book/course, and start learning from, but use it more as a reference than learning source.
I am not suggesting to only go through the content. Try to understand the concept, but also research it (on Google). Look for more resources, more explanation, more examples. When you will understand the concept, save the source that helped you the most (bookmark the page), and search for examples that you can solve.
This way, it is easier to learn, because you are combining the explanations of different sources, and you are sticking with the most simple explanation that is working for you. Also, research is more interesting than reading\listening the same thing all over again.
Understand the base (minimum) necessary logic rather than implementation
This is important for a few reasons:
First, if you understand the logic, it will be easier to learn the implementation
Second, the implementation may change, but the base necessary logic won’t
At the very beginning, it will be difficult to differentiate between logic and implementation, and maybe you should try to learn and remember everything, but later try to understand and study just the minimum necessary required things.
I still google some basic things. But because I know what I have to do, I exactly know what to search for (only the implementation/syntax).
With this approach, you will spend your time wisely, and you will be able to learn more important things.
To learn your first programming language is very hard, but that’s because you have to learn programming concepts (the logic). After you learn that, you can learn any language (the implementation) you want, in a matter of weeks.
Code, code, code…
Learning programming is like learning how to drive, except it’s safer (at least, physically). You can read, you can learn, but when you sit down and start to drive, you’ll realize that you haven’t learned anything.
That’s why you should focus on coding. When you study something, try to learn the minimum, so you can start to code, and then code as you learn. There is a great answer on Quora, that mentions 3 rules that you should follow when coding.
Write at least one line of code per day
First, write code, then refactor
No distractions when coding
Here, you can check the answer, that has reasoning for these rules. Maybe you can forget the second rule, but the other 2 are very important.
I had to mention attitude. It is a hard path, especially at the beginning, so the right attitude is required. Hard work, believing in yourself, learning to say YES to everything is needed. More precisely, you say NO only when you are 100% sure that it isn’t possible to do. In any other case, you say YES, and you investigate, you try different approaches, you ask for help if it is necessary, you do everything you can. A time will come when you will need to learn to say NO, but first, you have to learn to say YES.
Of course, don’t forget to rest. You have to rest from the hard work you have done. Most of the stupid things I have done were when I was too tired. When you are tired, you don’t think rationally. You just want to finish your task, no matter. That’s when the biggest mistakes come. You won’t learn anything, you won’t do anything well, you are just wasting your time and nerves.
https://www.north-47.com/wp-content/uploads/2019/09/New-to-programming.png366800Elvedin Selimoskihttps://email@example.comElvedin Selimoski2019-09-23 06:37:592019-09-26 12:54:53New to programming? 5 things you should pay more attention to