Shortcut cheat sheets

Visual studio code - https://code.visualstudio.com/docs/customization/keybindings
Resharper - https://www.jetbrains.com/resharper/docs/ReSharper_DefaultKeymap_VSscheme.pdf
Chrome developer tools - https://developers.google.com/web/tools/chrome-devtools/iterate/inspect-styles/shortcuts

Useful git commands cheat-sheet

git commit --amend -m "New commit message"
git push origin --tags
git push --set-upstream origin name
git branch -u origin/foo - track remote branch
git remote -v - view list of remotes
git remote set-url origin - set remote
git branch -m newname - rename current branch

git push origin master -f - forced push

Rebase branch

git checkout feature/branch
git rebase master
git checkout master
git merge feature/branch // fast-forward here

Cleanup

git branch -D name - delete branch locally
git push origin --delete branchname or git push origin :branchname (:branchname should not exist locally then)git

git tag -d name - delete tag locally
git push origin :refs/tags/name - delete tag remotely

git reset --hard HEAD~1 - one commit back

git remote show origin (shows what is in origin and what is stale)
git remote prune origin (removes all local garbage from repo)
git branch -lvv (view list of branches with remotes and marks if remote gone)
git clean -df (remove all untracked files)
git checkout . (discard all the changes to tracked files)

Code snippet to investigate an object content without dances with debugger in C#

var investigated = ...; // assign your object here
System.IO.File.WriteAllText(
    @"D:\test.json",
    Newtonsoft.Json.JsonConvert.SerializeObject(
        investigated, 
        new Newtonsoft.Json.JsonSerializerSettings
        {
            Formatting = Newtonsoft.Json.Formatting.Indented,
            TypeNameHandling = Newtonsoft.Json.TypeNameHandling.Objects
        }));

Rethrow exception and preserve stack trace in.net 4.5

ExceptionDispatchInfo.Capture(myException).Throw();

Simplified module loading in powershell

There is a feature for automatic module discorvery in Powershell. It can search for modules based on paths from PsModulePath variable. It is easy to modify it in a script:

$env:PsModulePath += ";$PsScriptRoot/Modules"

Import-Module SomeModule -ArgumentList "foo" -Verbose // no need to specify path to the module

Get-OtherModuleThing // module will be loaded automatically

External program execution handling in Powershell

External command handling in Powershell is quite similar to .cmd-files. For example:

svn update
if ($lastexitcode -ne 0) { throw $lastexitcode }

UPD: it is better to use throw in powershell rather than exit

Proper script inclusion in PowerShell

It is handy to use simple script inclusion in PowerShell called dot sourcing:

. .\include.ps1

There is a problem however. If you try to call the script from another directory that script lives in, an error occurs. include.ps1 will not be found since PowerShell uses current folder by default as a starting point.
To avoid this, script directory can be used:

$scriptDirectory = Split-Path -parent $MyInvocation.MyCommand.Definition
. $scriptDirectory\include.ps1

UPD: In newer versions script directory variable is provided on the shelf, just use $PsScriptPath variable

External program execution handling in Windows .cmd files

It is common to use .cmd or .bat files to run some simple scheduled tasks. But if you run some external .exe and it reports an error, your script will continue running. So, how to stop execution and exit with error code (usually it is any exit code except 0)? Just write next ugly line after each external program execution:

if %errorlevel% neq 0 exit /b %errorlevel%

For example:

svn update
if %errorlevel% neq 0 exit /b %errorlevel%
sqlcmd -S . -i task.sql
if %errorlevel% neq 0 exit /b %errorlevel%

Explicit datetime values in SQL server queries

It is common to type some temporary queries by hand in SQL Server Management Studio. In order to filter results by date easy to read datetime format can be used:

select * from Posts where CreationDate > '12 Apr 2012 09:07'

Time part can be omitted as well:

select * from Posts where CreationDate > '12 Apr 2012'

This format should work in most scenarios since it is difficult for SQL parser to mess with such an obvious date format. Certainly I would not recommend using it in production code.

Reference Ext JS components as instance fields

In our project we used to work with Ext.getCmp method if we need some dynamic interactions with our components. Which is not a very good experience actually. Instead of calling Ext.getCmp('usersPanel').doLayout() I would prefer just use this.usersPanel.doLayout().

To simplify our life we just can assign all needed fields in initComponent method:

initComponent: function() {
  Ext.apply(this, {
    items: [{
      xtype: 'panel',
      id: 'usersPanel'
    }]
  });

  this.callParent(arguments);

  this.usersPanel = Ext.getCmp('usersPanel');
}

Could be a nice solution, but there are some drawbacks: id property will correspond to html id attribute which should be unique in scope of html page. If we need to create several instances of our custom control we will run into troubles.

Ok, there is another way to achieve our aim:

initComponent: function() {
  this.usersPanel = new Ext.panel.Panel();
  Ext.apply(this, {
    items: [this.usersPanel]
  });

  this.callParent(arguments);
}

Well, quite straightforward way for autogenerated content, but will become quite unreadable in a component with several components. I can not call Ext designer very smart tool as well when it gets to the part with modifying generated components.

Happily enough there is a built in support for local ids in Ext JS.

initComponent: function() {
  Ext.apply(this, {
    items: [{
      xtype: 'panel',
      itemId: 'usersPanel'
    }]
  });

  this.callParent(arguments);
  this.usersPanel = this.getComponent('usersPanel');
}

It has a pitfall though. Method getComponent works only with items collection, but for deep hierarchy this approach doesn't work. My components usually have several layers of nested components. Especially when some layout work is required.

After some thinking we decided to allow components register themselves in a root container when they are created. Performing this work in initComponent is a good idea, but we need to have a reference to a container itself. So, initialConfig must contain two additional arguments: local identifier and parent component. We decided to do one pace further and make it more concise to be written in one line. Something like this: saveAs: { component: this, fieldName: 'usersPanel' }

Let's stop here for a while and discuss one small tip for JavaScript. Managing scope for code should be done carefully. If not it is easy to get some annoying 'undefined' errors. To simplify life we can just store a reference to an object in a variable once and let closures work for you. Usually I define me variable in the beginning of instance method which is equal to this.

initComponent: function() {
  var me = this;
  // ...
}

Back to our instance fields stuff let just make it more fluent: save: me.as('usersPanel')

As you may guess we defined a method as in current component which just returns a new object similar to { component: this, fieldName: 'usersPanel' }. All components in Ext JS are descendants of Ext.Component, it is a good place to put our registration extensions there:

Ext.Component.implement({
  as: function (fieldName) {
    return {
      component: this,
      fieldName: fieldName
    };
  }
});
  
Ext.Component.override({
  initComponent: function() {
    this.callOverridden();
   
    if (this.initialConfig.save) {
      this.save.component[this.save.fieldName] = this;
    }
  } 
});

Our initial example will look like:

initComponent: function() {
  var me = this;
  Ext.apply(this, {  
    items: [{
      xtype: 'panel',
      save: me.as('usersPanel')
    }]
  });
   
  this.callParent(arguments);
  // usersPanel is created and registered
  // me.usersPanel is available
}

You can check working example of this technique.