If you do projects, what is more important code on github or a server with working projects?

Question

Project management

I have a question that has been bothering me for a long time.
I am fond of different programming languages, at work I work as a backender in PHP, Laravel, etc. I almost never do layouts and the front, sometimes I work with the front, like an angular one, and sometimes I can get carried away with python, pearl, c and c ++.
What is more important for an employer when hiring, what is more important for a client who wants to give me an order for freelancing, and what is more important for employers to work remotely?
A web server with a portfolio project that you can read about me, see my projects, study them in action and look at the code, or just a github account with code without examples?
Code or working draft in action? But what if it's a program in C++, or in bash, or in other languages ​​not related to web development?
The opinion of team leads, even experienced programmers, is very interesting.

Answer 1

For me, working projects are more important than any code in the repository.
Because firstly, not all source codes can be made available to the public.
And secondly, the customer needs to solve the problem. The code in the repository is not a solved problem. But a ready-made working project or even a business that brings money is a solved problem.
Only indicate what part you did if you did not work on the task alone.

Answer 2

Yes, bullshit for the back is all)) the portfolio makes sense only for the draftsman. the contribution of the rest is not visible to the naked eye. more important is what's in your head and the ability to sell yourself.

Answer 3

The most important thing is your ability to communicate and know the specifics.
And the ability to communicate is even more important than your ability to code.
In addition, there is a lot of legacy code or MVP, how to show it?
Eventually. Update your resume so it's at least a little bit up-to-date. Keep a blog, and constantly practice presenting yourself and your code. Keep acceptable code in open repositories so that purists do not immediately start hating you.
Tell customers not about frameworks, but about real tasks, and tell them in the form: it was bad, and what I did to make everything better.
IMHO
PS for HR, make a list in general from everything you know, and break it down into categories:
HARD
SOFT
WEAK

Answer 4

A successful project/active git profile can be a disadvantage when looking for a full-time job.
A good open source can bring a customer who needs improvement.
In short, everyone needs hungry and brilliant. And if a person has other sources of income, then
he has no patience until a brighter tomorrow

Answer 5

It must be either