Mobile or Web (or both)?

Many beginning developers are questioning themselves about the area of the software development they want to build their career in and I was one of them (I'm still beginning, but I did choose already).

Today there are several major areas you can focus on.

1. Operation Systems (Windows, Android, iOS etc.) - here you would write pretty low-level code that would handle interaction with the hardware.
2. Game Developing - could be broken down into many subcategories, such as game engines, UI in games, gameplay etc. 
3. Mobile - building apps for mobile devices running Android, iOS, Windows Phone etc. This area is growing really fast nowadays because of new mobile devices. Android is embedded in TVs, cars, VR and IoT (I personally think, that someday Android development would be one of these major areas of software development itself).
4. The Web is growing just as fast as mobile, and the reason for it is online clouds. Almost everything is going to the web, it's convenient, you can access it almost everywhere, and in developed countries, it's fast and cheap. 
5. Data science - this one is about big data analysis, machine learning and sometimes artificial intelligence. Note that it's actual science. You would be learning much theory before doing something actually working, unlike the other categories.
6. Embedded software - this is low-level software that is built for one particular product, for example, for a digital camera. This category got a second breath with the emergence of the Internet of Things.

There are more, but it could take a whole post to list them all. If you think there is a category that definitely should be on this list, please drop a comment I will include it.

Today I want to talk about the two most popular (for now) categories: mobile and web development.

Mobile VS Web

Some people think that there is some kind of competition between these two. And they are right, in some way.

Mobile and web developers always try to make the experience on their platform feel better that on the other. 

Which is better, create a mobile app or just make an ada``ptive design of web version for mobile devices?

What is great about this competition is that it's healthy, it makes both platforms create new ways of interacting with the users, enchant them, simplify their life, and make them amazing.

I even heard the opinion that you should both web and mobile. Which, as I think, is wrong because if you want to build the career it's better to focus on something instead of picking all into sight.

So if you want to be a developer what should you pick? Unfortunately, it's not that straightforward but let's look at advantages and disadvantages of every category and I hope it will help you to decide on your own.

Web Development

Advantages	Disadwantages
Cross-platform. You can run your app on every device that has a web browser.	Runs only with browser so if you want to build offline app using web technologies (e.g. Atom) you need to ship a browser with it
A huge developers community	You can only use JavaScript and it's kinda slow so you limited in optimization.
Fast development cycles (write->build->test->repeat)	You do not have the computer resources control unless you're using some framework for building offline apps

Mobile Development

Advantages	Disadwantages
Over a billion of people have a mobile phone	There are two major platforms and you should choose only one (while it's better to have your app on both)
A huge developers community as well (for Android and iOS).	Slow development cycles.
Full control over resources.	You should care about optimal resources usage.
You can use native low-level processing (for example NDK) to optimize your app

For me, mobile is more convenient. And I don't mean that Web is worse, it should be your choice.

If you want to build something more interactive it's better to learn mobile, if you want your apps to be accessible from anywhere and anything that has a browser it's better to get to Web development.

I hope I helped you to choose the direction to go.

See you in the next one!

Top 6 learning resources for Android Developers

In my opinion, learning is a lifelong process, and that's a popular point of view today mainly because it's information age. Knowledge now is the most powerful tool, not the only one that is needed for success, though. Furthermore, without it, no other tool can help you achieve it.

I think that you already know the importance of learning if you read this blog. So today I'll give you my top 10 learning resources for Android Developers.

1. Udacity

Udacity is my favorite online-learning platform. And I think it'll always be. The enthusiasm and passion with which its' CEO and co-founder Sebastian Thrun develops and maintains the platform are encouraging.

First of all, it worth to mention that Udacity is not an Android tutorials platform. There are a plethora of courses and nanodegrees for different professions and specialties, such as iOS, web development, tech entrepreneurship, machine learning, cloud computing and so on and so forth.

With his platform, Sebastian Thrun wants to repair today's broken education system. Provide learners with an affordable source of knowledge and give them an opportunity to enter the business area of their dreams and moreover, perform great in this area.

For Android developer, there are 2 great nanodegrees. One is for beginners and the second one is for intermediate. Both are made by in partnership with Google that makes this information a first-hand. In my opinion, this is a great opportunity to learn for those who participated in the platform development.

The one for beginners was introduced not long ago, at Google I/O 2016 I believe. It contains Android Development for Beginners wich was the first course I've completed on Udacity, and many other courses that will help a starting out developer to build a portfolio full of basic Android apps. 

And the second one and the one that I'm in the process of passing Android Developer Nanodegree. This one is great so far and as I think is most complete Android course out there. It'll teach you how to build advanced applications that require careful design and implementation.

These nanodegrees are $199/month and $299/month for Nanodegree Plus (you'll get a job offer or 100% refund) and if you graduate in 12 months you'll get 50% tuition refund. Also, you can complete all the courses for free but you'll not get benefits of nanodegree such as code reviews, personal instructions etc.

2. Android Weekly

This is not an educational platform like Udacity. It's not even a blog or something. It's a newsletter, but the effort that its' editors put in every newsletter is priceless and make it such a great source of new information about Android. 

I mean, this is just a mediator, but such a great mediator. Android Weekly is not only for those who wants to learn about Android but also for those who just want to be up to date with everything that happens in Android community.

It provides you with information about latest blog posts from all around the web, new podcast releases, new youtube videos and even conference and job offerings. Without it, I would probably bash my head against a wall searching all this.

I really encourage you to visit Android Weekly and subscribe to their newsletter.

3. Android Hive

Yet another great way to learn about Android. The author of this blog is Ravi Tamada and he is as said a Hardcore Android Developer.

There are so many great, valuable, and detailed tutorials about Android and  technologies related to it.

Almost anything you can think of in Android Development is already written as a tutorial on this blog. Really recommend it!

4. Android Developers Blog

Who can get you in the insights of Android better that people who made this? I think no one.

And this is what all about this blog is. The people from Google's Android team sharing tips, tricks, insights and new features of Android.

If there's something that should be discussed in Android community, be sure that there is already a blog post about it on Android Developers Blog.

5. Google Code Labs

I've already written a blog post about these the other day, but it never hurts to mention them another time.

Great tutorials with on the go instructions about special features that you may want to implement in your Android app.

6. Android Development Training

And of course last but not least the Android Development Training. 

Here you can find most up to date information about crucial parts of Android Development provided with code samples from real Android apps and detailed explanations of all what is going on in the code.

If you stuck during development and don't know how to implement a common feature this is the first place where you should go for help.

Also, in the Udacity courses this training often acts as a reference for students.

So here's my Top 6 of learning resources for Android Devs. If you know something great and this is not in this list please share in the comment section below, I'm learning too so extra supply of knowledge can not hurt.

It's all for today, see you in the next one! (or in the comment section :) )

P.S. It would be douchy to include myself in this list but I'm writing about Android Dev too!

Why You Should Probably Stop Follow Your Passion

Kind of strange title for a blog which aims at motivating people to learn, isn't it?

But I really think that passion is not moving people forward much. Passion is unstable and inconsistent. It can be helpful on first steps but after that, it leaves you with yourself.

What Is Passion

To avoid any misunderstanding I want to define what I mean when I say "passion".

I personally, see passion as an imaginary friend that I think will do much of the work with me. When you just starting out, it's really great to have that one friend because you think that you can move heaven and earth. But with time passion leaves and you don't feel like doing anything you started with it.

Look at this as walking with someone arm-in-arm. You two maybe want to move with different speed, but often this speed defined by the slowest one. And it's sad to admit, but passion is slowing down every day, and one day it just stops.

But how to overcome this? How to keep you doing what you was so passionate about? I think there is an answer.

Stop Follow Your Passion

I think that by just blindly following your passion you will not get valuable results and will be disappointed in what you were passionate about.

I'm talking about it because I know it firsthand. I have plenty unfinished projects that I was passionate about. All of them now just are gathering dust and I think I'll never go back to them.

Yes, you should just stop it. But it doesn't mean that you should stop doing what you were doing. No, but you should stop relying on that imaginary friend. 

I think that habit of relying on someone else comes from our childhood when parents supply us with all the necessary things, such as food, clothes, a roof over your head etc. And despite that we are grown up, independent people that habit remains. 

And as every habit, it's possible to give it up. Let's consider how.

Giving Passion Up

Subconsciously we want work to do it itself (or the passion imaginary friend will do it). We concentrating on the result but always ignore the process. 

The process is the main part of success!

It's important to realise where you want to come, but you can't get anything done without doing it.

In this terms, Shia LaBeouf is absolutely right. Just DO IT!

Many people experiencing "lack of motivation" because this motivation is all they had. They went all in with this motivation and lost.

You should have something else besides motivation/passion. 

I think that the best thing you can have is routine that you keep up no matter what. With routine things become easier.

And the most suitable time to build your routine around something is when you most passionate about it. 

You (probably) brush your teeth every morning and every evening. Do you need to be motivated to brush your teeth? I think no. It's just your routine and you do it no matter what.

You should extrapolate this approach to other things you doing. Especially ones you want to succeed in. 

Define hours when you code, hours when you learn new things, hours when you eat and even hours when you sleep.

After that even if your motivation is gone you left with your schedule that will help you to reach your goal.

For Example

This is my personal schedule. Seems little bit scary. But it's flexible can change depending on what I want to achieve and my university schedule. (Kanbanflow is the software that helps me to track my tasks)

Now, consider this blog when I was just starting out (actually, I am just starting out), I defined that I will write a post every week on and publish it by 2 p.m. on Sundays. It's my 9th post (not counting Hello World post). In march 2017 I'll have 48 posts and the year after that I'll have 96 posts, 192 posts in 4 years etc. 

No matter how motivated to write I was on Sundays. With time, I will have a big blog with much content to read. And I will get all the benefits of blogging.

These benefits (especially for a software developer) and ways to get them you can find in free email course How To Create Blog That Boosts Your Career made by John Sonmez author of Simple Programmer blog. Many ideas I've got from his book Soft Skills: The software developer's life manual and encourage you to read it too.

Summary

Passion is a great kick starter, but it can't be used as a fuel. 

Great fuel is the discipline. 

Discipline is the thing that will push you forward from milestone to milestone. And moving from milestone to milestone you will acquire new passion for starting something new.

Discipline is the basement for growth. And in our constantly changing world growth is crucial even if you want to stay put.

So go ahead, build your schedule and make your success closer every day. No one will do it for you.

See you next week, peace!

What if there is a similar app that is more successful than yours?

It's so much easier to publish your app in Google Play than in Appstore, that's why there are so many similar apps in Google Play. It creates conditions for healthy competition among developers.

To perform well in this competition you should always keep your app better than the others.

But what if your app is already losing? What if there is an app that has a larger audience than yours?

Actually, I think that it's not even a problem. It's an opportunity!

An opportunity

Wait, what? An opportunity? Why losing to another app is an opportunity?

Because you losing a battle not the war!

Actually, I think that software market is a place where nobody can win the war. It's Infinite War (not the Infinity War, though), with many many small battles.

Still, why losing a battle is an opportunity? Because if you analyse the reasons of losing, and why your opponent is winning you can gather very useful information.

With this information, you can come up with a plan that is even better than your opponent's.

What kind of information?

You should pay your attention to some key moments while analysing your loss.

These key moments are

• Is your opponents app is actually better (be honest with yourself, it's the only way to improve), if so:
• What is the feature/features making this better than yours?
• If you find some, can you improve the idea of this feature in build it in your app?
• If you can't find these features pay attention to the implementation of features both apps have, maybe it's just about the quality.
• Look at things that are in your app but not in opponent's, maybe they are surplusses and making UX worse.
• By the way, if you decide to remove these things, you should be very careful because if you have some decent audience they can use this features and removing them will be harmful.
• Maybe it's all about graphic design. Some users migrate from one app to another (that has the same functionality) just because of design UX can make a huge difference.
• If it is not, likely the reason of succes of other app is marketing. 
• Unfortunately for many developers, better code and design doesn't mean larger audience, it only means an opportunity to get a larger audience. 
• Pay attention to how your opponent marketing his app.
• Does he have landing page about his app?
• What traffic sources he uses?
• Maybe he has a blog where he writing about this app (blog can be a huge source of traffic)
• Compare this to your ways of marketing your app, find differences and figure out what you should change to gain more audience.

Another really important source of information is feedback, not only from your app, but form every similar app out there. You can find out what people need from their own testimonials.

With all this information, you can take action and make your strategy better.

Is it even legal?

About the first part, it might seem like stealing features, yes it is, but you should be a clever thief.

You shouldn't just take your rival's app and make another x.x.x version of it. Actually, you should do the things your way.

You probably already have some picture of what is your audience and why they like your app. So do everything with this on the background.

Your actual audience is your potential audience

Actually, in every business, you should aim at the audience you already have. Improve your app for them. I think that actual audience is your potential audience. It's word of mouth marketing. 

With this approach of satisfying your actual audience, you can get exponential growth. 

It's really important, but many developers and entrepreneurs don't understand that, and they are drowning while trying to attract new users. 

When you trying to walk through someone else's path you will eventually discover that you're always second.

So don't just steal someone's features try to adapt these for your users. And if you can't do so, just don't, it means that it's not for your app.

For example, look at Apple, everyone knows that they are stealing features and ideas from other mobile manufacturers, but they do it in their own way satisfying the users they already have. I think, that this is the reason of their success.

Overview

The main idea of this post is when there is some app that already has more users than yours, it can be a source of really useful information for you if you will analyse it carefully.  But you should be pragmatic about what you doing with your app when trying to gain more users.

Okay, build your audience guys, see you next week, peace!

How To Get an Idea For an App

There are two common problems in software development, lack of knowledge and lack of ideas.

For today's post let's consider the second one.

Lack Of Ideas

Suppose you have, decent skill in software development, so what other you need to start developing software? Right, the Idea (and IDE of course). 

So where do you find them? This question is often the main struggle for many software developers.

Common Pattern

Look at apps on your smartphone. What is common between all of them?

Yes, they are all some way useful, not productive, though, but useful.

An app should be useful

It's surprising how many devs don't understand that.

Every app is useful in its own way. Some app lets you manage your personal finances, some helps you with time management, there are a bunch of apps that let you stay connected with friend and family (e-mail/messenger apps), and some of them help you avoid boredom (I still have Flappy Bird installed for the emergency case).

So most of the apps (not only mobile) out there solve some problem. So if you are a programmer you already familiar with problem-solving, but what about problem-finding?

Problem-Finding

Basically, you need to find someone's pain to relieve it. You should be like psychotherapist when you're in search of an idea.

Many developers try to solve their own problems and make similar apps one after another. Think of it, how many software developers out there that have same problems as you? Let me help you, MILLIONS. We all have common problems in living and likely some of us already came up with a solution. So please, don't make another to-do list.

But what the other thing you can do, you can ask. The answer to this question can freak you out, especially if you're introvert (like me).

Just go out and make friends!

Yes, it's that easy, but not for a software developer. Actually, it's kinda struggling for computer worms like us. But you know what? When you get use to it you'll even like it! Yes, you definitely will, because homo sapience is a social species, so it's in your nature.

Every person you meet will be some way unique and will have interests that differ from yours and problems that differ from yours. So that's your source of ideas  - people.

Actually, it's even better to find some group of people with same interests because to solve a problem you need an accurate description of it. You can't really come up with a solution if someone just telling you that one's feeling discomfort. You need to know what is the root of evil. So the more people you know with the same problem, the more information you can gather about it.

This is kind of groups I'm talking about:

• Photographers
• Artists
• Poets
• Musicians
• Language groups
• Any kind of professionals (even software devs, but only if you'll seek for a problem that isn't solved yet)

This list can be really long, but I think you've got the idea.

So when you have some group of people you should find out what causing pain to them and how do they fighting with this pain to provide yourself with some ready solutions that you can just automate.

And start to solve their problems, because this is what programmers do. But before starting development process find out if someone else already solved it and how maybe you have the better approach.

PulsePoint is a great example of this kind of apps. It solves the problem of people who are suffering cardiac arrests and can actually save a life, isn't it useful?

How To Win Friends

There is a plenty of content on this topic: books, podcasts, YouTube videos, blog posts. So I think it's better to give you a reference to best of them than trying to fit everything in one blog post section.

• How to Win Friends and Influence People by Dale Carnegie - one of the best books on the topic, I encourage you to read it several times.
• The 7 Habits of Highly Effective People: Restoring the Character Ethic by Stephen R. Covey -  this one will give you another point of view on your live and people you meet.
• Simple Programmer Blog - blog providing soft skills especially for software developers, founded by John Sonmez, this guy is the reason why I started to blog.
• Also, check out his book Soft Skills: The software developer's life manual you'll find a huge amount of useful information in this book (even if you are not a software developer).

Finally

This is not the only way to find an idea and not the easy one, though, because people will not tell you ready-to-develop idea, in most cases they even don't know what they want and your job is to find it out. But eventually, it's a fun process and you'll meet many great and interesting people.

See you next week, peace!

P.S. I personally think that if you're just starting out idea does not matter, just try to implement something that can be barely useful. With that approach, you find your feet rapidly.

How To Combine Learning And Developing part 2

Read 1'st part of this post where I talk about Learning While Developing.

Hi! Today I'll tell you about the second (and I think the right one) way of combining learning and development. This way I call Developing While Learning.

Oh wait, sounds like it is the same thing as Learning While Developing, isn't it?  Yes, it might sound like the same thing, but in fact, it's opposite. Let me explain what it all means.

The essence of Developing While Learning

As I said Developing While Learning is the opposite to Learning While Developing, so you might already guess the essence by yourself.

Developing While Learning is about creating some product while learning something. But it shouldn't be your dream project. It should be something appropriate for your level. With time, probably your learning projects will be more difficult, but when you're starting out don't go right off the bat. Even most experienced developers start with "Hello world!" app when they start to learn  new technology.

Defining a success project

When you learn something you have to define your success project. Like the end point of learning, the point where you know you learned what you wanted to learn.

This project should be something really specific because when you trying to achieve something blurry and not concrete you still don't know where is the point of success. 

Here's the example of good success project

• Weather App
• Fetching forecast data from API
• 3 activities
• Weather forecast for the week
• Details about weather for specific day
• Settings

This project used in Developing Android Apps course at Udacity (which I encourage you to enroll).

And here's the success project that can actually harm your learning process.

• An Android app

You'll never find something like this in any course at any University because it's too broad. I can build "Hello World" app and I'll be happy with it as an elephant (it's the Russian phrase, means very happy)  or I can try to build something with 3-5 killing features, bells, whistles and brilliant design and still not be satisfied with it. So be as specific as possible when defining success project.

The other reason why your project should be specific is that you can break it up into subtasks and for each subtask you can find out what you should learn to perform it. It's psychologically easier to perform multiple small tasks than one tremendous one.  

How to define your success project

I think the best way to define your success project for learning is to steal it. Yes, you read it right, just steal the idea from some app. Steal from Gmail, Dropbox, Instagram, Facebook, any app you know. Just take something for your level.  

It's sounds like reinventing a wheel, but it's actually reimplementing a wheel because to learn how to make a good wheel you should make some wheels (probably bad).

With this approach, you will not spend your time on thinking up and sifting ideas to just learn something. 

And who knows, maybe you'll make a better app than one you stealing from.

You also can implement your own idea, of course, just make sure that it's appropriate for your level and for what you want to learn.

Benefits of Developing While Learning

The most evident benefit is an experience. You're facing challenges that you will face in real development, but when you'll face it in real development you'll already have a solution for it.

Another benefit is your very own code. Anything you developed that way is now yours and you can use it any way you want. You can rebuild using your new skills you acquired or improve it some other way and publish it. You can take some parts of your code and make a framework from it or contribute to an open source framework. Now you can use it the way you want it to be used.

And last but not least benefit is that one day you can set your dream project as success project for your learning. With any app you develop your knowledge gets higher and higher, and there will be the moment when your dream project is appropriate for you as a success project so why not to try it?

Learning 4 life

Actually, I think that developer's professional life is about constant learning. Every developer learns something new with every new project (if it is not routine, of course). Some developers just know more than others, but there's plenty thing that they'll learn in their professional life.

So don't be afraid of saying that you just learning, everyone is just learning! 

Overview

So here's what we know from 2 parts

1. There's 2 ways Learning While Developing and Developing While Learning
2. Learning While Developing is not as good as may seem (but it's still a way)
3. Developing While Learning is beneficial and actually fun!
4. Define your Success Project! (you can steal it, nobody will know ;) )
5. Make it as specific as possible! 
6. Have fun learning!

That's pretty all you should know about combining learning and developing.

See you in the next one, peace!

How To Combine Learning And Developing part 1

I think there are two ways of combining these two things, today I will tell you about one of them Learning While Developing.

The Example of Learning While Developing

Consider you have the idea you passionate about, like a web or mobile app that solves all peoples problems at once. So you want to implement it as fast as possible, but you don't have much knowledge about the app development. So you decide to start developing and just learn new things while doing your app.

So basically, it's about this approach, you have something you really serious about and you
don't have much knowledge about how to do it.

Is it a good approach?

First of all, let's find out the reasons to do things that way

1. You're really passionate about your idea.
2. You are afraid that somebody can "steal" your idea and implement it while you still learning.
3. You want to do it as fast as possible. 
4. You think it'll be a great success.

And now let's find out is it a good approach.

I'm absolutely sure that it's not. I had an experience of doing things that way and I didn't finish any of projects that started with this in mind. The reason, I think, that a big idea requires big efforts to develop. And when you know nothing about how to develop your idea into a product it requires even more efforts. 

Don't be delusional

Last 2 reasons to do thigs that way are delusions because of the first reason. When you're passionate you can't be pragmatic and evaluate your possibilities.

You'll can't develop your idea fast if you don't even know how. You'll spend most time Googling things and always reworking your old code because you learned how to make it more effective. You'll end up transferring your project from one framework to another because you "need" that "cool feature". And then your passion will end and you just move to another great idea. But when you already have some experience in the field you can decide what tools you should use to meet your goal.

But why great success is a delusion if there's such a great idea? Because for users, quality is more important than an idea. Don't forget they don't know that your app can solve their problems until they actually use it on a regular basis so the only way to estimate your app is quality but you can't provide it yet.

What if somebody will develop a similar app? Actually, I think it's not a bad thing. I even think when you're starting out it's a good thing. Because you have an example of how your app should work and you can focus on how to implement it and improve it instead of thinking about every small detail in your own app. Also, someone who has the same idea and has skills to implement it will do it faster and better than you anyway. Picasso had a saying he said "Good artist copy, great artist steal". (by the way, I stole this phrase from Steve Jobs)

I will tell more about similar apps in one of my future posts.

The right way to combine learning and developing

So there is the other way to do that, and I will tell you about next week in the second part of this post so stay tuned.

See you in the next one, peace! 

How I made my first Android (also Java) app

Every moment when you do something for the first time is truly unforgettable. So my first Android app was not an exception and this blog post will not be the one.

The event

It was about half a year ago on VL Hackathon #4, a local hackathon provided by great people, mostly volunteers. Hackathon lasted for 48 hours and for this time these people treated us as well as they could.

Of course, I was not alone, there were two teammates Vasiliy Nikiforov and Peter Nazarov who are also in my study group. If you think that we already knew what to do and how to act on hackathons you're totally wrong, that was our first one.

Actually, we didn't even know how to use Android Studio!

But we picked the idea, not the best one (actually, I think one of the worst ideas we could pick :) ) , but the easy one, that  idea which we could implement within 48 hours without any knowledge about Android Development and with only one member of our team who knew Java at some decent level, it was Peter.

The idea

Our idea was an app about quotes, primarily motivational, so you can motivate yourself throughout the day (yes, I know, it's embarrassing for me to tell it every time). You can upvote/downvote existing quotes and even add your own! Not the best, but appropriate for our level.

The process

These 48 hours are unforgettable for me. By the way, I came on the hackathon with the flu so the pills were my breakfast, lunch and dinner, but I was so excited so I just didn't notice my illness. It was 48 hours of googling, reading and coding (and about 4 hours sleeping), it was incredible 48 hours.

Me and Vasiliy

These 4 hours of sleep

The result

But not everything was like in a fairy tale.

Most of the features of our app were implemented just about 2 hours before the end and debugged in the moment before the presentation. Here what it looked like at presentation:

You can add your own quote!

Never do screenshots like this. Use demo mode!

Favorited quote.

It was really embarrassing to present our because it was really bad implemented and we knew it but we did it! We just did the best we can in our situation and we knew that the second time will be better, and third time even better than the second.

We didn't pursue result, but we did pursue the process. I think that to achieve some results you should go through the process and if you do it again and again, results will be better and better.

The people

Actually, the coolest thing about this event that I meet a bunch of great people with whom I stay connected even now. Not only tech guys, there was the cosplay band who invited me to do the cosplay photo set about Scott Pilgrim and I was the Scott Pilgrim!

Perfect match!

So this kind of events can provide you with the connections you don't even think about. Why are you still reading this? Go find any and participate!

Summary

So what I want to say with this post is don't be afraid of failure, just do what you want to do and if it doesn't work as you want don't worry too much, You are just starting out it is not the end of the world (this is, actually, the reason why I'm writing this post right now). So just go and do something you was afraid to do, and show it to people!

See you in the next one, peace.

P.S if you want to see the code check out my GitHub.