With a saturated market for new coders via coding bootcamps, self taught devs and university grads its easy to lose site of why you started to be interested in learning to code to begin with.
Evaluate your motivation to make sure you’re coding for all the right reasons. Don’t learn to code because you see quotes of possible salaries on Glassdoor or some blog post. Don’t learn to code because everyone else is doing it. Find the reason behind your passion so when things get tough – and they will get tough – you can remember your motivation behind it.
Some give up coding so easily because they haven’t properly explained their why. My why is because I love to create things, I love solving problems and there’s great satisfaction when I get to see a website or application I built on the web – Makes me eager to start the next one. I encourage you to think about your why and write it down – Commit it to memory so that when your up until 2 in the morning trying to solve a problem, you’re able to realize the bigger reason you are up to begin with.
The end of last week was spent doing Test Driven Development with RSpec. The idea of test driven development is to test each feature in a project, fail that test, write code that makes that test pass, repeat. Each method, each feature should be tested to ensure it works correctly.
RSpec is one of the most popular testing frameworks in rails. It can create instances of your controllers, models and views and test them, it tests whether the routes are set up properly, it tests that the request and response is received from the server and tests regular Ruby classes…It’s pretty powerful tool to have.
We used expectations in the Coding Dojo console. Mainly, expect and to…meaning expect(page).to have_text(“The Dog”) which translates to expect the page to have the text “The Dog” on it, of course this after an action has been made. It’s pretty cool that it translate to plain English.
Then there’s the describe method which is used to list what the controllers and methods are supposed to do, for instance you can ‘describe’ a CodingController by saying that ‘it’ should show all coders. When describing Controller classes and methods, you should always put in require ‘rails_helper’ so it can find the controller or method you wish to describe. We also testing the models to make sure the validations and relationships were working properly.
We were introduced to Capybara which tests the actual user expectation when visiting a page for example you can declare statements like these ‘visit “/coding/new”, fill_in ‘New’, :with => “Tiffany”
And finally we testing for features of the page for example it “prompts the user fields”
After a few assignments, I cruised to the next section.
Rejection: Everyone’s been through it and no one likes it. Rejection can have the potential to set you back but don’t let it. There’s nothing worse then applying for a position at a company that you really want to work for, going through the interview process only to find out that they’ve given the job to someone else. Of course, you thought you were the best candidate for the job but remember not every opportunity you apply for is a culture fit. So, here are my 3 ways to deal with rejection:
1. Learn from your mistakes: This is a big one. Remember your answers from your interview and take notes right after the interview, being sure to note any mistakes you think you may have made including not answering a question correctly to not smiling and being friendly to the interviewer…It all counts. Use these notes to help you in your next interview.
2. Get back out there: Today’s job market is competitive but there many opportunities out there, you just have to seek them out. If you’re anything like me, you’ve had your eye on other opportunities while you were interviewing. I do that because you never know if you’ll be a good fit for the team or company; I think of it as not putting all your eggs into one basket: Have options. Always look on job boards and communicate to people that you are interviewing and looking for roles and your new job may be around the corner. Keep applying to qualified positions and have all your experiences and resume up to date.
3. Don’t give up: You may think that it’s fate you didn’t get this gig and to just stay in the job you have (if you currently have a job) or that you should scale back to lower qualifications if you don’t have a job. Don’t ever take less than your potential. Of course, if you really need the role, you have to do what you need to do but generally speaking, settling for less is never the way to go. You may think that you should just apply for entry level roles when you have the skills to apply for senior level roles but that is not a good idea because you will not be happy with your end decision later on in life. Be hopeful and confident when you apply for positions. Know your true potential and what you deserve and strive for it but never settle for less than greatness.