The Tech Beacon site has posted a list of thirty-five programming habits that make your code "smell", little things that you might do every day without knowing they could be causing issues with the long term maintenance of your code.

Bad habits are hard to break and even harder if you don't realize that what you're doing is undermining your work. If you know but don't care—that would be the worst. But you're here, aren't you?

As a programmer, I've seen a lot of poor practices, not just around code, but also around teamwork skills. I've been guilty of practicing many of these bad habits myself. Here are my top 35 bad programming habits, organized into four categories: code organization, teamwork, writing code, and testing and maintenance.

They've broken up the bad habits into different categories to make it a bit easier to consume:

• Code organization
• Teamwork
• Writing code
• Testing and maintenance

I think just about any developer out there as, at one time or another, fallen into the trap of one or more of these bad habits.

On Kinsta.com Daniel Pataki has posted a list of seven things not to do in PHP 7 when it's finally released. It's no secret that there's a lot of new functionality coming with this new version but that also potentially means some bad practices coming along with them.

I’ve already shared some of the upcoming features of PHP 7, in this article I thought I’d take a look at some of the bad patterns we should stop using as we switch to the lightning fast PHP 7.

Among the things on his list are suggestions like:

• Do Not Use mysql_ Functions (removed from core)
• Do Not Use PHP Close Tags At The End Of A file
• Do Not Perform Queries In A Loop
• Do Not Trust User Input

Some of the suggestions do have a direct relation to what PHP 7 has to offer but most of them are just good practices to follow during your development work. Quite a few good tips in there, especially if you're relatively new to the language and want to start with PHP 7 and go.

In this new post from Vidyut Luther on PHPCult.com, he mentions some difficulties he had installing some new PHP software - caused by bad habits the programmers used that caused trouble down the line. To help prevent further abuses of these issues, he lists out some of them.

His list so far is:

• Turning "register globals" on
• using shot open tags
• using the ASP style of tagging
• single-line condition statements (without the curly braces)
• improper use of exit()
• assuming settings on a remote server

For each of the above options, he briefly covers his opinion as to why they're wrong and can cause some serious headaches down the line. Most advanced programmers out there know about most of these issues, and have learned to work without them.

In this new post from Vidyut Luther on PHPCult.com, he mentions some difficulties he had installing some new PHP software - caused by bad habits the programmers used that caused trouble down the line. To help prevent further abuses of these issues, he lists out some of them.

His list so far is:

• Turning "register globals" on
• using shot open tags
• using the ASP style of tagging
• single-line condition statements (without the curly braces)
• improper use of exit()
• assuming settings on a remote server

For each of the above options, he briefly covers his opinion as to why they're wrong and can cause some serious headaches down the line. Most advanced programmers out there know about most of these issues, and have learned to work without them.