I hereby claim:
- I am jk1dd on github.
- I am yooserguy (https://keybase.io/yooserguy) on keybase.
- I have a public key ASAytaqQDyMZpiCzu2m1vDRMjT0UdJa3lYq9A3BxxDBFNgo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
List your longterm goal(s) of what you want to accomplish by the end of module 4
In this section, break down your longterm goal into smaller goals that you want to work on each week and/or day
22 March 2017
To prepare, I took notes on what I wanted to communicate (in a pattern of Open, Body, and Close), and then took a break - returning to review them at a different time, better able to see my comments from anothers' perspective, and hopefully made my impact match my intent more closely. I also double-checked that everything I said would be Specific, Actionable, and Kind.
The conversation went well - the hardest part was the build-up before the actual event. Once I was communicating and seeing that I was being well recieved, I relaxed more and was able to say everything I wanted to say, in the way I planned to say it.
This module marked the first time we have used a defined Project Manager during the projects. This helped with managing the larger size of project groups (4 students). In both big projects, we had daily stand-ups and retros to check in on progress and to make sure everyone stayed on the same page. This was beneficial both to learning and getting the projects completed - no one was stuck on a problem too long, and the project proceeded in a logical way.
We primarily relied on Agile methodology, focusing on the minimum viable product sort of iterative process, then using the extra time we had (sometimes!) to go back and extend and improve what we had done.
We also used various PM tools (waffle.io) and communication techniques to work as effectively as possible, and focus on constant improvement (even when things were 'pretty good').
To concatenate something is to mash it together. link to picture This would be important for performance - allowing the asset pipeline to be more streamlined, loading faster
Precompiling alters (arranges?) your assests so they can be served as quickly and directly as possible. This involves coffeescript and sass as they are two things that can be precompiled (?).
I am thirsty to know more and know what I can do better. I am constantly learning, both about programming and about myself, and applying it immediately. I am appreciative of the support of my peers on projects, and I make it known. I communicate and take responsibility for what I say I will.
I seek to make sure everyone on the team is involved and ideas are all examined. I am attuned to everything that has to get done on a project, and I am willing to discuss it openly with my teammates.
Sessions, Cookies, and Flashes
Since HTTP is stateless, it would be difficult to give the user feedback on whether they successfully interacted with the database. It would also not be possible to save settings, shopping carts, or other information between requests.
A cookie is a key/value pair, acts like a hash but it isn't really. It is stored in the user's browser and sent with each request. It is often used to store things like simple preferences settings, where a user left off on the page, and other non-sensitive information. They have an expiration date, or can be set to be cleared when the browser closes (I think).