judytuna
commented
5 years ago find a spot for these talks by people we like. perhaps learning about learning?
- [ ] sarah mei's "impact is the aggregate of many small changes over time" talk
- https://speakerdeck.com/sarahmei/the-insufficiency-of-good-design?slide=52
- http://www.sarahmei.com/blog/speaking/ --> "November 2012, RubyConf in Denver, Colorado. I did a keynote called “The Insufficiency of Good Design.” You can watch the video and see my slides."
- [ ] aga's LWT talk a few years ago on empathetic design. it's so good. find the link
alodahl
vegetabill
I find myself saying things to apprentices over and over again. I'm trying to write them down and maybe later I'll find a place for them to go in the curriculum.
[ ] IC vs manager track. IC in this case means individual contributor (not independent contractor). explain engineering ladder for career progression vs manager ladder. link to sarah mei's tweet about "have someone get really good at something for 18 years then do something else"
[ ] "managing up" lingo for getting what you want out of 1:1s
[ ] team structure (tech lead, 6 or 7 engineers, engineering manager, design, product manager. how you might work together.
[x] agile vs waterfall
[ ] lean startup lingo
[x] hackathons
[ ] the phrase "product market fit"
[ ] sourcetree for visualizing git
[x] lorem ipsum text, images
[ ] ask ingrid to add the sentence "bootstrap columns are like counting lego pegs" to the bootstrap lesson
[ ] challenges for various sessions, like CSS
[ ] https://github.com/htmlandcssclass/floating_block_layouts
[ ] design tools: sketch (plus plugins like stark for accessibility), omnigraffle for flow charts ($ tho) (visio on windows), invision // zeppelin (view only for devs. margin here is 20px)
[x] whiteboarding; see https://github.com/Techtonica/curriculum/issues/71
[ ] start a catch-all doc for questions to ask during interviews, like "can you tell me about how engineers work with your designers" etc
[ ] [lingo] what people mean when we talk about "resources" (people, as in "we lost resources so we didn't finish the project on time"). "expensive" as in "this is harder or takes more time to do"
[ ] pivotal tracker lesson maybe? pointing exercise
[ ] trello ... pomello (pomodoro + trello) ... asana ... ALL THE TOOLS
[ ] do women in tech resources way earlier. also see associated issue https://github.com/Techtonica/curriculum/issues/183
[x] -[X] developer evangelist/relations/advocate - would be in career week
[x] mac
[x] - two fingers to scroll on touchpad
[x] - pairing a magic mouse: put it in discovery mode by 1. turn it off. 2. hold down the mouse "button" and keep holding while you 3. turn it on (using the tiny switch on the back). then the green light should blink twice repeatedly. https://apple.stackexchange.com/a/181549
[x] - rename your magic mouse so you can identify it (and not steal someone else's mouse)
[x] VS Code and editor setup
[x] - how to auto indent
[x] - how to indent multiple lines at a time (highlight several lines, even just partial lines, then press tab to indent the entire code block, or shift+tab to un-indent the entire code block; internal indentation of the block will be preserved. useful for copy and pasting code)
[x] - code folding
[x] - autosave
[x] - mention that VS Code preferences are literally a text file full of key-value pairs
[x] - define key value pair somewhere
[x] CSS
[x] - reset.css basics (find a resource online, or even a video) // exercise where you try a simple website with and without a reset.css and observe the differences. i do not expect everyone to begin using a reset.css in their projects immediately; this is really so people learn about the user agent stylesheet.
[x] teaching debugging
[x] - i should do more interactive sessions with chrome dev tools
[x] - the phrase "pattern matching" and why it's important: use other code snippets to remind yourself of correct syntax
[x] - when VS Code shows you a red squiggly underline, it's trying to help. pay attention to the message.
[x] - if the red squiggly underline is under something that's clearly correct, like
color: red;in a css file, then first check if it really is correct[x] - when you make a change on a file, and then visually when you refresh your page you don't see any changes, run through a quick checklist:
[x] - did you save? this kills me every time (see: add autosave to VS Code lesson if it's not already there)
[x] - make a temporary, very obvious change on your html page. i write some text in the top of the body, or a prominent heading. save the file and reload the browser. verify that you see the text. if you don't see the new text, maybe you have the wrong file open, or the file didn't save, or something else very strange is happening.
[x] - make a temporary, very obvious change to your css file. i like to add
color: red;to something extremely obvious likebodyorh1. save and reload the browser and verify that the thing you expected to turn red actually turns red. if it doesn't, maybe the CSS file isn't getting loaded properly. or check for syntax errors earlier in your CSS file that may render the rest of your CSS file inoperable. are you missing a semicolon? did you use=instead of:accidentally? are you missing a quotation mark in a font declaration, so your CSS file thinks there's a really long string somewhere? are your curly braces correctly matched and closed?[x] bootstrap
[x] - containers inside of containers. talk about rows and columns.
[x] - rows vs "masonry-style" a la pinterest
[x] - clarify order of overriding. large overrides small when screen is large. col-xs-12 col-lg-6 for example
[x] add https://guide.bash.academy/inception/ as beautiful resource (via aaron/kelly)
[x] add https://github.com/GoogleChrome/lighthouse to chrome dev tools or accessibility. it now comes in chrome. find it under audit