Hi! I’ve been kinda inconsistent for the last few months with my posting. I think now’s a good time to change that. I’ve been busy applying for jobs, and while I’ve had some luck, it’s been pretty rough. I recently had one that lasted about 3 weeks, had a realistic code challenge and pair programming that simulated working at the company, and everyone I interviewed with was really nice. They really have their shit together, and every step of the process was clearly explained. That’s why it was really disheartening when I didn’t get the job. They were nice enough to give me feedback about why they didn’t hire me, and it came down to skill level. The solution is pretty clear: get better at coding. I’m armed with my digital copy of Exercises for Programmers: 57 challenges to develop your coding skills, and I plan to complete at least one exercise and one blog post about it each day.
My goals are to :
- Make my code more DRY
- Focus on OOP
- Master Ruby
- Show my work
I’ve been focusing on the Rails side of things for the last year, and I think I’ve neglected my logic and fluency work. To that end, I’ll try and explain my process as I work through this book. We’ll see how it goes.
Keep at it!
LikeLike