- Outcomes and standards-based education
- Not a curriculum company
- Turning juniors/mids into mids/seniors
- Turning seniors into leads, principles, VPs
- Not necessarily with career alignment- they don't have to go all-in
Courage time is an opportunity to explore material that falls outside the scope of the curriculum. Over your warmup period, pick a technology, framework, library, etc. that interests you and dive in! Do some google searching, do some reading, find a tutorial, etc. This is your time to flesh out your interests and potentially discover some cool tech that excites you.
Possible topics include things like:
const express = require('express') | |
const app = express() | |
const path = require('path') | |
const fetch = require('node-fetch') | |
const PORT = process.env.PORT || 3000 | |
app.get('/api/user', (req, res) => { | |
res.json({ name: 'Richard' }); | |
}); |
node { | |
echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1' | |
echo 'No quotes, pipeline command in single quotes' | |
sh 'echo $BUILD_NUMBER' // 1 | |
echo 'Double quotes are silently dropped' | |
sh 'echo "$BUILD_NUMBER"' // 1 | |
echo 'Even escaped with a single backslash they are dropped' | |
sh 'echo \"$BUILD_NUMBER\"' // 1 | |
echo 'Using two backslashes, the quotes are preserved' | |
sh 'echo \\"$BUILD_NUMBER\\"' // "1" |
A quick guide on how to setup Node.js development environment.
nvm allows installing several versions of Node.js to the same system. Sometimes applications require a certain versions of Node.js to work. Having the flexibility of using specific versions can help.
Picking the right architecture = Picking the right battles + Managing trade-offs
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
This is how you can take an OpenVPN .ovpn config file and extract the certificates/keys required to import the profile into NetworkManager.