The Dev Environment: Issues, Debug Patterns, Env Checkers
Hosted by NoVa.JS
Details
Your development environment is a house of cards you’ve been building since day one on your computer. Guess what? It’s different than literally everyone you’ve ever collaborated with. I use brew, zsh, and nvm. But you might use macports, bash and n. Someone on Windows or Linux will have a totally different environment too.
Any tech lead, support technician or a tool savvy developer knows this can be, and frequently is, a problem. I have found myself debugging development environment issues more than I care to admit. It’s always something: a node version is 7.5 instead of 7.6. (this has happened) Or your version of Chrome is new and a deprecated API is gone. (this has happened too) Or you’re missing a critical component of the Android toolchain. (yup, this too) Or Xcode hasn’t been updated. (guess what, this too)
It’s maddening, but it’s a fact of life with the software development progress. Toolchains are growing in both complexity and size and are getting no easier to use. Any efforts to unify toolchains are often brittle, proprietary, or experimental, so clearly that’s not the way forward for everyone.
The way forward is three fold:
-
Know what you have: Easily finding the “fingerprint” of everything that makes up your environment. From your OS version, to the path of your node binary. This is envinfo.
-
Enforce what you use: Enforcing and correcting mismatched environments on a per project basis. This is Solidarity.
-
Lock down critical paths: Encapsulate with containerization and full virtualization if necessary. This usually means docker, vagrant, virtualbox and similar technologies.
## Case studies of environment issues
- Ruby while using fastlane
- Node while building a web project
- Android SDK in a React Native Project
- Xcode in iOS project
- Missing Bash 4 builtins
## Typical environment debug patterns
- why are they all different spellings, and dashes?
- `node -v`
- `docker --version`
- `Xcodebuild -version`
- `Open Chrome => chrome://version`
- With envinfo - cli usage for whole environment `$ envinfo`
- With solidarity - cli usage for project specific environment `$ solidarity`
## Applications of environment checking
- Issue trackers and bug reporting including Expo, react-native, webpack, create-react-app
- Local debugging for teams
- Debugging CI operations
- Team member onboarding
AGENDA
• 6:30PM -- Doors open
• 6:30 - 7:00PM -- Socializing | Food & Drinks
• 7:00 - 7:50PM -- Talk & Demo
• 7:50 - 8:00PM -- Q&A
• 8:15PM -- Doors closed
ABOUT THE SPEAKER
Trevor Brindle (https://twitter.com/trevorbrindlejs) is a Senior Front End Engineer at Modus Create. He has an avid interest in React Native, music, party parrots, open source software, and automating all the things. He enjoys mentoring new developers and speaking at conferences about JavaScript, Hybrid Development, and Continuous Integration. Trevor lives and goofs around in North Carolina with his wife and daughter.
