You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the current vision you have for your career. What are the values that will drive your job search? What are your goals for your job search? What kind of role do you see yourself pursuing in your job search? Being able to provide for myself and future family. To become part of a company that influences gaming or entertainment. A Jr Development role for frontend or backend or fullstack.
Based on what you wrote above, please write a refined summary statement for your professional story:
I am Software Developer who is passionate about creating useful and polished applications. I have been interested in development since my younger days of surfing the internet on AOL.
Please list the top 3-5 industries and companies you'll pursue in your job search as of right now.
Twitch.tv
Crunchyroll
Reddit
Funimation
What is the Stack data structure? What are the rules of interacting with a Stack?
The stack is a fundemental data stucture that follows the FILO flow.
What is The Call Stack? How does it work?
Call stack is the order you computer processes your code. An example if you called a method and within that method you declare a variable, calling the method goes in the stack first then the variable declaration. The process of setting the variable as the last thing in happens first then the method being finished happens second
What is a return value, in terms of The Call Stack?
The final product of an operation.
When an error occurs, how does Ruby create the Stack Trace?
When there is an error Ruby throws an exception and the stack trace leading up to that error in the console.
Week 4 has been pretty cool. I'm constantly amazed at how much data manipulation backend learns in mod 1. So many of these concepts I didn't hear about until mod 2 during the front end program. Though I do understand that there isnt the need to focus on DOM manipulation so just getting use to the difference. Was super happy to get an interview this week. Backend is creeping closer to my love of front end but I dont know if I will get the creativce fufillment like styling the front end side.
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
Working on a larger team, practice collaboration
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
De'Marcus - Experience and documentation reading
Matt- Efficient coding and quick in executing needed solutions and implementation.
Project was interesting. I enjoyed rendering the board (Gave that good ole front end feeling) and I really took the time to practice TDD. I also really tried to take my role as a sort of mentor to my partner and I tried helping him learn new concepts and would have him explain lines of code to me to make sure he understood what everything did. David was very receptive to feedback and was a pleasure to work with. Great project for learning alot of new methods.
This week has been benificial in multiple ways. It has made me confident as a developer that I can take my previous understanding of JS and apply it to other languages. The amount of enumerables is mindblowing and I feel like Ruby was built with more thought than JS. The biggest thing I'm learning is where to initiate code where I expect the user to respond. After speaking with Dione it makes alot more sense where it should go and why. The instruction has been great and things I didn't even think about like 0 being truty in Ruby when I'm use to it producing a falsey in JS connditionals is something i know whould have gotten me hung up.
My group started off with a really good DTR. Everyone knew exactly what everyone else had planned going into the first weekend. The front end was utilizing PR Templates and it made it really easy to understand what had changed and what would be affected.
What didn't go well?
Once there was a pivot, we did not come back together to nail down exactly what needed to happen with the new direction. There was conflict in what was important for the MVP as far as prioritizing testing over styling. Some members felt like others were not having there input considered and it was turning into a boss/subordinate dynamic. As crunch time approched we did less and less detailed PR's.
What can you take with you to the work place to be a better communicator?
I definitely got better at creating a detailed PR and having the 'conversation' in the code review. Also whenever there is a change in direction, I understand how crucial it is to reestablish all the details necessary for the new direction. Worki
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters