This is much better. Atwood concedes that a little bit of coding knowledge is important just as understanding basic plumbing issues are important.

However my opinion is that coding is just a tool like an arc welder, wood lathe, or propane torch. There is no point in teaching someone how to use them if they have no real interest in having a passion for using them. They should know they exist for a certain class of problem, but that's it. Then if they decide that they want to be able to build furniture then let them dive in.

I wouldn't say it's stupid. IMHO the important bit is that people need to become better problem solvers. This means understanding the problem and knowing which tool to use, but this also means that learning new tools effectively is just as important. Besides you know the saying, when all you know is how to hammer then everything is a nail.

Anyway, I kind of agree with the author, but I think they needed more stress on the understanding the problem part.

Edit: I hate my phone

I always thought MS sucks at support which would be the only reason to go with a corporate backed distribution. Unless they plan on only bringing MSSQL and office to their distribution

I don't see how that is possible. Linux is open source. Even if MS manages to take over a distribution and add proprietary binaries to it will probably end like everything else they take over. Look at Nokia for an example.

You're welcome

I was hoping they were all kidding.

Can you elaborate on the security?

I wouldn't knock it for constant updates though. They are a bit in your face, but considering my Firefox install is on 43.0.1 and I've only seen it ask me to restart a handful of times, I am not sure I like being in the dark about updates. If I had more time I think I would want to know why Mozilla is updating Firefox yet again.

Why not both?

Regardless, I am not a fan of ms after having to try and understand their licensing (they have training courses just to understand their licensing). I would love to use their tech more, but they seem to put a giant paywall around it.

You don't get that with OSS. I use SQL server, but because of their ridiculous licensing I would love to jump completely to postgres if given the chance.

I just superficially tried tkinter. Note that in 3.x it's a lower case t. In Python 2.x it's upper case.

It really annoying that people can't cope with conflict. That in order to contribute to something you have to bend over backwards to make sure everybody's feelings are taken into consideration. It's amazing that these people can actually get things done.

Keep in mind that when you get to code in the real world you will find yourself cursing out the dev before you because they had no idea what they were doing. So while they did use "OOP" it was hardly correct. And they did it everywhere.

Anyway, I would say it total depends. If you only have one class like Car then I would say just make it a method of that class. If you had many classes with the same type of method then I would explore other options in the interest of reusability. For example maybe you might want to make a more inclusive parent class and put the method there instead.

You start acting offended over any little thing. Do it respectfully. Say your feelings were "hurt". Demand an public apology and cite the code of conduct. Do it so that it gets so annoying and bogs down development. I would recommend an established alt for doing this.

The point? Show them why a doormat mentality is not the right way to interact with other people. However, it must be done politely and respectfully. Otherwise, they might pick up the actual intent and ban you.

Feelings get trampled when personal work is in the spotlight. Of course you must act professionally and just deal with the possibility that your work might be received with less enthusiasm than you expected or even mockery. It happens. To get butthurt over it tells people you are unable to take criticism well. I wouldn't want to work with those people.

Nor would I want to work with people who apologize for every faux pas. With those people I feel like I never a get straight answer.

How do you feel about Oracle taking over java. I am getting up to speed with java for Android, but part of me is worried that Oracle is going to ruin java with ridiculous licensing and etc.

I totally agree. I have been working on stored procedures that were written by people who were just trying to get things working. A code and fix situation if you will. There was no planning or proper testing.

Anyway, now I have someone helping me and they can easily modify my code, but if they have to look at the old version they're baffled as to where to start looking for how it was done before.

Writing careless code is a cancer in a project, and sometimes the only solution is to kill the code and start fresh