I hate this attitude of my study (when i studied):

"it might be a good idea to teach the students how to program securely by default?"

"oh no but we just want to teach them the basics"

"so why not the secure basics by default?!"

"nah we just want them to get started and understand it, that's all. We'll get to the secure way later on"

Well, fuck you.

The fuck, this is like saying:

we only teach them how to drive the car, speed limits and that other stuff that you need to not die or kill anyone else will come later

@linuxxx CATHAT!!!!!!!!

@ewpratten NOPE!!

@linuxxx it would have been amazing

@ewpratten True!

@linuxxx and I thought it was easier to convince people to do things when they are drinking

So true!

Same here:
(Sample code given by teachers does not work)
- 'hey, wouldn't​'t it be nice if the sample code worked out of the box?'
- 'yeah, sorry. The code was made by my predecessor and it is pretty old. See it as an exercise to practise fixing broken code'
- 'okay... What about these bad coding practices?'
- 'yeah, it is old but it captures the idea so it is good enough.'

That's what they call a university.
@cwizard @iliasib

@max-jak Our university in a nutshell.
Lesson on how to write good code:
Step 1: Do not write bad code
Step 2: Magic
Step 3: Profit

We are only teaching the students about the electricity flow and conductors. Not holding the metal plate while it acts as a conductor is too advanced and we only teach the basics here.

Novice here. From what little I know and the insight I'm getting from the industry on devRant, didn't expect to learn on this platform, suggesting ideas or using the softer "ask the non-coder what they think approach" seems to get nowhere and sometimes ends in catastrophe... Does anyone have suggested solutions for "getting things done the right way" when communicating with outside parties?

@zkoynz The impression you'll get from only reading dev rant is worse than reality - simply because you don't rant about stuff that's all right.

In my experience, most clients listened to what I had to say and valued my professional opinion.
My advice: consider denying requests when you get the feeling that a client will regret his/her own specification at a later point - because you're likely going to be blamed for it.

@Condor I like it when people over engineer stuff. Always fun!

Hahaha, this is how the teach linux at our school. 777 permissions and for example root mysql databases for websites. Atleast they said it is insecure.

@theCalcaholic that seems like great advice for any request, yet I have not practiced it nearly enough. Better late than never. I'll make sure to keep that as an option for myself. Thank you for the insight.

I think that's pretty much the same everywhere. And the "later" that they said, that "later" would never come.

Unless those poor students go through a situation and have to learn it the hard way.

I sincerely wish that the education system would hire smart teachers to teach it the way it should be - the right way. Even if it means having to go an extra mile to explain the topic.