#100daysofcode Day [004 && 005/100]
Today I finally pulled together and refactored my code, took the time to develop pseudocode and a flow chart and put everything down on paper. From that blossomed success, I finally finished project 0 for @cs50. I learned alot more then I though I would. When I started the project I looked at it as a joke in the sand box considering it was in a kid friendly environment. I was quickly humbled with several refactors and bugs.But overall I learned that programming is the art of solving problems by breaking those problems into smaller more manageable ones.
I learned that programs are a list of instructions that solve a certain problem. These instructions are a series of scripts that are composed of statements (a line of code that commands a certain task). Statements are made of operators, variables, events, conditions, and functions. Overall I'm stoked with my progress. To me, it mapped out the ABC's of programming and showed me the basics.
An easier way to set default parameters using ES6!
What is your favorite feature of ES6? I think mine has to be template strings. Destructuring and property shorthand is pretty awesome too!
What an important step that @microsoft is acknowledging how big tech has impacted Seattle residents. It is pledging $500 million toward affordable housing to help alleviate the housing crisis they’ve played a part in creating AND pushing local government for pro-housing zoning and law changes. •
This is the the company’s largest pledge in its 44 years. The Seattle pledge break down is as follows
• $250M toward loans for low-income housing across the region
$225M in loans for middle—income housing on the Eastside
$25M in grants for homeless in the metro area •
For our Senior Technical Coaching Fellow @maxcellw being able to empower others is what makes it all worth it. "I remember I didn't have the understanding in code going through University myself and I hope to act as a role model of how we can take our journey and impart the knowledge in ways that is accessible and empower others with strong ways of building connections with their knowledge." 💙🌈🧮
Day 14 😊💪
Still trying and learning
About React native. Its so interesting and easy, is crazyyyy. These new technologies are only focused on frontend and we do less and less backend, thats an interesting change on development.
Looling foward to tomorrow!! ❤
Writing code another developer can understand is an art. If you’re like me, when you write code and revisit it again months later, you often times forget what exactly it’s doing. Imagine being in the shoes of someone who didn’t write it. If it contains a lot of for loops and non-descriptive variable names, they probably won’t have any idea how exactly it works at a quick glance.
As a result, over the past year, I’ve been evolving my coding style to include higher order functions and principles of functional programming and abstraction. The idea of abstraction is to use vocabulary that corresponds to the problem being solved. In this case, since I’m multiplying by number, the function name multiplyBy is most fitting.
Higher order functions are basically function that operate on other functions. The multiplyBy is an example of this because I’m altering the function that gets returned with the parameter that is passed in. Writing code this way is easier to understand and makes it a lot more reusable!
Is this something you all put to practice?
So we went through a bunch of Web Basics. So let’s put that to the test. Give this algorithm challenge a try using what you learned!
Hints: Look at my past Web Basics post 👀
Solution will be shared on Friday 💪
➡️➡️ Follow @samanthaming for weekly Web Development Tidbits 🌟🌟🌟
Spent great amount of time fixing some bug with ESLint and nutxjs. Hopefully is fixed. Almost finish my es6 exercise.
Today the first post about arrays. Is a series of posts about all I have been learning that you can see in my Github/guides and soon will have a app supporting that. You can also help and add your tutorials and docs there. See my pinned twitter to learn more
Our students have just begun week 2 of their 12-week journey to becoming software developers. One student - Seth - shared some thoughts on what it's like to take the road less traveled. ⠀
"Everyone is always looking for a launching pad or a big decision that is the difference between their optimal self and calamity. We are looking for these life changing moments too frequently. Our decision to sign up for the program was our life changing moment. That was our “two roads diverged,” and we all chose the path less traveled. These next three months will be a series of thousands of smaller choices. With the analogy of walking the path, decisions like not watching television so you can focus on your work or asking questions about things you don’t understand are the equivalent of putting on sunblock or eating a meal on the trail. You’re already on the trail. The choices you make while on this trail affect your health when you arrive at the next major fork. We’ve already made the toughest choice in this whole situation. We decided our current situation wasn’t cutting it, so we left stable jobs, took out loans, sold stocks, and put friendships, familial relationships, and romantic relationships on the back burner. We chose into a path that’s darker, filled with brambles, and pretty narrow because after we had long talks with our friends, family, and ourselves, we understood that this path isn’t something that we couldn’t handle. Now we just have to choose to eat meals and keep our laces tight, so we can arrive to the next fork with stamina and clarity."⠀
"The most important thing a student can do to get a job as a developer, is to be a great developer. When we combine their stellar technical skills with a compelling personal narrative and their passion for code, employers will take note, and students will end up in jobs doing what they love for a living.” - Head of Career Services Gretchen Jacobi 😍👍
Like my previous post, if you’re used to writing for loops and forEach to check if an array passes a certain condition, the filter function is another useful one to transition into. It accepts a callback function that gets called on every element and keeps the element if its true and removes it if it’s false. It also returns an array so you don’t need to worry about mutating the original array or declaring another one like my other examples.