Good Developer vs Bad Developer

[marcvanriet]

Maybe we should restrict the 'script kiddies' to using PyQt. Python is a very good scripting language and for a would-be programmer easier to learn and use than C++. And the binding with Qt is very good. (Used it 5 years ago on a Linux system, guess it only got better by now, and guess Windows works also fine.)

Then we just have to give them 1 installer that puts Python+Qt+PyQt on their system in 1 step so we get no questions about that.

And then we need a script-kiddy detector in the forum

Best regards,
Marc

[wysota]

Maybe we should restrict the 'script kiddies' to using PyQt. Python is a very good scripting language and for a would-be programmer easier to learn and use than C++.

First of all we have no way of enforcing such a restriction. Second of all people not willing to learn C++ will not be willing to learn Python. According to me the path is education, not restriction. We've been discussing some ideas during Developer Days, we'll see if we can make anything happen. But this requires time.

[stampede]

nice thread

my simple thought:

I think that good developer will tend to reuse the code, when a bad one will just try to rewrite things from scratch. Bad developers likes to write their own code, and good devs know that sometimes it's even more important to read someone else's code and try to improve and reuse it. Bad developers thinks that code written from scratch will always be better than old one.

Good dev: "This function/class/system is a mess. Let's try to do some refactoring."
Bad dev: "This function/class/system is a mess. I will write my own."

Of course there can be situations when only thing left to do is to rewrite, but I think you know what I'm talking about.