Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PowerShell Troubleshooting Guide

You're reading from   PowerShell Troubleshooting Guide Minimize debugging time and maximize troubleshooting efficiency by leveraging the unique features of the PowerShell language

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher
ISBN-13 9781782173571
Length 206 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Michael Shepard Michael Shepard
Author Profile Icon Michael Shepard
Michael Shepard
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. PowerShell Primer FREE CHAPTER 2. PowerShell Peculiarities 3. PowerShell Practices 4. PowerShell Professionalism 5. Proactive PowerShell 6. Preparing the Scripting Environment 7. Reactive Practices – Traditional Debugging 8. PowerShell Code Smells Index

Language-agnostic code smells


Some things look wrong no matter what language they're written in. For instance, if you have 200 lines of code in a block, it's always going to be a sign that some effort might pay off in terms of rewriting it using smaller, more modular code. Also, if you see several blocks of code that are identical, or even very similar, it will probably be worthwhile from a maintenance standpoint to factor that code out into a function. Some other code smells that are very common are:

  • A very large parameter list

  • Overly short identifiers

  • Extremely long identifiers

  • Deeply-nested loops or conditionals

  • Multiple-personality functions (that is, functions that do more than one thing)

One thing that is worthwhile to point out is that these are all somewhat subjective. For instance, what is a large parameter list? Some PowerShell cmdlets have dozens of parameters. Do they smell? Everyone will have their own perception of when that line has been crossed. Even when a usage isn't excessive...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image