50 Mistakes for Software Developers

Found this while perusing the internet.

Most seem to make sense to my noobish brain.

Thoughts, opinions, comments?

https://www.fabiosilvalima.com/50-common-mistakes-development/

Entry 22 - public class variables instead of using properties - is very common with Unity. I prefer properties myself but they’re not necessarily a bad thing. You don’t really need to have a property if you’re only setting or passing a private variable through without any additional code.

I read a lesson on properties and I was having a hard time grasping it because it seems like the get and set should be reversed, at least in my way of thinking. But as you said they probably aren’t as needed when it’s not user input that’s being passed.

I’m definitely guilty of 35 & 36 - excessive switch / case and recurrent code, but slowly getting better, I think.

And Debugging. I need to learn the proper ways to do it. Currently I use a bazillion Debug.Log statements to debug.

“Not studding, staying at the comfort zone.”

I think it is mostly not good. The article doesn’t have much substance in it and provides no explanation. When you give an advice - “do this, don’t do that”, a good idea is to explain why. This article doesn’t bother to do that. There are a lot of typos, mistakes and strangely constructed sentences on the list - translation is not very good. The writer may be skilled in some web-related technologies, however, but at least some of this stuff may not really apply to Unity3d - as already mentioned by @Ryiah

4 Likes

Properties are only necessary when you need to do stuff during get or set, or you only need get or set. I used to be a big fan of them back in Delphi times, but now I’m not entirely convinced they’re very useful or necessary.

I think a better idea would be to get some programming book, instead of relying on scraps of information from the web. Books beat blogs. IMO.

2 Likes

I’m surprised anyone got to 22. The butchering of the English language through the article is killing me.

Most of the article seems to be very vague. A lot of it is repetitive. And a lot is just the guys own opinion with little substance.

1 Like

https://www.amazon.com/Microsoft-Visual-Step-Developer-Reference/dp/1509301046/ref=lp_697342_1_4?s=books&ie=UTF8&qid=1492749005&sr=1-4

I got this book and am working through it. Only issue is to download and run the samples requires Windows 10 and I’m on Windows 7. It wasn’t clear from the cover and didn’t figure that out until part way through the introduction. So if I do the practice I have to create my own practices.

I just went with the assumption English was not his primary language.

I just thought some might find it interesting reading, but perhaps not.

That’s fairly obvious from the writing style. My point is there are plenty of resources written in decent English, so there is no need to waste time on ones written by people still learning the language.