Answer the question
In order to leave comments, you need to log in
A question about training and how to design projects?
Hello everyone, there are probably guys here who hire people / participate in interviews / conduct interviews on their own. Please tell me how you evaluate the design of the code/projects of potential juniors.
The following points are of concern:
1) Is it worth licking your projects from the point of code design to the ideal. (conditionally made a project 3 months ago, you have it on github, you have already learned a lot in 3 months and know how to do it better and whether it needs to be rewritten) (I think not, it’s quite normal when a person’s development is traced on github.
2 ) In general, before an interview, when you look at the github of potential juniors, do you look at the code? or conditionally see if the project works without bugs / do you like it / what functionality does it have.
3) Also a question about the code, but in a slightly different way. If you write a project, due to the fact that there is no practical knowledge at all, theoretical mediocre, you write it slowly. You spend perhaps a month, and you understand that here and there you can do better, but here you can think of something else (there are no bugs just in terms of the design and beauty of the code). This will take about another week. Leave the code in some average state and go further, which will allow you to learn something new or finish off the existing one.
4) There are 2-3-4 good projects in the portfolio, or 10 medium ones.
Answer the question
In order to leave comments, you need to log in
Projects value their essence. That the project solves some problem. Let not the world, but something for you.
There is no need to lick the code, you just need to adhere to the standards, and then the project can be finalized at any time without subsequent re-licking.
I can look at the code of a project that I found interesting. Or look at the specific implementation of a separate moment.
To do this, the project must be completed. Not cool, but enough - readme, usage examples, purpose.
3)
That is why the project is not "and then I tried what the x library is", but a more or less finished product that solves an integral problem.
4. Yes, at least one. It’s just that the essence of the projects is that these are not educational tasks, but your personal pet projects that you decided to do for some reason and brought to a working state.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question