If you are leveraging git submodule for Hugh themes and you are accustomed to using git diff to see what changes you made and totally forgot to commit, you will need to tweak your command for git submodules. By appending --submodule=diff you will see diffs for submodules as well: $ git diff --submodule=diff You can run this command at your top level repo and see all changes in that repo plus submodule(s) or cd into a specific submodule and see see the diffs for those changes only.
If you are leveraging git submodule for Hugh themes and you are accustomed to using git without passwords (via ssh urls), you’ll find that when you add a git submodule, it will be setup for “https urls” and thus prompt you for a password: $ git push origin master Username for 'https://github.com': This is obviously annoying but easy to fix. You can check the urls for your origin with git remote -v:
When I first started tinkering with Hugo for static website generation, I would find a Hugo theme that I like, cd into my themes directory and would simply git clone the repo into my website. This works, makes sense and is the most common install instructions from the theme authors. However, you will likely run into an issue where you want to make an edit to the theme only for your website.
I recently updated to the latest stable version of node (v7.5.0) with the following command: $ nvm install stable --reinstall-packages-from=node and when I ran my ios-triage cli app, I saw several DeprecationWarning messages: (node:3958) DeprecationWarning: Calling an asynchronous function without callback is deprecated. Initially I was pretty excited because I recently taught myself node and as a noob I knew I was missing some callbacks which was preventing my async.
What is Technical Debt? Technical debt is a popular term within the software industry. First coined by well-known programmer Ward Cunningham, technical debt is a metaphor that explains the long-term burden developers and software teams incur when taking shortcuts. ThoughtWorks’ Martin Fowler sums up the point well: “Doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt. Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.