Remote / Working from Home, Part 3

[Part 1] [Part 2] [Part 3] The previous entries went through the basics of everyday "working remote." This entry talks about new hires or new teams introductions and other good stuff.  Initiative, Integrity and Vigilance Working remote, when starting with a new team can be a little awkward. Especially when you've never met the team in person first. These are good guidelines for this situation. Ask questions - Show Initiative Sesame Street taught my youngest: "Asking questions is the best way to learn." Not sure which questions to ask? Find someone, anyone that is available Ask to be pointed in the right direction Don't assume everyone will drop what they're doing. Be patient. Be calm. Basic Questions to Ask: Who can help with HR questions? Payroll Dates Benefits Timesheets Expenses Time Off Requests Who is my manager, if not working on the same project? Who are the members of the team I'm working on? What access, resources, documentation do I need

Tip of the Day: Number 3372.7

Windows: Moving Applications Between Multiple Monitors [Win] + [Shift] + ( [⬅] or [➡] ) One simple, elegant key stroke sequence vs. : Moving a window that is maximized: [Alt] + [Space] [R] [Alt] + [Space] [M] ( [⬅]  or  [➡] )

Remote / Working from Home, Part 2

[Part 1] [Part 2] [Part 3] Part 1 covered the primary goal of DevOps: Communication.  Part 2: Routine & Consistency Establish daily practices that everyone can depend on.  Make a mental list of your daily work routine: Shower Yes, it's super easy to skip this, but trust me, it's vital to establishing a fresh perspective. A shower can do wonders for your attitude and Vim. It sets a tone for the day: Warm. Energetic. Positive. Work Casual / Respectable Clothes Somehow, wearing comfortable work-proper clothes gives a mental energy to be able to focus on tasks. You never know when you're going to have a video call. "Clothes Maketh The Man." Have Breakfast Even if you don't feel like eating. Drink a protein shake. Scramble some eggs in a drinking glass and microwave for a minute. A Solid "Start & Stop" Work Times This an important key to consistency. Everyone on your team will know when you're available and working. Post this information i

Back-Track: What happened between 2017 and 2020?

This blog hadn't been updated in quite a long time. Why? It was intended to be an easy, private notebook for me. Ramblings, thoughts, etc. During that time, I was using Twitter ( @edhaack) for quick, blurty blurts on findings - ultimately feeling overwhelmed (maybe).  What happened, really? Work. Life. Balance. Xceligent publicly and shamefully closed its doors a week before Christmas 2017. Previous co-workers talked about how I helped them and wanted my help on their projects. Ultimately, I siloed myself -- and have taken some time to reflect on the last 30 years. Why come back here? I think I wanted to return a more private, intimate and minimalistic platform.  /shrug Some of those tweets are kinda cool to go back and look at. I may just integrate this with that.

Remote / Working From Home

[Part 1] [Part 2] [Part 3] I usually refrain from mentioning current and previous positions I've held and will continue to do so. This is about the "better practices" of "working from home." This is the first of a few articles based on my experiences. When the COVID-19 quarantine threw everyone into a relative 'panic mode,' a VP asked me to write a short article on transitioning from working "in office" to "at home." There are a lot of these types of videos and articles available already, but it gave me pause to reflect on how this group and these teams work - cater to their culture. Part 1: Communication Communicate with tact and curtesy.  Status is vital to success. There's nothing worse than not knowing what people are doing. The default thought is they are watching movies or housework. Which leads to... Trust on all sides.  Trust that you are adult and responsible enough to do your tasks Trust that your people are those adul

PowerShell 7 - Scaffold Structure (Follow-up)

Some interesting hurdles crossed with this simple philosophy: Organize custom functionality in a structured, standard format. Main Scaffold "Process" and "Begin" segments Status Notifications - Output Logging Exception Handling - Generically Artifact Publishing Custom Structure AssertParameters (arg testing/validation) MainProcess $Script:Artifact.Data $Script:Artifact.Files Notes Simple dot sourcing the "custom" script, does not pull in $Script:args variables. (Must explicitly pass $Script:args) Almost ready for 'main' branch merge

Laptop w/ new Ubuntu 20.04 LTS Desktop

 I recently had to install Ubuntu Desktop on a laptop that had a problematic NVidia chipset: The system would always freeze in a very short amount of time - most likely due to a combination of overheating and/or bad drivers. This article saved the day: I just changed the GRUB config for the initial start of installation and everything worked without a single glitch. Even post-install, I did not have to change the grub config  Essentially, appending `nomodeset` to the line containing `linux` bypassed the default video check (even though it was listed during setup). Getting to the initial grub config with selecting the "lite" version of the USB partition.