A Months Worth of "Today, I Learned:" -- Learning Ember on the Job

I Got My Dream Job:

No, seriously. I did. 
Since about a month and a half of learning how to code, I've been applying for a particular position at a particular company every three months and repeatedly getting shot down. I chalked it up to not having quite enough experience. So, I kept learning and growing and gosh darn it, I talked to someone who worked there, built a prototype of an app on Codepen and then created it in EmberJS (together, a total of 13 hours of non-stop coding since I had absolutely no knowledge on Ember) and hoped for the best. Lo and behold, they thought I was a decent enough fit and I couldn't be more grateful!

But just because I got my dream job doesn't mean the work stops there. In fact, I'm pretty sure it gets harder. So, I've made it a habit to write down something I've learned every single day on the job even if it is extremely small. This is a day in the life of a junior developer making her way to meeting new people, working with a new team, understanding monoliths, and growing as a developer!

Success is to be measured not so much by the position that one has reached in life as by the obstacles which he has overcome
— Booker T. Washington

The things I've learned in the last month are because I ran into troubles accomplishing something efficiently. Each day that I learn something new makes me a faster and more efficient developer.

  • WebStorm hates monoliths
    • Do your research when coming into a job. Your perfect IDE or editor for one job isn't necessarily the right one for another.
  • The importance of using a calendar and understanding how schedules work in a company.
    • Making sure you're not only added to the calendars but also the lines of communication is going to assure that you don't miss out on company information!
  • How to toggle using only CSS
  • Naming conventions in projects change depending on the architecture, framework, and company.
  • Semaphore (integration) testing is amazing and horrible like the great and powerful Oz -- useful but also terrifying.
  • How to create a component in Ember
    • There will be a separate blog post on this entirely. Stay tuned
  • Using an #each helper isntead of using map
  • Making components with props and when to use yield
  • How to pass on global attributes or computed properties
  • No matter how good you think you are at CSS, you can always have a day that you suck at it.
  • Update your computer at home and not at work.
    • updating at work takes up unnecessary time that you could be coding.
  • The Ember documentation is pretty spiffy
  • Running Meetups and getting your footing at a new job can be a nightmare.
    • Learn how to balance out all of you learning.
  • Get a task, complete it, and move on.
    • If the task or story takes too long even after you've researched it, asked questions, and even done some peer reviewing, it isn't worth it. Come back to it later.
  • When in doubt, always consult the UI/UX team
    • They know what they're doing. They've done research to prove that where that button is is where it belongs. Give them what they want.
  • Choose your words carefully.
    • You never know who could be listening.
learningJenell Pizarrojob, dream