Things to consider: Get good at things you end up building over and over in your career

Readme.md

Lets get you good at things you end up building over and over in your career

Overall

• linters and formatters:
  add a config to enforce code standards and code style.

Manually standardizing a coding style is not worth the conflict.
If you cannot enforce it in an automated way with zero communication then you have no standard long term.

• formatter: the teams formatters must be aligned to avoid formatter override hell.
• cspell, check english spelling. (you could expose your dictionary of words on the front end too!)
  • vs-code extension, code-spell-checker - puts blue squiggles under words. (uses cspell under the hood)

Front End

• Funnels that all decisions feed through:
• A way to manage network requests
• A way to manage dates
• A way to manage colors.
• A way to manage icons.
• A way to manage images.
• A way to manage components like inputs, buttons, and calendars.

Backend

• Swagger to expose your api as a playground.
• Similar to hangfire, a dashboard that shows jobs, manual and recurring that can be managed for authenticated users.

Common things that get built over an over again.

Both

1. Forms
2. Authentication
3. Accept Payment
4. Role based authorization,
5. Image upload
6. Display data as a list and as a record. (Grids, Tables)

Backend

In the words of another programmer "Basically all I build is Crud Cycles (get post put patch delete)."
^ This comment sparked this blogpost.

Novelty

TBD

Other fun stuff

rate limiter intermediary api

Other

logging tools, a/b testing, finding performance issues.