Why Your Team Feels Stuck — and What to Do About It

Over the years I’ve learned that when a team feels stuck because they are constantly busy but not moving fast the answer isn’t more effort but better focus.

I’ve seen talented engineers grind through backlog after backlog, push late nights, automate everything in sight and still, somehow, progress stalls. Features pile up waiting to ship. Bugs reappear. Morale dips. And everyone wonders: What’s going wrong?

Continue Reading

Outcomes vs. Output: The Leadership Mindset Shift That Matters Most in Engineering

As a Director of Software Engineering, one of the most important lessons I’ve learned is the distinction between output and outcomes. It’s not just a matter of semantics; it’s a mindset shift that defines the difference between being busy and being effective, between a high-velocity team and a high-impact team.

Continue Reading

Troubleshooting Port in Use Errors On Linux With Containers

Troubleshooting Port in Use Errors On Linux With Containers

When you encounter a “port in use” error on Linux, it typically means that another process is already using the port you are trying to bind to. Here’s how to troubleshoot and resolve this issue. NOTE: You may need superuser privileges to run some of these commands. If you run the commands without sudo, you may not see all processes.

Continue Reading

How to Use CTRL+D To Close A PowerShell Window

If you’re familiar with using CTRL+D to exit out of your shell and want the same functionality for your PowerShell, here’s how to do it.

Open your PowerShell profile (Documents\PowerShell\Microsoft.PowerShell_profile.ps1):

notepad $PROFILE

and add this line:

Set-PSReadLineKeyHandler -Key Ctrl+d -Function DeleteCharOrExit

That’s it. Now reload your profile (or open a new terminal):

Continue Reading

Fixing GitHub Copilot Agent Mode Hang in Visual Studio 2022

I was running into an issue with GitHub Copilot’s Agent Mode in Visual Studio 2022 where it would hang indefinitely after executing a command. This was particularly frustrating as it disrupted my workflow and made it difficult to use the tool effectively.

As it turns out, the issue is pretty straightforward to resolve. Apparently it tries to use the Powershell 7 terminal. In my installation, this was misconfigured and was pointing to some non-existent path. In my case, it was pointing to C:\Program Files\Microsoft\Azure Functions Core Tools\workers\powershell\7.4\zh-Hans\pwhs.exe, which does not exist on my system. You can check the path by opening the terminal window (CTRL +` or View->Terminal).

Continue Reading