This time
** I would like to write for those who have learned the Rails tutorial but are struggling to create a portfolio (original app) **.
(I think it will be helpful for those who go to school.)
·24-years-old ・ March 2020 Started programming learning ・ June: Portfolio creation started Portfolio Github ・ From July to present, I am working on contract development while changing jobs to an engineer.
That's simply because the ** Rails tutorials don't teach you how to create a portfolio (original app). ** **
In the first place, the Rails tutorial is ** a good teaching material for understanding the structure of Rails **. (Probably school materials)
In fact, I myself worked on portfolio creation shortly after finishing the Rails tutorial, but soon stopped.
So, I would like to introduce the ** 3 steps ** that I have practiced.
1.Refer to the portfolio of inexperienced people who are changing jobs
2.Make anyway
3.Have an active engineer see
Most people who are changing jobs publish their portfolios and Github repositories, so let's take a look at both.
** Most of the code is simple and written **, so if you have a good understanding of Rails tutorials, you should be able to understand it.
There are a lot of features (gems) that aren't mentioned in the Rails tutorial, so you can see what features you can implement in Rails.
I actually learned about the search function (Ransack) and login function (Devise) through other portfolios.
It can be simple, so let's make it anyway!
The first service I made was ** "A service that allows you to post which gym you want to do muscle training in which part" **. To be honest, the result is terrible. (If you want to see it, please look for it on my Github w)
However, ** finding out what you do not understand or solving various errors on your own ** cannot be experienced without actually moving your hands.
As a point, let's write a ** mockup ** before making it!
So ** I will make it for the time being! ** Limited to this.
This is the most important thing!
It's okay to be told, "What are you saying when you're writing for self-taught people!", But ** it's really important to have an active engineer see you ** crying
There is a limit to the ** that you can find out what you do not understand, or you can solve various errors by yourself **, and it takes a lot of time.
The portfolio mentioned at the beginning was created by self-education by myself, but when I modified it based on the feedback received from active engineers, it was evaluated quite ** in casual interviews **, so those who are doing their best on their own , Let's get reviews from active engineers for beginners!
I went to an online salon and got reviews, but it would be nice to post it on Twitter etc.!
I wrote it for beginners, so it may not be very helpful to many people.
I myself didn't know what to do when I was self-taught, so I hope you find this article helpful!
Next, I'm thinking of giving you some technical difficulties in creating a portfolio!
Recommended Posts