Skip to content

Instantly share code, notes, and snippets.

This is my default career advice for people starting out in geo/GIS, especially remote sensing, adapted from a response to a letter in 2013.

I'm currently about to start a Geography degree at the University of [Redacted] at [Redacted] with a focus in GIS, and I've been finding that I have an interest in working with imagery. Obviously I should take Remote Sensing and other similar classes, but I'm the type of person who likes to self learn as well. So my question is this: What recommendations would you give to a student who is interested in working with imagery? Are there any self study paths that you could recommend?

I learned on my own and on the job, and there are a lot of important topics in GIS that I don’t know anything about, so I can’t give comprehensive advice. I haven’t arrived anywhere; I’m just ten minutes ahead in the convoy we’re both in. Take these recommendations critically.

Find interesting people. You’ll learn a lot more from a great professor (or mentor, or friend, or conference) o

@tmcw
tmcw / comprehensive_documentation.md
Created March 25, 2015 14:46
Comprehensive Documentation

Software is layered.

Documentation is not. If your documentation states

Run npm install foo to install this module

It is really saying

@landonreed
landonreed / README.md
Last active August 29, 2015 14:22
tota11y_now: a bookmarklet that puts Khan Academy's amazing accessibilty tools on any website
  1. Use Chrome. [recommended]
  2. Copy javascript text from tota11y_now.js below (you'll need this for later).
  3. Right-click on bookmarks bar and select 'Add Page...'
  4. Paste javascript into URL field.
  5. Give the bookmarklet a cool name like tota11y_now or accessibility rocks!!!
  6. Go to your favorite website (it won't work on GitHub Gist). E.g., https://twitter.com
  7. Click the awesome little sunglasses image in the bottom left of screen 😎
  8. All done!
@ericclemmons
ericclemmons / example.md
Last active July 17, 2024 06:50
HTML5 <details> in GitHub

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here
@rambabusaravanan
rambabusaravanan / detect-js-framework.js
Last active July 8, 2024 05:24
Detect JS Framework used in a Website
// Paste these lines into website's console (Win/Linux: Ctrl + Shift + I / Mac: Cmd + Alt + I)
if(!!window.React ||
!!document.querySelector('[data-reactroot], [data-reactid]') ||
Array.from(document.querySelectorAll('*')).some(e => e._reactRootContainer !== undefined || Object.keys(e).some(k => k.startsWith('__reactContainer')))
)
console.log('React.js');
if(!!document.querySelector('script[id=__NEXT_DATA__]'))
console.log('Next.js');