Anuradha Kumari anuk79

## matrix-trailer-red-1440-minute-urls.txt
As noted by @murdats below, there are more URLs than just these 1440 ones, depending on the argument values
that are hashed (as the filenames below are MD5 hashes of a few arguments: red/blue pill color, HHMM time, etc.)

You can read details about the algorithm used to generate these URLs here:

https://news.ycombinator.com/item?id=28448335

---

00:00 https://thechoiceisyours.whatisthematrix.com/generated/v7/high/d43725991d28ffcab04aa716762cf6af.mp4

## package_manager_post_glossary.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              8 stars
            
          
                MattGoldwater
                / package_manager_post_glossary.md
            
            
              Last active
              November 8, 2022 04:20
            
          
    My definitions below refer to how these terms are most commonly used in the context of software engineering.
Package 
A folder that contains any number of files and folders. It's not just a folder because it must include one file with a standard name.  This file varies depending on the package manager and language. For example, npm requires this file to be named package.json. If you're using python its typically _init_.py. 
The contents of the required file aren't standardized across languages or package managers. Typically, this file makes it it easier to use the package. 
A package.json file typically will contain information such as who created the package, who else is allowed to use the package, what other packages must be installed to use the package and scripts typically to run the program, run tests and more. You can read npm's package.json docs here.

  
## tatiana-mac-speaker-rider.md

      
              1 file
            
          
              42 forks
            
          
              19 comments
            
          
              305 stars
            
          
                tatianamac
                / tatiana-mac-speaker-rider.md
            
            
              Last active
              March 24, 2024 12:22
            
              
                Tatiana Mac's Speaker Rider
              
          
    Speaker Rider

by Tatiana Mac
Last updated 14 April 2021
What is a speaker rider?

As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.
Considerations

😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.

  
## index.md

      
              1 file
            
          
              35 forks
            
          
              46 comments
            
          
              272 stars
            
          
                bvaughn
                / index.md
            
            
              Last active
              May 4, 2024 11:25
            
              
                How to use profiling in production mode for react-dom 
              
          
    React recently introduced an experimental profiler API. This page gives instructions on how to use this API in a production release of your app.
Table of Contents

Profiling in production

Create React App
Webpack 4


Profiling in production

React DOM automatically supports profiling in development mode for v16.5+, but since profiling adds some small additional overhead it is opt-in for production mode. This gist explains how to opt-in.

  
## index.md

      
              1 file
            
          
              13 forks
            
          
              38 comments
            
          
              315 stars
            
          
                bvaughn
                / index.md
            
            
              Last active
              April 3, 2024 07:41
            
              
                Interaction tracing with React
              
          
    This API was removed in React 17


Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

  
## router.html
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>Building a router</title>
  <script>
    // Put John's template engine code here...

    (function () {
      // A hash to store our routes:
	As noted by @murdats below, there are more URLs than just these 1440 ones, depending on the argument values
	that are hashed (as the filenames below are MD5 hashes of a few arguments: red/blue pill color, HHMM time, etc.)

	You can read details about the algorithm used to generate these URLs here:

	https://news.ycombinator.com/item?id=28448335

	---

	00:00 https://thechoiceisyours.whatisthematrix.com/generated/v7/high/d43725991d28ffcab04aa716762cf6af.mp4
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>Building a router</title>
	<script>
	// Put John's template engine code here...

	(function () {
	// A hash to store our routes: