JimHume

# Note: One would want to wrap this in a batch file that contains this:
# PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '.\LaunchKubernetesDashboard.ps1'" 
# (or whatever you name the file)

clear

# Get the currently-active cluster name
$clusterName = $(kubectl config current-context)
# Get the user name for the active context
$contextUser = $(kubectl config view -o jsonpath="{.contexts[?(@.name == '$clusterName')].context.user}")

JimHume

clear
# Find the current cluster admin user token
$clusterName = $(kubectl config current-context)
$contextUser = $(kubectl config view -o jsonpath="{.contexts[?(@.name == '$clusterName')].context.user}")
$token = $(kubectl config view -o jsonpath="{.users[?(@.name == '$contextUser')].user.token}")

# Copy the admin token to the clipboard
Set-Clipboard $token

# Launch the dashboard and open it in a browser

JimHume

    public static class DbContextExtensions
    {
        /// <summary>
        /// Resolve the connection string for the given <see cref="DbContext"/>. This resolves variables in the
        /// connection string to their local values. E.g. "Data Source=|DataDirectory|\Database.sdf" will resolve
        /// to "C:\ProgramData\MyApp\Database.sdf".
        /// </summary>
        /// <param name="dbContext"><see cref="DbContext"/></param>
        /// <returns><see cref="string"/>: The fully-resolved connection string.</returns>
        public static string GetResolvedConnectionString(this DbContext dbContext)

JimHume

#!/bin/bash

################################################################################
# Constants

# TOKEN: Taken from an API bot
TOKEN='letters-numbers-numbers-numbersandletters'

# CHANNEL: When viewing the desired channel in a browser, this will be the last 
# segment of the URL

JimHume

#!/bin/bash

# This is the contents of the updated script:
NEW_SCRIPT=$(cat << EOF
package setup_update;
sub process {
    return 'success';
}
sub display {
    my $vars = shift @_;

JimHume

Linux NetFilter, IP Tables and Conntrack Diagrams

IPTABLES TABLES and CHAINS

IPTables has the following 4 built-in tables.

1) Filter Table

Filter is default table for iptables. So, if you don’t define you own table, you’ll be using filter table. Iptables’s filter table has the following built-in chains.

JimHume

#!/bin/bash


function arg_or_default()
{
    if [ -n "$1" ]; then
        echo "$1"
    else
        echo "$2"          
    fi                     

JimHume

http://sijinjoseph.com/programmer-competency-matrix/

Describes the different areas and requirements to becoming skilled in computer science. Very valuable as both something to strive for and personally evaluate against, and also as a manager to look for these characteristics in your reports.

https://www.linkedin.com/pulse/7-things-make-great-bosses-unforgettable-dr-travis-bradberry

This was a great article for management, but also for developers. Providing feedback to a manager that they are or aren't following some of these tips can be extremely valuable in both directions.