README.md

My Toolbox

Because others will share in my work, I must ensure that the work I produce guides my team toward good practices by making bad practices difficult

Pragmatically, development is a never stopping process of reviewing previous decisions and making improvements.

Global npm

• npm-check-updates

Developer Focused

• Engineering Values - Alt Version
• Broken window theory
• Go faster, slow down
• Every developer should be an architect
• Boy Scout Rule
• YAGNI

Team Focused

• Scrum Dysfunctions

Code Reviews

• Code Review Guidelines
• Pull Request Etiquette

Principles

• Clean Code Fundamentals
• Aha Programming
• Naming clarity and brevity
• Iron Triangle

Best Practices

• React Folder Structure
• Javascript Naming
• Conventional Commits
• Utility helpers are evil, sometimes neccesary
• PascalCase, camelCase, and snake_case
• Atomic Design
• React Design Patterns
• React state management

Tools

• Coolers Palette
• brew package manager
• zsh
• cleanshot

React

Getting Started

• Thinking in React
• Javascript to know for React
• 5 Best Practices for React Developers
• Component Abstraction

Components

• React component architectural attributes
• Breaking up components
• Compound Components
• const vs function

Libraries

• testing-library
• react-query
• husky
• mock service worker

Helpful Guidelines

• Stop mocking fetch
• Write tests, not too many

Blogs

• Kent C Dodds
• alligator react
• LogRocket
• reactjs

Free Courses

• Javascript to know for React
• The Beginner's Guide to React

Paid Courses

• Testing Javascript
• Epic React Dev
• Clean Code
• SOLID Principles

Azure DevOps

• Understanding Azure DevOps Pipeline Variables

Books

Dev

• The Pragmatic Programmer
• Clean Code
• The Clean Coder
• Clean Architecture
• Head First Design Patterns

DevOps

• The DevOps Handbook
• The Unicorn Project
• The Phoenix Project

Team

• Crucial Conversations
• Agile Conversations
• Debugging Teams
• Eat That Frog
• Good to Great