Showing posts with label Work. Show all posts
Showing posts with label Work. Show all posts

Monday, December 6, 2021

Setting up a new work laptop

I started at a new company today and am setting up my new laptop. I thought I would spend a few minutes writing my standard list of software that I install by default, for my future self (and perhaps, others).

Must have software:

For Microsoft Development:
For Git integration:
I also run, as Visual Studio add-ins:
For Azure development:

Friday, April 21, 2017

Dictatorial Management

Issues don't go away simply because you issue an edict or say that the issue will no longer happen.

One of my favorites is a problem my team runs into almost every day: a developer checks code into the system and breaks the deployment to our test environment. Management's "solution" is that developers shouldn't break the deployment so there's no point in educating the developers on how to troubleshoot and resolve deployment issues.

Now stop and re-read that last sentence. What!?

Because an issue shouldn't occur, there's no point in educating people on how to solve the issue when it does occur. This is a typical management solution.

Another common management solution is to threaten to track the number of issues per developer and have this count reflected on their next performance review. Thus far, I've never seen this done, as to do so would be quite onerous on the manager (and in reality, what does this actually solve?).

How much more successful would companies, teams, and people be if we would stop the nonsense of impossible solutions? Simply stating 'this issue will never happen again' or to threaten and cajole does nothing to actually solve a problem. Why don't we work in realities and actual possible solutions instead of the ridiculous power-insanity of those at the top or the simplistic manager solutions that do nothing to address the real issues.

Do you want to actually provide a real solution? How about empowering your employees with the mastery and autonomy to actually care about what they do and the quality with which they do it? What if they had some ownership in the process and the success of what they are doing? What if instead of dictating, you stepped aside and let the team choose? It might not be good for your ego, but it sure would solve a lot more issues than a top down approach.

Tuesday, May 14, 2013

The backups, the backups, oh the… wait, I don’t have them… DOH!

I know I should backup everything regularly.  I work in software.  Really, I have no excuse.  I’ve read several of Scott Hanselman’s posts on setting up regular backups.  I have some (manual) backups that I do on occasion, but nothing regular and certainly not comprehensive.  A few weeks ago, the blog hosting service canceled my account, they did not keep any backups (why would they?) and I did not have any backups of my blog posts.  Shame on me!  And so I am here, attempting to recover some of the posts through Google’s cache and the internet archive, with limited success.  The images are gone, but at least the text content is available.

The main lesson I have learned through this is that backups must be automated if they are going to regularly happen.  A manual backup is nice, but I forget, I get busy, I tell myself I’ll do it tomorrow, or any number of excuses.  The tools exist today for automating most backups.  I have no excuse.  Neither do you.

I echo Scott’s recommendation of having at least three backup locations.  I’ve spent the last several days setting these up, with cloud storage being one, a local NAS (network attached storage) drive being the second, and an external hard drive being a third.  I’m still in the process of doing this.  I will also be setting up services that run daily/weekly that will backup my mail, blog posts, and any content that regularly changes.  By the end of this, I’ll likely be backup crazy, but next time, I won’t lose content!