惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
阮一峰的网络日志
阮一峰的网络日志
WordPress大学
WordPress大学
博客园 - Franky
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
H
Help Net Security
T
Tailwind CSS Blog
L
LangChain Blog
J
Java Code Geeks
Stack Overflow Blog
Stack Overflow Blog
云风的 BLOG
云风的 BLOG
T
Threatpost
Project Zero
Project Zero
D
Docker
I
InfoQ
Recorded Future
Recorded Future
Help Net Security
Help Net Security
L
LINUX DO - 最新话题
小众软件
小众软件
Engineering at Meta
Engineering at Meta
宝玉的分享
宝玉的分享
Google DeepMind News
Google DeepMind News
M
MIT News - Artificial intelligence
雷峰网
雷峰网
The Cloudflare Blog
T
Tenable Blog
Recent Announcements
Recent Announcements
PCI Perspectives
PCI Perspectives
T
The Exploit Database - CXSecurity.com
GbyAI
GbyAI
Schneier on Security
Schneier on Security
Webroot Blog
Webroot Blog
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Y
Y Combinator Blog
P
Privacy International News Feed
T
Threat Research - Cisco Blogs
A
Arctic Wolf
The Hacker News
The Hacker News
B
Blog RSS Feed
Security Archives - TechRepublic
Security Archives - TechRepublic
C
CXSECURITY Database RSS Feed - CXSecurity.com
Spread Privacy
Spread Privacy
Latest news
Latest news
Blog — PlanetScale
Blog — PlanetScale
Jina AI
Jina AI
TaoSecurity Blog
TaoSecurity Blog
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
S
Security @ Cisco Blogs
aimingoo的专栏
aimingoo的专栏

CSS Wizardry

Front-End’s Missing Metric: The TBT Window Meet Your Users Where They Are with Obs.js Better Browser Caching with No-Vary-Search font-family Doesn’t Fall Back the Way You Think What Is CSS Containment and How Can I Use It? When All You Can Do Is All or Nothing, Do Nothing Obs.js: Context-Aware Web Performance for Everyone Low- and Mid-Tier Mobile for the Real World (2025) The Fastest Site in the Tour de France Making Sense of the Performance Extensibility API Why Do We Have a Cache-Control Request Header? HTML Is Not a Programming Language… Build for the Web, Build on the Web, Build with the Web Licensing Code on CSS Wizardry A Layered Approach to Speculation Rules Designing (and Evolving) a New Web Performance Score Core Web Vitals Colours The Ultimate Contract Templates for Tech Consultants: Protect Your Business and Get Paid Optimising for High Latency Environments Cache Grab: How Much Are You Leaving on the Table? blocking=render: Why would you do that?! Correctly Configure (Pre) Connections The Three Cs: 🤝 Concatenate, 🗜️ Compress, 🗳️ Cache What Is the Maximum max-age? How to Clear Cache and Cookies on a Customer’s Device The Ultimate Low-Quality Image Placeholder Technique Core Web Vitals for Search Engine Optimisation: What Do We Need to Know? The HTTP/1-liness of HTTP/2 In Defence of DOM­Content­Loaded Site-Speed Topography Remapped Why Not document.write()? Speeding Up Async Snippets Critical CSS? Not So Fast! Measure What You Impact, Not What You Influence Optimising Largest Contentful Paint Measuring Web Performance in Mobile Safari Site-Speed Topography Speed Up Google Fonts Real-World Effectiveness of Brotli Performance Budgets, Pragmatically Lazy Pre-Browsing with Prefetch Making Cloud.typography Fast(er) Time to First Byte: What It Is and How to Improve It Self-Host Your Static Assets Tips for Technical Interviews Cache-Control for Civilians Bandwidth or Latency: When to Optimise for Which ITCSS × Skillshare What If? CSS and Network Performance The Three Types of Performance Testing Getting to Know a Legacy Codebase Image Inconsistencies: How and When Browsers Download Images Identifying, Auditing, and Discussing Third Parties My Digital Music Setup Measuring the Hard-to-Measure Finding Dead CSS The Fallacies of Distributed Computing (Applied to Front-End Performance) Ten Years Old Relative Requirements Airplanes and Ashtrays Performance and Resilience: Stress-Testing Third Parties Refactoring Tunnels Little Things I Like to Do with Git Writing Tidy Code Configuring Git and Vim Base64 Encoding & Performance, Part 2: Gathering Data Base64 Encoding & Performance, Part 1: What’s Up with Base64? Code Smells in CSS Revisited Typography for Developers Moving CSS Wizardry onto HTTPS and HTTP/2 Ack for CSS Developers A New Year, a New Focus Preparing Vim for Apple’s Touch Bar Choosing the Correct Average CSS Shorthand Syntax Considered an Anti-Pattern CSS Wizardry Newsletter Nesting Your BEM? Improving Perceived Performance with Multiple Background Images Continue Normalising Your CSS Pure CSS Content Filter Pragmatic, Practical, and Progressive Theming with Custom Properties Refactoring CSS: The Three I’s Speaker’s Checklist: Before and After Your Talk Improving Your CSS with Parker The Importance of !important: Forcing Immutability in CSS Mixins Better for Performance Managing Typography on Large Apps White October Events Workshop Partnership BEMIT: Taking the BEM Naming Convention a Step Further Travelling Like You Want to, When You Have To Contextual Styling: UI Components, Nesting, and Implementation Detail Subtleties with Self-Chained Classes Cyclomatic Complexity: Logic in CSS Immutable CSS Can CSS Be Too Modular? More Transparent UI Code with Namespaces When to use @extend; when to use a mixin The Specificity Graph CSS Wizardry Ltd.: Year 1 in review
CSS Wizardry referral scheme
Harry Roberts · 2014-08-05 · via CSS Wizardry

Written by on CSS Wizardry.

Table of Contents

Independent writing is brought to you via my wonderful Supporters.

  1. Terms

Since I began working for myself late last year, one thing has been very apparent: the majority of my work with companies comes about because of individuals within that company. Designers or developers who follow my work, my articles, or my talks, who then go and suggest to their boss(es) that they get me in to run a workshop, or help out on an initial sprint or two’s work, etc.

I’ve always been very grateful of this, and as a result, I’m setting up a (very informal) referral scheme. Any individual within a company directly responsible for that company hiring me will receive a $50 (USD) Amazon voucher. Not a huge amount, but a simple, small thank you.

Terms

Terms and conditions will be very informal, because that’s just how I prefer to do things. I want this to remain a nice, simple way to say thank you to people who help me out, so I’d rather it didn’t become a formal, rule-based system to be gamed. Loosely, they will be along the lines of:

  • Only one gift voucher per engagement: only one person can receive one, not a whole team.
  • There won’t be any online booking system or referral code: just ask the person who emails me to mention that you sent them.
  • Vouchers will be paid once an invoice has cleared: for hopefully obvious reasons.
  • It only works if the engagement comes off: no vouchers for introductions that lead nowhere, naturally.
  • It should work for most types of engagements: but any oddities or exceptions will be dealt with as best as I can. For a workshop or development project, sure; for an hour of advice over Skype, probably not.
  • Referrals cannot be back-dated: I’m sorry, but it’s for engagements from here on in only.
  • Things are subject to change: within reason. If USD50 all of a sudden becomes worth GBP1,000, I will have to go back to the drawing board.
  • Any unusual circumstances will be dealt with on a case-by-case basis: if there are any grey areas, we will discuss them together.

But if you have any questions, please just fire me an email: csswizardry@gmail.com.

An example of a cut and dried introduction eligible for a referral reward:

Hi Harry,

Sarah, one of our front-end engineers, has asked about getting you in to run a workshop with our team. Have you got any availability over the next two months?

Thanks,
Josef

Yay, go Sarah! You may have just earned yourself a $50 Amazon voucher.

I really hope this works out, as it exists to say a genuine, grateful thank you to the individuals responsible for me having such a varied and fun job!