JessiDevs Weekly Rundown: November 8, 2020
This week I’ve been continuing to focus on improving my efficiency when it comes to working in the front end.
Digging right on into how to effectively use Flexbox and CSS Grid is a great way to make framing up a new UI element quick!
Flexbox vs. CSS Grid: Which Should You Use and When?
Flexbox and CSS Grid are two CSS layout modules that have become mainstream in recent years. Both allow us to create…
Key article takeaways:
- “The most important thing to know is that flexbox is one-dimensional, while CSS Grid is two-dimensional. Flexbox lays out items along either the horizontal or the vertical axis, so you have to decide whether you want a row-based or a column-based layout.”
- “On the other hand, CSS Grid lets you work along two axes: horizontally and vertically. Grid allows you to create two-dimensional layouts where you can precisely place grid items into cells defined by rows and columns.”
- “CSS Grid focuses on precise content placement.”
- “Flexbox focuses on content flow rather than content placement.”
- “Flexbox treats each row independently. Different rows align flex items differently, based on the amount of text inside of them.”
- “Using the
flex-shrinkproperties, you can achieve a completely fluid layout that optimizes the allocation of flex items at every viewport size.”
Bonus: This bomb UI Card Codepen.
Angular :host, :host-context, ::ng-deep - The Complete Guide
In this post, we will learn how the default Angular styling mechanism (Emulated Encapsulation) works under the hood…
- Why isolate styles in an Angular app? “As we develop a component style suite for an application, we tend to run into situations where the styles from one feature start interfering with the styles of another feature…If we are not careful and systematically organize our styles…we will quickly run into CSS maintenance issues.”
Unlikely Optimism: The Conjunctive Events Bias
When certain events need to take place to achieve the desired outcome, we're overly optimistic that those events will…
I have worked as a marketing project manager, a product owner, and now a web developer. Something that all teams struggle deeply with is how to appropriately estimate projects. Every project I’ve ever worked on has suffered from this bias in some way. Our human tendency to be optimistic both about estimating work in the face of unknowns and in understanding the impact of setbacks is something that I am both aware of, but fall prey to as well.
- “The conjunctive events bias makes us underestimate the effort required to accomplish complex plans. Most plans don’t work out. Things almost always take longer than expected. There are always delays due to dependencies.”
- “Plans don’t work because completing a sequence of tasks requires a great deal of cooperation from multiple events. As a system becomes increasingly complex, the chance of failure increases. A plan can be thought of as a system. Thus, a change in one component will very likely have impacts on the functionality of other parts of the system. The more components you have, the more chances that something will go wrong in one of them, causing delays, setbacks, and fails in the rest of the system.”
- “The conjunctive events bias teaches us to be more pessimistic about plans and to consider the worst-case scenario, not just the best. We may assume things will always run smoothly but disruption is the rule rather than the exception.”
That’s it from me this week! Thanks for reading with me. Any articles you all would recommend I check out?
This rundown is a post from my newsletter JessiDevs! JessiDevs is a weekly, curated rundown of articles, books, and topics that will help you learn to code, keep that code clean, and learn to learn more effectively. Click here to sign up to receive updates right to your inbox.
My Recent Articles
Big Change Is Scary and Chaotic
Lean into fear and embrace not knowing. See what it has to teach you
Routing 101 in Angular 9+
A quick tutorial on using Angular routing to display your views and pass data between components