Week one of prework
Thanks for checking out my blog, it is currently being worked on. My hardest past so far was using my machine locally to initialize the repository. Once I got the repo set up, I created a readme file with only a header.Then I added in a gitignore from the wrong directory somehow, so I had to go back and fix that later. After got those two files added locally, I pushed up to github. Once I had an understanding of adding, commit, pushing and pulling, I started to add a few extra files.
I've added an html document that I have been able to implement! I also added a few images from my computer just to test it out. Finally I removed the wrong gitignore, and added the right one in the proper place, and updated the readme.
An "aha" moment I had was setting up the initial repository on my local machine, but that's integral for understanding web development. After I had the terminal properly configured, I was able to move forward with git upload, and from there started my blog. I think the coolest thing I've learned so far is the terminal commands, they can be used on almost any system.
Week two of prework
Thanks for checking out my second week worth of work, this week I spent my time learning the fundamentals of html and css. It has definitely been a challenging week, implementing skills I had literally just learned. But that is the exciting part about this bootcamp; learning on the fly. My favorite part was adding in the nav bar on my top right corner, that made my blog feel like it had more depth.
What are your thoughts on pseudo coding?
I have some experience previously with pseudo coding. I took a class in computer science that didn't use computers... But it absolutely helped me with the process that goes into thinking about how to effectively write code the machine will implement correctly. I understand that properly writing code helps with the end result, because theres a million ways to get the same result, but some are better than others.
What are you struggling with?
I'm having trouble with CSS, but I'm sure with experience I will eventually get the hang of it. I'll have to look for more resources on it, or find a way to use the documentation and implement it in a live fashion, to see the changes. I'm open to any suggestions on CSS tutorials or training, because I had a hard getting getting the CSS Comprehension ID card finished, and I'm sure it could be better done.
What are you excited or eager to learn more about?
I am excited to continue to learn designing websites, making my blog more personal was very fun. Learning more CSS and getting comfortable with it will only make my blog more animate and alive. Java will also be exciting to implement in the webpage, i'm intrigued to see next weeks work, but hesitant because I'm weary with CSS at the moment.
"Aha" moments have been in short supply this week.. I was able to get through HTML with relative ease, but CSS has thrown me through the ringer. While I was able to finish all the assignments, I stumbled through the CSS without a true understanding of the work. Hopefully as I continue to work over the weekend I will have more of an understanding.
Week three of prework
What are your thoughts about the roles HTML, CSS, and JavaScript play in the process of rendering content and providing user experience?
They all work in with each other to produce the full experience for the user. With only html the page would be very basic, with only css you'd have style and design to the page but no content. Finally, Javascript executes all the script on the page so that he user will have a dynamic experience on the website. I'm excited to see how Javasript will continue to play an important job in our roles as a web developer.
What are some objects that your blog incorporates?
Right now I don't believe my page incorporates any objects at the moment. I'd like to add a live twitter feed embedded in my main page, along with a search bar, so I can searh through all my content in the page and find anything relative. I'd also like the make my nav bar sleeker and more modern with an eternal scroll function.
Week four of prework
What was one thing you liked and disliked about each of the new topics covered in prework?
All around I found the prework to be very beneficial to the progress of my wed development career. Prework alone forces you to search for the information and figure out how to come up with the right answers on your own. The hardest part would be actually combing through the information/documentation. Referencing the documentation is the best way to make sure that your code is right, and through time you will become more confident.
What was helpful?
Every introduction topic we helpful with exposing you to content, and slowly getting you to manipulate it more and more until you have a basic understanding of how the process works.
What hindered your progress?
Being alone was both a benefit and a hinderance. By being alone you are forced to rely on yourself to get the answer, but also left you to continue or develop bad practice if not properly corrected. Syntax and logic can easily be messed up, and alone it is easy to get yourself possibly stuck.
How did you overcome challenges?
The help channel on slack was a great help. Every one was very active in problems they experienced, and if you had the same issue, someone else probably had the issue a swell.
Week One in Class
What did you learn about that helped you understand more about design?
Bootstrap is a design godsend. The ability to quickly throw css onto a page without much modification is amazing, giving me the opportunity to make a completely responsive and stylized page in less than a day. The C.R.A.P. principles of design are also important to think about when creating the page, actually giving you rules to use so that a page is much more professional.
What do you want to continue learning about that helps you understand design better?
The more I can learn about utilizing bootstrap, the more fleshed out and stylized my designs will become. I'll have to keep referencing the documentation on getBootstrap to keep finding.
What Design aspects are important to you as a user and as a developer?
proper spacing, symmetry, proper color deviation, and proximity are all very important to make a page actually look styled properly. As a developer I strive to make my page look as flush and easy to read as possible. As a user, having a hard time reading a page or misunderstanding the layout will do nothing but cause me to leave the page immediately.
What is the number one thing that held you back this week? Why?
I would say the number one thing holding me back on my first week of coding would be is figuring out how to design a page, that looks modern and not like its been up since 1997.
What is one thing you would like to get better at in bootcamp?
I would like to get better at making my websites as responsive as possible. In todays day and age, if you cannot access a webpage on any device then it will not survive. People use their phones, apps, ipads, laptops, TV's and more all have access to the internet, and all of them should be able to access them.
Week two in Class
What did you learn about that helped you understand the development process?
Psuedo-code has helped me understand the grand scope of developing much more, by allowing me to take a step back, and access what I need the code to do in a basic level, and then how to implement it with the right questions.
What does it mean to develop good code?
I believe writing good code means to make the most out of the least code, and have your code accomplish the task at hand as efficiently as possible.
What does it mean to be a good developer?
A good developer does not repeat themselves, they keep it as dry as posible,and to get the best possible product with your least amount of time invested. Repeating and development make your work redundant.
What is one thing that programmers hate doing?
Not to sound like a broken record, or to miss the point or anything, but I think that developers hate repeating themselves. Working harder than needed to get the result intended is against the morality of a developer, IMO.