My new Pluralsight course Personal Productivity & Performance Tools for Windows Developers “get more done in less time” has just been released.
It covers a range of developer-focused and general productivity tools that you can mix and match to suit your way of working.
“We’re constantly under pressure to be more productive. Learn how to use these tools to improve your productivity, streamline your workflows, and get more done in less time. ”
The course consists of:
- Reduce Typing with AutoHotkey
- LINQPad – A C# / VB.NET Scratchpad
- Starting Programs and Websites with SlickRun
- Take Control of your Clipboard with ClipX
- Remember What you Did with TimeSnapper
- Making the Internet Work for You with IFTTT
- Free Image Editing with Paint.NET
You can find this course along with my other courses on the Pluralsight author page.
The idea of "the power of three" is a universal concept; it can be seen anywhere from religion (The Holy Trinity, Triquetra, etc.) to childhood learning ("ABC", "123") to entertainment (The Three Musketeers, The Three Stooges, etc.) to project management (the scope-cost-schedule triangle).
One simple way to exploit the power of three is to define outcomes/wins/achievements. These "three wins" can be at any level:
- Three wins for the project
- Three wins for the year
- Three wins for the month
- Three wins for the week
- Three wins for today
The three chosen things should not be simple tasks to be ticked off, they should be things that feel like a "win" and give a real sense of progress and satisfaction.
The "wins" should be realistic and achievable.
Getting Results the Agile Way by J. D. Meier makes extensive use of the power of three with its "Monday Vision, Daily Outcomes, Friday Reflection" and three types of "Hot Spot".
The power of three can also be applied to individual items of work/features being developed, for example a feature can be evaluated by: user value, business value, technical value. In agile team retrospectives the power of three can be used to decide: what went well, what didn't go well, what will be improved upon in the next iteration.
(the above is an excerpt from my book Keeping Software Soft)
My 3 Wins for 2014
These are my 3 (professional) wins for 2014 (in no particular order):
While these aren’t my only wins for the year, they are things that I feel if I accomplish them, when I see in 2015 I can look back and be content.
It’s also important to be flexible with plans, if professional or personal events happen that mean I really can’t accomplish these then that’s ok: no plan survives contact with the enemy.
Make some time to think about and write down your 3 wins for 2014 and feel free to share them in the comments.
There's a lot of negativity sometimes in our profession, just take a look in your Twitter stream.
The tools we use aren't absolutely 100% without imperfection; the vendors of the tools we use don't always go in the direction we want them to; and sometimes the things we invest time in learning go away and it's beyond our control.
We are change
It's amazing to me how many developers seem to hate Windows 8, even to the point of wanting to install start button replacement tools. And that's ok, it’s a personal choice. For me, Windows 8 is the best operating system I've ever used. Another example was the "Visual Studio menus are shouting at me!", for the record I didn't "fix" this "problem" as it didn't bother me. But I know some developers who really hated it.
Perhaps because we are agents of change, we don't like not being in control of change.
I think we're living in a golden age of software development
We have amazing (if imperfect) tools, Visual Studio is great and we have some awesome open source libraries that are super easy to install via NuGet.
Between my Windows Phone and Windows Store apps I've had almost 28,000 downloads. More than downloads though, that's 28,000 people’s lives that I've touched, even if it’s in a small way.
I can have an idea, and within an hour have a prototype running on my touch screen Lumia phone, or my SurfaceRT tablet. This is amazing, really it is, and I take it for granted sometimes.
This doesn't mean we shouldn't highlight problems or disagree with the strategies of our tools vendors. When we do, we can drop f-bombs and call "them" idiots and create more negativity in our profession; or we can call things out with respect and with hope for the future.
It's our community, we get to decide how it feels...
I’ve been awarded a Microsoft Most Valuable Professional award for the first time in my career.
I feel like it’s a real personal achievement for me. But why?
The first is purely one of recognition, and while I suppose this could be considered somewhat egoistic, I guess we all like to be rewarded or recognised.
give each other more compliments; not in the vacuous, high-fiving, “team-building exercise” kind of way
I suppose that if you feel good whilst feeling like you’re helping others, then it’s nice win-win.
The imposter syndrome seems to be an oft-quoted thing in our industry and I’m not ashamed to say that I sometimes suffer from this “phenomenon in which people are unable to internalize their accomplishments” [Wikipedia]. Recognition, such as direct compliments from individuals and awards such as the MVP scheme help to alleviate this. I think my article “5 Ways To Give Yourself A Break” was a reflection on this. Perhaps one thing we can do to make our industry more amazing is to give each other more compliments; not in the vacuous, high-fiving, “team-building exercise” kind of way; but in a genuine and sincere appreciation of others’ efforts.
Making Things Better
Things like access to other MVPs and having a more direct line to Microsoft to provide feedback will hopefully make the products and tools we all use better. It’s cool to think I may be able to participate in betas or other programs and provide feedback to make things better.
All in all, I feel like this is a significant milestone in my career and I hope to make the best of it in the coming year…
* Technically it’s from Oct 1st PST – but it’s the 1st here in Australia :)
In my many years of being a software developer there’s one thing that I’ve seemed to have experienced on and off throughout this time: Fear.
- Not knowing the latest language/framework/architecture
- Falling “behind” everyone else
- Not being the best
- Not being as good as others
- Being wrong
- Making mistakes
- Looking stupid
- Not being able to learn future technology X
This list could go on…
I’m not alone in these feelings. I have been told the same by, or seen this trait in, other developers I’ve worked with over the years.
We don’t have to be super heroes
So what can we do as a community of developers for us all to feel happier and more fulfilled?
I think if we want to make our professional community better we can start by learning to gives ourselves a break.
Here’s five ways we might be able to do this, feel free to disagree or add your own ideas in the comments section.
1. You Don’t Have To Wear A Cape
We don’t have to be super heroes.