Meet Brian Love 🧑💻
Brian is a software engineer and Google Developer Expert in Web Technologies and Angular with a passion for learning, writing, speaking, teaching and mentoring. He regularly speaks at conferences and meetups around the country, and co-authored "Why Angular for the Enterprise" for O'Reilly. When not coding, Brian enjoys skiing, hiking, and being in the outdoors. Brian recently launched lookout.dev where you can find best practices and expert advice on topics ranging from TypeScript, Angular, React, Node.js and more.
My Stats 🏆
My Contributions 💪
Use Const Assertions in TypeScript to enforce readonly properties of literal expressions
Should I use type prefixes or suffixes?
Use Feature Policy Headers to disable browser features
Enforce HTTPS using Strict-Transport-Security Header
Avoid Using Dependencies with Known Vulnerabilities
Avoid Importing Sass StyleSheet Multiple Times in Angular
Use Number Constants over Magic Numbers.
Use numeric separators for large numeric literals
Prefer Template Literals over String Concatenation
Use Tree-Shakeable Providers in Angular
Protect Class Members and Expose Only the Public API
Allow for Type Inferencing Where Appropriate
@importCSS using a URL
Prefer Interfaces over the use of the
anytype or large inline object types
It is unnecessary to specify
publicmodifier for TypeScript class members
@scopePaths for Shorter Import Paths Configurable in tsconfig.json
Specify Access Modifiers for TypeScript Class Members
Do not use