I’m working through a 6-hour-long video series which covers such topics as Big O notation, algorithms, data structures, etc. : Basically, the nitty-gritty stuff that we didn’t cover in DBC.
First, a very simplified was to determine Big O –
n : If you have a single loop, your function is O(n).
n-squared : If you have nested loops, each additional loop adds one to the exponent. So, a loop in a loop would be n-squared; a loop, in a loop, in a loop, would be n-cubed, etc. These are bad news.
1 : If you have no loops at all; you go in, perform an operation, and get out, your big O is O(1).
log(n) : If you’re using any kind of recursion – or divide and conquer – your big 0 is O(log n)
On to the next lesson!
I received my first callback today. It’s from a third-party staffing firm regarding front end and back end positions that they’re trying to fill. My imposter syndrome and overall awkwardness have me doubting my ability to land a job this quickly, but worst case scenario, this will at least be good interview-practice for me. In order to prepare for my meeting with them on Friday, I need to refresh some of my SQL and Rails skills. I decided to devote tomorrow to those two tasks, since the recruiter specifically mentioned them as requirements for their open positions.
Thursday, I have the hour-long mock technical interview that I scheduled through the firm that DBC contracts with. That should also be good preparation for the real thing on Friday. Other than that, I’ll spend Thursday during the day at the maker space, brainstorming the Raspberry Pi project with the guys there.
Overall, I’d say it’s been a productive 4 days out of DBC: Signed on to two volunteer jobs, got free membership at a maker space, met a handful of great folks in the industry, and scheduled my first job interview.
Also, this arrived in the mail today.
The cold that’s been developing for the past few days has finally knocked me over. I’ve got meetups all week that I’m going to try to drag myself to, but it’s a struggle to focus on anything at the moment.
Some good news though:
The co-founders of the maker space I visited yesterday have asked me to work on a project with them. They currently have a live web-feed of their space and want to add a new feature: using a Raspberry Pi, they want to keep up-to-the-minute track of who is in the space at any given time. This will allow members to check the list online in order to see if there’s anyone in the space that they’d like to meet up with. It sounds like a fun idea and I’m excited about the opportunity. I’ve never worked with a Raspberry Pi before, but I’m getting giddy over the chance to. Plus, this will be a good opportunity to learn new things, expand my skills/resume, and meet some cool people.
In other news:
I talked to the man yesterday about the other volunteer project that I was interested in working on. My plan today was to spend much of the day looking over the APIs they’re using and the code he sent me, but my illness is making that difficult. Regardless, I think I may be in over my head with his project. I’m going to be upfront with him about the fact that I’m a junior dev and there will be a considerable learning curve. I’m eager to give it a shot and help in any way that I can, but I worry that his expectations of me are too lofty for what I can actually deliver.
Sitting at a coffee shop in the Merchandise Mart, trying to figure out how to get the most out of the (potentially) lengthy period of unemployment that I’ve just entered. It’s my first day after finishing career week with Dev Bootcamp. I’m sure I feel like most others in my situation do: optimistic, enthusiastic…terrified, overwhelmed. What if I’m not cut out for this? What if my passion isn’t enough to turn me into a quality coder? What if, during my period of unemployment, I completely forget everything I’ve just learned? What if every potential employer I encounter recognizes that I’m a huge fraud who’d never even heard of the command line up until a few months ago?
After considering what the heck I should write about, I decided I’d focus on the new things I’m learning and the journey I’m going through towards making a huge career change. The journey from complete amateur who’d never heard of the command line to someone who is worthy of employment in web development.
Rather than sit on my couch and code, I found a local “maker-space” where I could sit around other people and code. Since it’s my first visit, I got a tour of their equipment. Side note: my transformation into a techy must be in full effect because I found myself genuinely interested in the gadgets they have (3D printer, Raspberry Pi – among other things I’ve forgotten the names of).
I sit surrounded by sawdust and power tools I’d be too afraid to use, while a few programmers sit around me and work on their own projects.
This is a great space!
Hone my PHP skills.
The volunteer position I’m interviewing for this afternoon is built in Codeigniter with PHP. While I’m comfortable with the basics of PHP, I worry I’ll be in over my head taking on a large project built entirely in it. I’m working on preparing myself for the opportunity though.
After a productive morning of PHP, Apache, and job-hunting, the owners of the maker-space invited me to join them for lunch across the street. It is admittedly intimidating trying to keep up with the conversation of people who, combined, have likely been programming for longer than I’ve been alive. It was great getting to know others in the industry though. Once I get passed my imposter syndrome, I could see this becoming a good niche for me – something I’ve never felt in other job before.