add more Vim and shell resources

mattmakai · mattmakai · commit 9bf843bb5628 · 2018-07-04T09:40:47.000-04:00
diff --git a/content/pages/02-development-environments/02-vim.markdown b/content/pages/02-development-environments/02-vim.markdown
@@ -147,6 +147,10 @@ to get started with these tutorials.
   to quickly open files in other directories rather than expanding the 
   whole path.
 
+* [Seven habits of effective text editing](http://moolenaar.net/habits.html)
+  explains moving around efficiently, fixing errors quickly and forming good
+  habits.
+
 
 ### Vimrc resources
 These are a few resources for learning how to structure a `.vimrc` file. I
@@ -160,6 +164,10 @@ individually instead of going whole hog with a Vimrc you are unfamiliar with.
 * [Vim and Python](https://justin.abrah.ms/vim/vim_and_python.html) shows
   and explains many Python-specific .vimrc options.
 
+* [Vim as a Python IDE](http://liuchengxu.org/posts/use-vim-as-a-python-ide/)
+  shows a slew of plugins and configuration options for coding with Python
+  in Vim.
+
 * This
   [repository's folder with Vimrc files](https://github.com/amix/vimrc/tree/master/vimrcs)
   has example configurations that are well commented and easy to learn from.
@@ -232,6 +240,9 @@ ready to take that step.
 * [VimAwesome](https://vimawesome.com/) is a directory of Vim plugins sourced 
   from Vim.org, GitHub and user submissions.
 
+* [Command-T](https://github.com/wincent/command-t) is a Vim plugin for
+  fast fuzzy searching files.
+
 
 ### Vim Plugin Managers
 If you use many Vim plugins together it is really handy to have a plugin
@@ -246,3 +257,28 @@ are the most commonly-used ones in the Vim ecosystem.
 
 * [Vim-plug](https://github.com/junegunn/vim-plug) bills itself as a
   minimalistic Vim plugin manager.
+
+
+### Niche tutorials
+After you have been using Vim for awhile there will be features you bump
+into without realizing they were ever there. The following tutorials show
+how to use some specific niche features. You may already know about these
+if you have been using Vim for awhile but everyone's learning path is 
+different so it's useful to do a quick scan to make sure you are not missing
+anything.
+
+* [Vim’s absolute, relative and hybrid line numbers](https://jeffkreeftmeijer.com/vim-number/)
+  shows how to change the line numbering scheme. There was a period of 
+  time I used relative line numbers although I eventually switched back
+  to absolute numbers. The usefulness of these schemes is often dependent
+  on what language you are working in.
+
+* [A simpler Vim statusline](https://www.blaenkdenum.com/posts/a-simpler-vim-statusline/)
+  explains how to customize your bottom screen statusline *without* using
+  plugins such as [vim-powerline](https://github.com/powerline/powerline) 
+  or [vim-airline](https://github.com/vim-airline/vim-airline).
+
+* The [vim-clutch](https://github.com/alevchuk/vim-clutch) is a really cool
+  project and walkthrough that shows how you can create a foot pedal to
+  switch between Normal and Insert modes instead of using the typical ESC
+  key (or a remapped key).
diff --git a/content/pages/02-development-environments/06-jupyter-notebook.markdown b/content/pages/02-development-environments/06-jupyter-notebook.markdown
@@ -162,3 +162,7 @@ like advanced interactive visualizations.
 * [Python & Big Data: Airflow & Jupyter Notebook with Hadoop 3, Spark & Presto](http://tech.marksblogg.com/python-big-data-airflow-jupyter-notebook-hadoop-3-hive-presto.html)
   walks through a data pipeline that combines several commonly-used
   [data analysis](/data-analysis.html) tools with a Jupyter Notebook.
+
+* [Ansible-jupyter-kernel](https://github.com/ansible/ansible-jupyter-kernel)
+  is a kernel that allows you to run [Ansible](/ansible.html) tasks and 
+  playbooks from within your Jupyter environment.
diff --git a/content/pages/02-development-environments/07-shells.markdown b/content/pages/02-development-environments/07-shells.markdown
@@ -35,3 +35,8 @@ environment named `fullstackpython` within the macOS Terminal application.
   of lag in your keystrokes appearing on the screen. It's a fascinating look 
   at how a small difference of tens of milliseconds causes some shells and 
   editors to feel slow while others are snappy.
+
+* [Why Create a New Unix Shell?](http://www.oilshell.org/blog/2018/01/28.html)
+  is a post by the creator of [Oil shell](http://www.oilshell.org/) that
+  goes into the rationale for building a new shell even though so many others
+  such as Bash, zsh, PowerShell and KornShell already exist.
diff --git a/content/pages/02-development-environments/10-powershell.markdown b/content/pages/02-development-environments/10-powershell.markdown
@@ -33,3 +33,15 @@ of a Python programmer's
 
 * [Getting Started with Windows PowerShell](https://docs.microsoft.com/en-us/powershell/scripting/getting-started/getting-started-with-windows-powershell)
   is a guide for your first steps with PowerShell.
+
+* [Windows Command-Line: Backgrounder](https://blogs.msdn.microsoft.com/commandline/2018/06/20/windows-command-line-backgrounder/)
+  and
+  [Windows Command-Line: The Evolution of the Windows Command-Line](https://blogs.msdn.microsoft.com/commandline/2018/06/27/windows-command-line-the-evolution-of-the-windows-command-line/)
+  give historical perspective on how the Windows shell has evolved from
+  MS-DOS days into the current Windows 10 world.
+
+* [PowerShell in Azure Functions](http://www.brianbunke.com/blog/2018/02/27/powershell-in-azure-functions/)
+  shows you how to use PowerShell scripting language code in your Azure
+  Functions. The language is only in experimental mode on Azure Functions 
+  but could be useful if you have a bunch of existing scripts that you want
+  to use on the [serverless](/serverless.html) platform.
diff --git a/content/pages/04-web-development/40-integration-testing.markdown b/content/pages/04-web-development/40-integration-testing.markdown
@@ -45,3 +45,9 @@ during development so they can be addressed immediately.
   coded in Java but still relevant when you're learning about integration
   testing.
 
+* [What is an integration test exactly?](https://softwareengineering.stackexchange.com/questions/48237/what-is-an-integration-test-exactly)
+  is an awesome Stack Exchange thread that defines the differences in 
+  testing approaches like [unit tests](/unit-testing.html) versus integration
+  and other tests. There is also some practical advice like "It’s not 
+  important what you call it, but what it does" which as a pragmatic 
+  programmer I am keen to agree on.
diff --git a/static/img/logos/react.png b/static/img/logos/react.png
