Skip to content

Instantly share code, notes, and snippets.

View machikoyasuda's full-sized avatar
🦺
beep

machiko machikoyasuda

🦺
beep
365 followers · 1.7k following
View GitHub Profile
@machikoyasuda
machikoyasuda / diy-e-bike-conversion-readme.md
Last active August 24, 2023 20:19
diy-e-bike-conversion-readme.md

D.I.Y. E-bike conversion

image

Components

  1. Front G311 Kit - Front wheel pre-laced with geared hub motor - $300
  2. Motor controller, C4820-GR_Higo - $100
  3. Thumb throttle, attached to handlebars - $15
  4. G311 Torque Arm, attached to front dropouts - $20
@machikoyasuda
machikoyasuda / goma.md
Created June 23, 2020 03:21
goma.md

IMG_20200505_082945

@machikoyasuda
machikoyasuda / keybase.md
Created March 1, 2019 21:27

Keybase proof

I hereby claim:

  • I am machikoyasuda on github.
  • I am machiko (https://keybase.io/machiko) on keybase.
  • I have a public key ASBwbr2yXvrcUWgtlolidybifKmyqCT3NFYg2OdCV3E9tQo

To claim this, I am signing this object:

@machikoyasuda
machikoyasuda / gist:72fd0ed2dcb867deb4bca48e4e4e1616
Created March 1, 2019 21:26
keybase.md
### Keybase proof
I hereby claim:
* I am machikoyasuda on github.
* I am machiko (https://keybase.io/machiko) on keybase.
* I have a public key ASBwbr2yXvrcUWgtlolidybifKmyqCT3NFYg2OdCV3E9tQo
To claim this, I am signing this object:
@machikoyasuda
machikoyasuda / ready-for-development-design-checklist.md
Last active October 1, 2018 23:42

Ready for development checklist:

Once design mocks include these cases and scenarios, the Development team will be ready to start writing a ticket and working on the code for it:

  • UI States: The mock should include what the various UI states look like, including:
  • Active
  • Complete
  • Incomplete (ex. Validating data)
  • Blank/Empty data state (ex. No credit cards found)
  • Disabled
@machikoyasuda
machikoyasuda / ready-for-development-design-checklist.md
Created October 1, 2018 23:19

Ready for development checklist:

Once design mocks include these cases and scenarios, the Development team will be ready to start writing a ticket and working on the code for it:

  • UI States: The mock should include what the various UI states look like, including:
  • Active
  • Complete
  • Incomplete (ex. Validating data)
  • Blank/Empty data state (ex. No credit cards found)
  • Disabled
@machikoyasuda
machikoyasuda / ready-for-development-design-checklist.md
Created October 1, 2018 23:19
Ready for Development checklist

Ready for development checklist:

Once design mocks include these cases and scenarios, the Development team will be ready to start writing a ticket and working on the code for it:

[ ] UI States: The mock should include what the various UI states look like, including: [ ] Active [ ] Complete [ ] Incomplete (ex. Validating data) [ ] Blank/Empty data state (ex. No credit cards found) [ ] Disabled

@machikoyasuda
machikoyasuda / testing-markdown.md
Last active January 30, 2018 22:07

diff

 var remark = require('remark');
 var report = require('vfile-reporter');

 remark()
+  .use(require('remark-preset-lint-recommended'))
   .process('_Emphasis_ and **importance**', function (err, file) {
 console.error(report(err || file));
@machikoyasuda
machikoyasuda / index.html
Created November 6, 2017 22:08
Reaction Commerce: React Guide // source https://jsbin.com/liwagi
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>Reaction Commerce: React Guide</title>
</head>
<script src="https://fb.me/react-15.1.0.js"></script>
<script src="https://fb.me/react-dom-15.1.0.js"></script>
<body>
@machikoyasuda
machikoyasuda / wsc-los-angeles-2017-projects.md
Last active July 16, 2017 04:19