Is it worth it and what developments to put on github for a future portfolio?

Question

GitHub

Is it worth it and what developments to put on github for a future portfolio? Which section? what code? with what notes and so on?

Answer 1

1. It is worth posting your classes (PHP) and libraries (JS).
2. It is worth laying out non-trivial and popular functionality.
3. A whole project of something - it's better not to spread it: few people will believe that you did it alone and this is a rather time-consuming task.
4. It is worth showing your knowledge and skills in code structure, algorithms, working with text or binary data, recursion, etc. in the code.
5. The best thing is to take the missing implementation of the required algorithm from Wikipedia in the language in which you plan to show your skills and implement it (after searching on GitHub and Google, and making sure that there is no implementation or insufficient quality).
6. You can make EVEN ONE function, but so that it is in demand and does its job better (better and faster) than existing analogues and provide a comparison table for the speed of execution of your and other similar solutions.
7. The task of the portfolio on the git is not only to show the quality of the code and knowledge of the programming language (and various approaches), but also the ability to think outside the box with the maximum possible result.

Answer 2

For me, it’s so easy to have something, moreover, as confusing as possible, so that there would be no desire to look in detail, because:
1) Write an ORM - fu bikes, there are ready-made ORM frameworks
2) Lay out a project on a framework - you yourself are nothing and didn’t write
3) Post it on VanillaJS - fu, no one writes on it anymore
4) Post it on angular - fu now everything is already on angular2 5) Post it on
angular2 - fu it’s not clear and in general everything is already on VUE
on Assembler, because few of the new generation of developers know them, they are already all mired in abstractions))

Answer 3

It is worth laying out everything, everything in general. And since this will be a public code, you should take care that it is not a code that is shameful for this stage of your development.
But in the portfolio for the employer should be an adequately small amount of solid work. You can create an organization on GitHub and move irrelevant repositories there so that only cool works are in the root account. You can create a "portfolio" repository from one readme.md and collect links to your best projects with annotations into it.
I already wrote about sorting repositories on GitHub using organizations . How do you organize your work?

Answer 4

Any code that you are not ashamed to show. In which there is no govnokoda. Well, it depends on what you specialize in. And on what, by the way? For example, you could write your own website and show the source to the future employer.