Why should you dig into Github

Why should you try Github?

When I was looking for a job in my senior year, I tried to find a job related to hardware and Internet of Things (PS: Majoring in electronic information Engineering). Even though your resume is full of experiences, it’s not really useful. After a couple of on-campus job fairs, out of ten resumes, not a single one was sent out — the school rejected them outright. I don’t have any interest in the bully face. A swift horse needs a bole. Later, I joined Martin Flower’s company, but that’s another story.

It’s a cruel world, and most of the additional skills you gain in school are useless if you’re not handsome or tall. If you don’t have a reputation at work, it can affect how well you get paid at your next job. Github is one of many things that could change that.

My story with Github

I signed up for Github when I was a sophomore. When I got familiar with it, I was a senior. It has been a year since I graduated. Over the past two years, I’ve tried to create projects on Github in a few dimensions:

1. Quickly start the framework to combat, that is, demo
2. Refactor someone else’s code
3. Create your own usable framework
4. Build large applications quickly
5. Build a common framework

Making and harvest

First, let’s talk about the harvest that has nothing to do with skills. My graduation project is “Minimum Internet of Things System”. Considering that our professional teachers have no knowledge of this aspect, there will be problems in the defense, so I try my best to get closer to this aspect. By the time I graduated, the project had over a hundred stars, so something that is easy to pick up is still welcome (ps: however, such hardware-related projects are usually limited by the few hardware developers on Github).

A month after graduation, I received an email from PACKT Publishing (ps: They found me on Github) about reviewing a book on the Internet of Things, namely “Learning Internet of Things” mentioned in “From Review to Translation OF IT Books”. To review an Internet of Things book in English as an “Internet of Things expert” with no passing level 4… Of course, later is the review finished, the book has my English introduction.

A month ago, I received an email from MANNING Publishing (ps: also on Github) about reviewing a catalogue of books on the Internet of Things and making suggestions.

And that leads to other things, which of course are not the subject here. We won’t talk about harassing emails or Chinese cooperation here. I never imagined that I could have a small world in the English-speaking world.

What this tells us is, find a Github theme that you’re good at and you’ll get a lot of calls.

Making and growth

Having written about how to Improve Yourself on Github in the past, I just want to say three things:

A project that doesn’t have tests is pretty stupid, unless you have a project that only has one function, and that function returns Hello World.

If your project has thousands of lines of code and if you can guarantee 95% test coverage, then I don’t think your project will have too many complicated functions. If there is such a function, it is covered by tests.

If you’re working hard on the project, you’ll see bad code and try to improve it, refactoring. When you have some, your skills will continue to improve. You start experimenting with more things like stubs, mocks, fakeserver.

One day, you will find that you can’t live without testing.

Then they believe that any project that doesn’t write a test is playing hoodlum

This is all about what we can reap, and the fact that we’re trying it means that we know it might be good for us. There are already many examples of how you can improve yourself, but here are the others.

Convenient to work

We can get different knowledge, content and information from it. Everyone can learn from other people’s code, and when we need to build a library we can look for different libraries and code to implement our functions. For example, when I’m implementing a library, I’ll go to Github with the corresponding component:

• Promise to support
• Class (PS: Not a good way to use a Class)
• Template is a simple Template engine
• Router controls the routing of the page
• Ajax Basic Ajax Get/Post requests

Get a job

More and more people are getting jobs on Github because they’re doing what some companies are looking for. So when they’re looking for code, they’ll try to invite them.

As a result, it has been a trend to find suitable candidates on Github.

Expand your professional

If we want to create a better, more powerful framework, knowing more people can be more helpful. Sometimes it will have the same effect as the one above.

other

In fact, this is also a topic of influence. Only by increasing your exposure can you have the opportunity to reach more people.

Github project analysis

For Github, you don’t need to create a great framework, you just need a good theme, or you need a good Demo. Visually, the most popular libraries in China are all kinds of Android and iOS.

Having analyzed some of Github’s user behavior, let’s start with Github’s Star. (Deadline: 23:00, March 9, 2015)

As long as there are these types

• Libraries and frameworks: andjQuery
• System:Linux,hhvm,docker
• Configuration set: for exampledotfiles
• Auxiliary tools: e.goh-my-zsh
• Tools:HomewbrewandBower
• Data collection: e.gfree programming books.You-Dont-Know-JS.Font-Awesome
• Others: Resume asResume

A good theme can easily be popular in the short term, and a library mainly depends on long-term growth unless there is high exposure.

other

My Github: github.com/phodal (ps: has been hit 316 days, welcome to share.)