MichaelDimmitt

Material UI has a resources section: https://m2.material.io/resources

Where they publish a figma baselining design kit
Along with a dark mode figma baselining design kit

Storybook for material react table: https://www.material-react-table.dev/

Quickly scaffold an extension using: https://code.visualstudio.com/api/get-started/your-first-extension

VS-Code, UI architecture and elements for vscode extensions.

Sourced from: https://code.visualstudio.com/api/ux-guidelines/overview
^ the overview has additional items, that I might build out in another document.

Rewriting this here because I just want an at a glance reference.
Where it is a thing and then an image and I can scroll through it all.

globalRenderCounter

In different parts of the codebase add:

// file1
countRender('render1');
// file2
countRender('render2')
// file3
countRender('render3')

U.S. Web Design System (USWDS) Research

My favorite component so far from USWDS

https://designsystem.digital.gov/components/in-page-navigation/

Templates: (404) (Documentation) (Landing) (Authentication) (Form) (Landing page)

https://designsystem.digital.gov/templates/authentication-pages/create-account

Fork your own instance of the publicly published USWDS figma:

https://www.figma.com/community/file/836611771720754351

Status: Test has not been completed.

Things to test, to learn how to speed up a typescript lsp.

If config file is at root of project:

only open the folders that you will be working in for your editor.
is it smart enough to know to only check that folder?
does number of files open in the editor matter?
does it matter if you have multiple config files? (one in each folder)

a. The test ... make a significantly annoying typescript project.

React hook form notes, How the watch function works:

Summary:
The watch operator uses .subscribe function that creates a generator. That generator progresses forward by next() being called. This then gets evaluated to see if a re-render needs to occur and gets passed to useState.

useWatch():
useWatch.ts#L68
useWatch.ts#L184

Note: uses a syntax similar to a generator, when .next is called it executes a callback function that triggers updateValue from the useState.

My Thoughts: Guidelines for Code Reviews

Does anyone have a document they follow for having guidelines reviewing code within a team?

I read through this document today and it was helpful for this task:
https://github.com/mawrkus/pull-request-review-guide?tab=readme-ov-file

Different ways developers can review a pr

sanity check (confirm it looks good and logs are on the pr, tests are written or a checklist followed)
devs should check this themselves but it sometimes slips.

Regarding the copy and paste pattern in development.

“A good plan violently executed now is better than a perfect plan next week.” -General George S. Patton, Jr.

When what is defined as a "good pattern" is setup And it is sufficiently complex. Be mindful that there are probably ways to automate and simplify.

But for the time being you need others to execute that pattern. Find the person who knows the pattern best and can accomplish the task most efficiently and accurately

Have a meeting with them and note how long the meeting took.

I need to fix all of my gists by moving them somewhere.

Each of my gists probably have a specific intended use.
I.e. book summaries - for helping people understand what I got out of a combination of books.

Current challenges: (what do I need?)

I am not able to quickly get to the gist by typing 'gist tmux' - to get to my tmux keybinding gist.
I need an auto generated re-arrangable table of contents. - this could be cool! drag and drop.
no preview shows when I post it in slack

	1. location
	2. proximity
	3. atmosphere conversations
	4. atmosphere meeting
	5. atmosphere
	6. coffee
	7. wifi
	8. outside atmosphere
	9. outside bugs
	10. outside chairs