Development Experience(s)

I figure I'd just share stuff as found myself needing to automate more of my life. This might also give you some behind-the-scenes insight in what I'm doing. Or it might not. Previous article in this series:  AutoHotKey is neat ... Dates! I write a lot of notes with dates attached to them. With a simple .date , AHK writes the current date in my local date format in whatever I'm editing, e.g. 30/09/2021 : ::.date:: Today := A_Now FormatTime, Today, %Today%, ShortDate SendInput %Today% return To prepare for future meetings, I use .t for tomorrow, or .2 for the day after tomorrow. ::.t:: Tomorrow := A_Now Tomorrow += 1, days FormatTime, Tomorrow, %Tomorrow%, ShortDate SendInput %Tomorrow% return ::.2:: DayAfterTomorrow := A_Now DayAfterTomorrow += 2, days FormatTime, DayAfterTomorrow, %DayAfterTomorrow%, ShortDate SendInput %DayAfterTomorrow% return Window management! Windows already comes with great windows management; I use the following built-in actions on a daily basis (

My first thought was to take the text and remove all non-hexadecimal values from it, meaning "In f orm a tion C l a ssifi ca tion" would be #FACAFA . Neat! " Ba n a n a s" would end up being #BAAA . Not exactly a banana-looking color, but it's a color. I played around with it a little bit when I got another idea. What if I just take extract the numerical unicode value from each character and build up an RGB color from that?  let r = 1, g = 1, b = 1; Array .from(text) .map(c => c.charCodeAt()) .forEach((v, i) => { if (i % 3 === 0) b += v; else if (i % 2 === 0) g += v; else r += v; }); The only issue I was having then, was that the resulting number would exceed 255 which is a non-OK color value. To solve the issue, I decided to normalize the value to somewhere between 150 and 255 to get bright-looking colors that would look nice behind

Constructed as a fable, this book - like the Phoenix Project - is able to pack a lot of learning in a small package. I found the book quite easy to read, getting through half of it in one single sitting (which is unheard of for me)! I understand now why this is recommended reading for leadership positions at Redgate (where I'm currently employed), and I - in turn - strongly believe that more people in leadership, nay team settings  should read this book. There is so much to unpack about intrapersonal behaviour, that I'd argue the book will be valuable quite early in one's career, if one is expected to partake in meetings and discuss topics. Pretty broad, eh? Indeed.