Jeff Hicks jdhitsolutions

Public Presentation Policy

I have been an IT professional for over 30 years. I have been speaking publicly and presenting at conferences for probably 25 years. I have presented to all types of groups, from small user groups to large conferences, literally around the world. As I enter the last part of my IT career, I am re-assessing what role conferences will play, and where I want to devote my energy and financial resources. The truth is, that as much as I enjoy presenting and meeting people, there is always a trade-off between the time and money spent on conferences and the value I get from them.

Beginning in 2024, I have decided to make some hard decisions. If you are involved in a conference or event where I have spoken in the past, this may be of interest to you. The bottom line is that I am now very selective about what events and conferences I will present at. Let's dive into some details, and of course there will be exceptions, which I'll cover in a bit.

Requirements

First, **I will no longer

PowerShell Podcast ScriptingChallenge

This is the PowerShell scripting challenge from my appearance on the PowerShell Podcast

Base Challenge

Using whatever tools and techniques you want, write a PowerShell function that will query the Issues section of a GitHub repository and create output showing the number of open issues by label and the percentage of all open issues. Remember that multiple labels may be used with an issue.

For example, if there are 54 open issues and the bug label is used 23 times,your output would show a count of 23 and a total percentage of 42.59 for the bug

	#requires -version 7.4
	#requires -Module Microsoft.PowerShell.Crescendo

	#this demo assumes you have copied the du.exe utility from Sysinternals to a folder in your path

	#the name of the module to create
	$ModuleName = "FolderUsage"
	#the parent folder for the module
	$ModulePath = "C:\temp"

	return "This is a demo script file."

	# Find Me: https://jdhitsolutions.github.io

	# Any one can learn syntax and mechanics.
	# Let's focus on the squishy bits - what you should write
	# and what not to write

	#region Essential rules

	#requires -version 7.4

	<#
	This function requires the gh.exe command line tool.
	You many encounter API rate restrictions under heavy use.
	#>

	#load the custom formatting file
	Update-FormatData $PSScriptRoot\ghLabelStatus.format.ps1xml

	#requires -version 5.1
	#requires -RunAsAdministrator

	#PSRefresh.ps1

	<#
	Update key PowerShell components on a new Windows 10/11 installation.

	This script is not intended for server operating systems. The script
	should be run in an interactive console session and not in a remoting session.

	return "This is a demo script file."
	#demo.ps1
	#about me
	https://jdhitsolutions.github.io

	#Module layout
	psedit c:\scripts\new-project.ps1
	. c:\scripts\new-project.ps1
	Help New-PSProject

	#requires -version 7.3

	<#
	No code in this file should be considered production-ready.
	All code and explanations should be viewed as educational material.
	You are free to re-use anything in this file in your own work.
	#>

	# FIND ME: https://jdhitsolutions.github.io/

	#requires -version 5.1

	<#
	Based on a function from https://gist.github.com/dhmacher/2203582502c7ab13015db8f52e94da45

	You need an access token that has at least write access to your status

	* go to settings -> Development
	* Click "New Application"
	* Enter a name

	#requires -version 5.1

	#set a temporary environment variable
	# example using the function alias and positional parameters: se rust_log debug
	Function Set-EnvironmentVariable {
	[CmdletBinding(SupportsShouldProcess)]
	[alias("se")]
	Param (
	[Parameter(Position = 0, Mandatory)]
	[ValidateNotNullOrEmpty()]