Reddit reviews Code Complete (Developer Best Practices)

As a software engineer at a DoD-funded company, I learned about this disaster at work when taking training on how software should be accounted for at each stage of a mission.

I feel like so many problems like this could be avoided if we just teach everyone software engineering fundamentals. I'm surrounded by some of our country's brightest engineers, scientists, researchers, and analysts but they still don't get the value of input validation! That one hurt my heart when I heard it.

Software engineering isn't even that hard. There are facts that we've been taking for granted for decades in the software industry. Everyone at this company depends on software and most people at least write the occasional script to help them. They should all know what's involved in making quality software.

(Of course all of these resources should be taken with a grain of salt, but it never hurts to gather more information to consider when making mission-critical decisions.)

Anyway this 'everyone should learn software engineering' thing is the hill I'm gonna die on at this company, wish me luck.

I second this, Code Complete is a great book for intermediate programmers. It covers practical issues that go beyond the normal issues covered in programming languages books, e.g. how to comment code.

Another good one is The Practice of Programming

A good "meta" book is The Pragmatic Programmer

• http://www.phptherightway.com/
  
• https://www.amazon.com/Code-Complete-Developer-Best-Practices-ebook/dp/B00JDMPOSY
  
• https://www.amazon.com/Modern-PHP-Features-Good-Practices/dp/1491905018/
  
  You're welcome.

Nothing is every really outdated, as you never know what you are going to encounter in a target / assigned environment and even have to continue to deal with legacy OS, PS versions and now cross platform. That cross platfomr bit, as far as in depth stuff, no refrence really exists, yet.

​

Why are not all the built-in help files and ps1/psm1, etc., not a good reference point and well as all the docs on the MS PowerShell GtiHub and docs site as well as these handy resources and one of the other top PS books that been around: for years now:

Windows PowerShell in Action, Second Edition Second Edition

​

And coding in general -just becasue the more your script , eventually understand real coding practices is paramount. Look to this reference. It's not PowerShell specific, but for wrapping you head and goals around coding practices.

Code Complete (Developer Best Practices)

​

PowerShell Documentation

https://docs.microsoft.com/en-us/powershell

https://docs.microsoft.com/en-us/powershell/module/?view=powershell-6

​

Other free eBook references

https://leanpub.com/u/devopscollective

http://www.powertheshell.com/cookbooks

​

Windows PowerShell Survival Guide

https://social.technet.microsoft.com/wiki/contents/articles/183.windows-powershell-survival-guide.aspx

​

DevOps Collective Videos

https://www.youtube.com/playlist?list=PLfeA8kIs7CocGXuezOoYtLRdnK9S_Mq3e

​

Cheet Sheets

https://github.com/PrateekKumarSingh/CheatSheets/tree/master/Powershell

​

PowerShell Best Practices

• https://blogs.technet.microsoft.com/heyscriptingguy/tag/best-practices

• https://blogs.technet.microsoft.com/heyscriptingguy/2014/05/28/powershell-best-practices-simple-scripting

• https://www.digitalshadows.com/blog-and-research/powershell-security-best-practices

• https://ptgmedia.pearsoncmg.com/images/9780735666498/samplepages/9780735666498.pdf

• https://www.digitalshadows.com/blog-and-research/powershell-security-best-practices

• https://github.com/PoshCode/PowerShellPracticeAndStyle

• https://gallery.technet.microsoft.com/scriptcenter/PowerShell-40-Best-d9e16039

• https://www.microsoftpressstore.com/store/windows-powershell-best-practices-9780735666498

​

​

​

Before you look into trying to optimize your code, beyond the basics anyway, I think it's more important to learn how to write readable and maintainable code first. Code that is easier to change, maintain, and write, is much much better than code that runs slightly faster.

Two books that are highly recommended for this are Code Complete and Clean Code.

The one book that every programmer should read is Code Complete. It goes over all stages of development in a high level overview that applies to any project.

I would then move onto Algorithms by Sedgewick and Wayne. I tried reading Introduction to Algorithms because it was strongly suggested to me, but it goes into higher level math really quick. I haven't taken calculus since high school and never took any higher level math classes in college, so I got lost after about page 30.

After that, I would just look for a book dedicated to design patterns in the main language you work with. There are some overlapping patterns between languages, but it's best to be practical about what you learn.

E` sulla mia scrivania da alcuni anni, presenza fissa (rileggo pezzi ogni tanto).

Insieme a lui anche questi:

https://www.amazon.it/Clean-Code-Handbook-Software-Craftsmanship-ebook/dp/B001GSTOAM

https://www.amazon.it/Code-Complete-Developer-Best-Practices-ebook/dp/B00JDMPOSY/

e questo

https://www.amazon.it/Practice-Programming-Addison-Wesley-Professional-Computing-ebook/dp/B00HU50A12/

Non lo sto chiedendo strettamente per me, ma piuttosto per avere una conversazione sull'argomento (e magari per imparare qualche nuovo trucco).

Grazie comunque per aver citato uno dei libri che piu' apprezzo sull'argomento.

Code Complete is a favourite of mine.

It might be aimed a little more at the professional than the student, but if you become a career software developer, it is an invaluable asset.