| // run from the command line with: | |
| // javac PalindromeTester.java && java PalindromeTester | |
| public class PalindromeTester { | |
| public boolean isPalindrome(String input) { | |
| // your code here | |
| return false; | |
| } | |
1.On a website, what is the purpose of HTML code? HTML describes the structure of a web page.
What is the difference between an element and a tag? Tags are the characters between the brackets p /p, whereas the element is the opening and closing tags, as well as the content between them.
Why do we use attributes in HTML elements? Attributes provide additional information about the contents of an element in name/value pairs.
Describe the purpose of the head, title, and body HTML elements.
As a songwriter, empathy is critical. Being sensitive to my own emotions and to the emotions of others is crucial in turning emotions into chords and lyrics, and without empathy, I would be unable to do this at all. Empathy is also what turned me into a vegetarian when I was fourteen, after I felt simply awful about shooting a deer with my grandfather. Because of empathy, I am more sensitive to the emotional state of others around me (even "others" when they are animals) which helps me in my relationships with other people, and has made me a healthier person with better ch'i because I refuse to eat meat.
Google Everything This one is very important. It sounds kind of obvious at first, but it truly is an essential skill for any job in the tech world. Specifically, learning WHAT do google is a skill that I have gotten better at, but still could get even better at. I think the key is learning to think more like a search engine, in that you become much quicker about thinking of the right phrases to google, instead of asking google a dumb question and expecting the algorithim to find the perfect answer immediately. I really like the "10 tab rule" in the article and will begin implementing it at once!
Understand that code is cheap Indeed, it is just pixels on a screen and the effort that goes into typing them. It's really easy to get stubborn and prideful when you can't quite seem to make any headway in a project. When you have put all this time into working on solving a problem, it can be hard to recognize you have taken
In-Class Reflections Using the Signature Themes Report
Read through the definitions:
Context: "You must discipline yourself to ask the questions and allow the blueprints to emerge because no matter what the situation, if you haven’t seen the blueprints, you will have less confidence in your decisions."
Went with absolute positioning. Trickiest thing was getting rid of the margin.
Think I got it pretty good: the question I had about this one is how responsiveness changes it, though I know we haven't gotten to responsiveness yet.
Strengths and Storytelling
My strengths have been evident since I began Turing, though I don't always see them manifest as strengths, necessarily. In Turing life, the most applicable are Context, Intellection, and Learner. Context as in I need to see everything contextually to understand it (big picture), Learner because I do enjoy learning, and Intellection, where my mind is constantly humming, but not always in a productive manner.
I have been using github issues to keep track of what needs to happen as far as features for my projects. Using a DTR was also particularly helpful.
For mod2, I have started to implement using waffle.io to expand my project management prowess.
Date of feedback conversation: 10/12/2017
How did you prepare for the conversation? Reflecting over the project and how each person participated in the project.
How did the conversation go for you? What was easy about the conversation? What was more difficult? I had a great group to work with on this project. Working in a larger group, communication is always a concern; however, we communicated really well. Giving feedback was easy because after working together and communicating through our project we were able to communicate our feedback as well.
Having a background in music as a bandleader, I learned how to work well in a team, especially because musicians can be particularly challenging in their temperments. Because of these experiences, I am really interested in what makes a team work well. Part of this is knowing when to take initiative and lead, but also knowing when to be a good team member is equally crucial. Whether scheduling tours or encountering a problem while recording, I learned how to solve challenges as a team. I used to think that programmers were loners coding alone in basements, but the more I learn about the craft of coding, the more I see that it is a group of people working together to solve a common problem. I fell in love with solving problems as a team, and I got into software development to solve problems of a technical sort in a similar fashion. Learning to code didn't come as naturally as music did, but because of that, I learned how to really be tenacious in overcoming obstacles. For me, tha