3 best pieces of advice ever
These are the three best pieces of advice ever.
These are the three best pieces of advice ever.
The command npm install is used in the Node.js ecosystem, particularly with the Node Package Manager (npm). It performs several key functions related to installing and managing dependencies for a project.
An open-source component library optimized for fast development, easy maintenance, and accessibility. Just import and go—no configuration required.
200+ of the most important questions — from building user interfaces in popular front-end frameworks to system design.
A - Action: Stop thinking, start doing! L - Learning: Knowledge is power, keep absorbing! C - Confidence: Believe in yourself, you got this! H - Humility: Stay humble, stay hungry! E - Enthusiasm: Tackle challenges with energy and excitement! M - Majestic Dreaming: Dream big, aim high! I - Innovation: Embrace new ideas, stay fresh! S - Strategic Thinking: Plan smart, execute smarter! T - Tinkering: Connect, refine, and make it happen!
Join Jecelyn and special guest Barry as they dive deep into the world of the bfcache and how it can make it lightning-fast to navigate around web sites. Learn how to optimize your site for the bfcache, and discover powerful debugging techniques to troubleshoot any blocking issues. Make sure your users are benefiting from this free web performance boost!
All-in-one markdown editor, collaborative canvas, and diagram-as-code builder
😍 CSS Style 😂🤣
In this post we're going to focus on the ways that a single load balancer might distribute HTTP requests to a set of servers. We'll start from the bottom and work our way up to modern load balancing algorithms.
Strong personalities seem to more effortlessly be able to do this. How do I develop a stronger personality? Keep reading for some practical tips.
I remember when my first mentor told me about Test-Driven Development. A great methodological approach to software engineering. It took me just a few minutes to understand what it was and how it worked. Then I spent the next six months actively not practicing it. TDD is hard when you start, so you just... don't.
Trying to decide between compute options on AWS? Learn about 7 popular compute services and how they compare in terms of Abstraction, Setup, Reliability, Cost, and Maintenance. We cover EC2, ECS, Fargate, Lambda, Lightsail, ElasticBeanstalk, and AppRunner.
I’m consolidating a list of prep materials that helped me land the frontend engineer position at MANNG. There are tons of awesome resources out there. Below are the ones that I found extremely useful.
As an author, value your reviewer’s time. For respectful code reviews: • Review your code yourself first • Break up large change-lists / PRs • Automate the easy stuff (linting, formatting) • Narrowly scope changes • Respond graciously to critique • Minimize lag between rounds of review • Artfully solicit missing information • Communicate responses explicitly • Don’t forget the docs. Good documentation contains context that is missing from the code. It’s doesn’t just repeat it. • Discuss things upfront where it makes sense to. Design docs and team meetings can be great for aligning on API semantics, implementation details etc. prior to the code review and can avoid exceptionally long review cycles. As a reviewer, check that code is… • Required. Is the code needed? • Well designed (e.g. how well do the various pieces interact together and the system as a whole?) • Readable by others • Doing what the author intended (and is the intention good for both end-users and maintainers?) • No more complex than needed (e.g. can it be understood quickly? are folks very likely to add bugs when modifying it?) • Commented with the why vs. what (explain why code exists vs what its doing if possible) • Following the style guide (ideally automate enforcement, code with major style changes (e.g. reformats) should be kept separate) • Has appropriate tests that are designed well • Sufficiently documented in the same PR (keeps the docs fresh, and helps explain what you're doing) ...and keep code reviews constructive! • Comments should be about the code, not the developer. • Programming skill evaluations don’t belong in code reviews. • Don’t ask condescending questions. Common examples of the genre include “Why did you do this?” • Write clear and specific comments. • Include positive feedback. • Avoid overly nitpicking. Lean on automatic style checking for this. • Let computers do the boring parts • Settle style arguments with a style guide • Start reviewing immediately • Start high level and work your way down • Be generous with code examples • Frame feedback as requests, not commands • Tie notes to principles, not opinions
Communication is one of the most important skills to develop in any career, but above all, one of the key skills to succeed in leadership roles. However, effective communication implies assertive communication. — A key component for engineering leaders: Say the right thing at the right time, in the right way.
The Chrome DevTools Performance tab is packed full of features that let you audit page performance in depth. This article explains how to use it to profile your site and interpret the results.
In every successful web page load, some critical components and resources become available at just the right time to give you a smooth loading experience. This ensures users perceive the performance of the application to be excellent. This excellent user experience should generally also translate to passing the Core Web Vitals.
Caching headers are one of those deceptively complex web technologies which are so often overlooked or misconfigured. The fastest request is the one that is not made, and caching headers allow us to tell browsers when they can reuse an asset that they have already downloaded.
Jenn, an Indeed Career Coach, explains the top leadership styles in management and how to identify the one that's right for you and your team.