I’ve been practicing some commands that I normally don’t use.
Some Sublime text shortcuts:
Legend
⇧ – Shift
⌥ – Alt
⌃ – Control
⌘ – Command
↵ – Enter
| Cut line | ⌘X | ||
| Go to matching parentheses | ⌃M | ||
| Insert line after | ⌘↵ | ||
| Insert line before | ⇧⌘↵ | ||
| Move line/selection down | ⌃⌘DOWN | ||
| Move line/selection up | ⌃⌘UP | ||
| Select all contents of the current parentheses | ⇧⌃M | ||
| Select line – repeat to select next lines | ⌘L | ||
| Select word – repeat select others occurrences | ⌘D |
Ruby Procs And Lambdas (And The Difference Between Them)
I had a hard time wrapping procs and lambas around my head but found this awesome article!
“Don’t Believe Anyone Who Tells You Learning Code Is Easy” – TechCrunch
‘…The most common state for a programmer is a sense of inadequacy.”
I believe it. There is so much to learn and the learning never stops. And of course, someone will always be a better programmer than you are. It’s all good though…I can’t wait until Dev Bootcamp and being able to be on the same learning path as those around me. I am mentally preparing myself for the feelings of frustration and discouragement that I know I’ll face while I’m there.
I have been going on the “Pre-Phase 0” materials whenever I get the chance. Dev provided a couple links that you can read to test your learning mindset and determine what your best learning technique is. I’ve written some notes about “Fixed Mindset vs Growth Mindset”and also about the VARK learning styles.
Fixed Mindset vs Growth Mindset
– Reaching your potential is not about ability
– It’s about looking at ability as something inherent that needs to be demonstrated or developed
– It is possible to change from one view to another
– Intelligence, like a muscle, grows stronger through exercise.
|
Fixed Mindset |
Growth Mindset |
|
– Intelligence is static |
– Intelligence can be developed |
|
– “I am the way I am” |
– Believe that the brain is like a muscle that can be trained. |
|
– Avoid challenges – stick to what they know they do well |
– Leads to a desire to learn |
|
– Give up easily |
– Embrace challenges |
|
– Effort is viewed as fruitless or worse |
– Persist in the face of setbacks |
|
– Ignore useful feedback |
– Obstacles do not lead to discouragement |
|
– Feel threatened by the success of others (convince themselves and others that the person’s success was due to luck) |
– Self-image is not tied to your success and how you will look to others; failure is an opportunity to learn, and so whatever happens you win
|
|
Result: plateau early and achieve less than their full potential |
– Effort is necessary to grow and master useful skills. => Effort leads to mastery |
|
=> deterministic view of the world |
– Learn from criticism. |
|
|
– The success of others is inspiring. |
|
|
Result: higher levels of achievement and greater sense of free will. |
The VARK Questionnaire – How Do I Learn Best?
This questionnaire is a guide to learning styles.
My scores:
Visual: 7
Aural: 10
Read/write: 12
Kinesthetic: 12
So my interview was last Friday, 5/16. I was nervous and scared. But at the same time, I HAD to do well. I never wanted anything so badly. I had read through tons and tons of blogs and forums for tips on how to prepare. I consulted a friend who had gone through the program himself. Basically, be confident and be passionate. The rest will follow.
From the day I was notified that I was getting an interview with Dev to the actual interview day, I studied Ruby like a maniac. I wasn’t GOOD at it, I just STUDIED it. Keep in mind that Ruby was all new to me, but the Java fundamentals helped. I went through Codecademy up to the Refactoring level, as suggested by Dev. Another friend of mine, who was a CS major and is a software engineer suggested writing code on paper. Forget the editor. This helped a lot as well. When I did use the editor, I ran the code that I wrote in Codecademy through the terminal to see if it worked. This helped with my understanding as well. It makes a world of difference. It also makes you learn terminal commands if you don’t already know it.
Ok, so the interview itself:
– Jumped straight to a logic problem (5-10 mins). I probably can’t tell you exactly what it is, but Google some logic problems and practice them. It’s OK that you don’t get it right in the interview as long as you “talk out” your logic process. After the interview, I thought about the logic problem some more and had the biggest DUH moment ever. It’s ok, I let it go.
– 2 Ruby coding questions. The interviewer takes you to a collaborative real-time coding platform. They ask you 2 simple questions. Again, if you do the Codecademy track, you really should be fine. But be over-prepared, just in case.
– They’ll ask you why you want to do Dev over all the other schools. If you watched the youtube video that they told you to watch, and reflected on it, you should know the answer. Be passionate about why you want this.
The very next day, I got an email with the subject line “Congratulations!” I don’t think it hit me at that moment. But I realized that this could change my life forever. I’m so freaking happy. I’m still happy. But there’s more work to be done. Hope this post helps you guys!
I thought it would be beneficial for both myself and others to make a blog about my journey towards becoming a software developer. I’m just a regular girl who needs all the help she can get to become a software developer and be happy in a career that she loves and cares about.
Pre-Dev:
I had an epiphany about 7 months ago just before I started my application for grad school at Boston University. I needed/wanted a better, more satisfying job. I kept thinking to myself “This really can’t be it.” I naturally thought getting an advanced degree was the answer. For me it was. In October 2013, I was admitted to Boston University’s Distance Education Master’s in Computer Information Systems. This was probably one of the happiest days of my life. It was my second chance, my opportunity to get further in my career. I was slated to start January 2014 and I am now 2 courses in. I’m currently taking Quantitative Methods for Information Systems (not a calculus fan..) but my first class was the one that really reeled me in. The second half of that course taught me basic Java. To me, there was nothing more amazing than writing code that worked and did what I wanted it to. And that was just baby Java….It would be awesome to be good at Ruby one day. Working on it!
So basically, I work full time, am a part-time grad student and am working to prepare myself for Dev Bootcamp in October!
My post about my Dev Interview and prep is next!
girlcoderblog 