It's appreciable how you chose to have your own portfolio. I liked the overall color theme and quality of your portfolio. I liked your projects section as well, especially the links to the Github repo, and the apps are really good. Just two things:
One:
This is in reference to Whatsapp & Music Player projects/
Try to add more details in the Readme of the repository, explaining what the project is all about, what problems it solves, and so on. This would be really helpful, when just in case your deployed applications don't launch in an office setup (for a person who is accessing your site where certain sites/ domains are blocked), in that case, information present in Readme, will help the person understand more about the application, without even launching it.
Two:
This one is from one of my personal experiences. While pushing changes to your repository, I noticed some of your commits are done in a single shot. Try to push changes (make commits granular) when it solves a bug or as the development progresses. This will be good to track the changes and understand how your project evolved (during the development process). It gives confidence to the technical recruiters that you have a good understanding of using version control tools and development
I actually planned on doing the readme for them and got sidetracked with other things. That makes a lot of sense. I'll take that into consideration. most of the time the extra commits are cause of weird mobile bugs that dont show in responsive mode, until I view it on a mobile. Thank you for the solid advice though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's appreciable how you chose to have your own portfolio. I liked the overall color theme and quality of your portfolio. I liked your projects section as well, especially the links to the Github repo, and the apps are really good. Just two things:
One:
This is in reference to Whatsapp & Music Player projects/
Try to add more details in the Readme of the repository, explaining what the project is all about, what problems it solves, and so on. This would be really helpful, when just in case your deployed applications don't launch in an office setup (for a person who is accessing your site where certain sites/ domains are blocked), in that case, information present in Readme, will help the person understand more about the application, without even launching it.
Two:
This one is from one of my personal experiences. While pushing changes to your repository, I noticed some of your commits are done in a single shot. Try to push changes (make commits granular) when it solves a bug or as the development progresses. This will be good to track the changes and understand how your project evolved (during the development process). It gives confidence to the technical recruiters that you have a good understanding of using version control tools and development
Wish you all the very best!
I actually planned on doing the readme for them and got sidetracked with other things. That makes a lot of sense. I'll take that into consideration. most of the time the extra commits are cause of weird mobile bugs that dont show in responsive mode, until I view it on a mobile. Thank you for the solid advice though.