msell

Mr Bojangles

3/4 time 168 bpm

Use a capo any where you want or not at all. Jerry Jeff Walker uses capo on 2

IntroC C/B Am C/G x4

Verse C C/B Am C/G F F G G x2

msell

✔ Using remote iOS credentials (Expo server)

Distribution Certificate is not validated for non-interactive builds.
Skipping Provisioning Profile validation on Apple Servers because we aren't authenticated.

Project Credentials Configuration

Project                   @msell/freshy
Bundle Identifier         com.msell.freshy
                          

msell

start of the song you can omit first bar if you want to play the melody


Em Em | Em B7 | Em Em | Em Em 

Am Am | Em B7 | Em Em| C7  B7



* alternating bass (exept on Am, just hit the bass there)

msell

NPM attempt

I did experement with changing over to NPM all toghether but it had its own set of issues and in the end does not seem to put us in a better spot than we were in with yarn. Here were the steps I followed to try out NPM:

1. Update package.json to use NPM instead of Yarn commands, then run synp to create package-lock.json
2. rm -rf node_modules && npm i && npm start:web to test the conversion to NPM was successful.
3. Error running web - @sentry/types module was not found. I will reinstall with npm i -D @sentry/types but this is a red flag that the converstion from Yarn to NPM did not completely work
4. After installing @sentry types I can confirm the web version and the native versions still work.
5. Using expo-cli@5.4.8 run expo upgrade
6. The interesting thing here is that the output of expo upgrade indicates that they delete the package-lock.json file and node_modules as part of the upgrade process. This seems like it could be problematic. Once the upgrade was complete I ran `np

msell

Key of A

A Major Scale

1	2	3	4	5	6	7	Octave
A	B	C#	D	E	F#	G#	A

Diatonic chord progression - A Major

msell

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

msell

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

msell

  
  const noMechanicsAssigned = (context, event) => {
    return context.mechanicsAssigned < 1
  }
  
  const caseMachine = Machine({
    id: 'case',
    initial: 'open',
    context: {

msell

Route	Duration	Miles	Things to do	Notes	Nights
Fairview to Little Rock	4h 45m	313	things with kids	We dont need to spend the night here, we could spend the day here then drive to Memphis at night to stay.	0
Little Rock to Memphis	2h 10m	137	tour, BBQ, Riverboat Cruise	Tour looks really good, riverboat could be good too	1
Memphis to Nashville	3h 15m	212			1
Nashville to Atlanta	3h 46m			This would be an alternate route instead of going to Birmingham	1
Atlanta to Destin FL	5h 11m	315			2
Destin to New Orleans	3h 57m	252			2
New Orleans to Shreveport	5h	327

msell

React development has always had a bit of a choose your own adventure experience. By that I mean there are a LOT of choices to make in any react app. Other frameworks are much more prescriptive in how you build applications. You won't get very far down your adventure before you must make some choices in how you handle data and state within your application. React components can have state using setState in a class component or useState in a function component. That along with context is really all React gives you out of the box. Over the years there have been countless state management solutions that have risen and fallen in popularity. Have a look at React State Museum to see about 20 of the most popular approaches over the years. There was a time where it looked like Redux was going to be the clear winner and for maybe a couple of years it did seem like every enterprise react app was built with redux. It's sort of fallen out of favor in recent years. Over the