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
What role does empathy play in your life and how has it helped you?
From a young age, I have been attuned to the people around me. This allowed me to adapt to new environments as my family moved around from one country to another. Similarly when I spent a year abroad in Germany, this skillset allowed me to learn the language and adapt to the culture quickly. More then anything, I believe being empathic has allowed me a bit of a chameleon anywhere I go.
How does empathy help you build better software?
It's clear to me that the innovative sofware of tomorrow will have empathy to thank. Empathy allows for sofware to be intuitive
to the user, so their experience is flawless. A flawless experience is a rewarding experience, because there is no wasted effort.
Additinally as our reliance on technology increases, being able to maintain a human experience while simultaneously adding a new technology/tool to
imporove our everyday lives will become critical.
What is your greatest strength and how do you know?
My greatest strength is empathy. It has been the desire to understand and be understood that's been ever present in my life, and is the reason I am able to adapt to differing situations. Strengths are often double-sided swords, and have a shadow aspects that form our greatest weaknesses. Too much empathy, on one hand has also made me a little cautious around certain personality types. It also makes me a little more prone to observartion than action, which depending on the situation can be both a strength or weakness.
Goals & Expectations: Increase our ability to use objects effectively. Learn to Pair and collaborate effectively.
We will know if we are succesful if we finish all the iterations and are able to earn a 3.
Collaboration Styles & Strengths and Weaknesses: A balance of paired and individual contributions that would look like
writing some code, having it reviewed by partner and refactoring together.
Overcoming Obstacles: We are both commited to finding the best approach to problems and recognize that this is better achieved
Each HTML element should be defined with an appropriate class to facilitate styling & UI
A section element will hold the larger 8 ball circle
Two articles will be within this section:
The first will contain the front of the ball (the 8) that will display upon load.
The second will contain the back which will activate upon clicking the ball and show the fortune. (will begin with hidden in class name).
The second article will contain another child element, maybe a small heading (h3 or h4), that will display the fortune.
Add a default fortune or a quick word on how the interface works
This should get us started, come back and add any additional elements as deemed necessary.
What is a "framework?" And how does it differ from a "library"?
A "framework" is essentially a set of rules that define how code within it will behave. A library is more like the code
that is actually used. In other words we may use a specific library to write code, and call on particular library features
to accomplish certain novel tasks. Ultimately, however, it will be the framework that decides how the code is
interpreted and thus executed.
Why should we consider using a framework over vanilla JS like you have been doing in mods 1 and 2?
When it comes to creating web apps on vanilla JS it is difficult to join our data state with the DOM/UI.
This gist contains a short assignment I'd like everyone to complete before our
formal lesson. The prework involves reading some of the React Router documentation,
and will allow us to keep the lesson more hands on.
Instructions
Fork this gist
On your own copy, go through the listed readings and answer associated questions
Two mocks (tailwindCSS + emotion
& theme-ui) assembled to explore CSS solutions for ReRent's decoupling.
They will remain unfinished prototypes. From our conversations and the Roadmap
shared, it seemed that Gatsby and Typescript would make up the core technologies and a CSS solution had not yet been decided on. Although familiar with CSS-in-JS
solutions, namely @emotion, I had no experience with CSS frameworks or styled systems before these mocks. The following takeaways
are opinions gathered from ~ 1 1/2 days worth of developing within each of the following repositories, some are more subjective than others and they are not in any particular order.