The Uni I graduated from introduced basic coding into every programm, from engineering to humanities to arts. Everyone used chatgpt to get through it without a second glance because they didn’t even understood why they need that. Even management didn’t, I guess, but they wanted to check a box of ‘being modern and progressive’.
It should be explained and deeply inserted into each program with at least a couple of mixed half-IT disciplines, like Databases in Law Practice or Computer vision in QA or Automation in Accounting or MatPlotLib in Countative Studies or… As it was there, it’s an isolated course that’s the same for everyone, it’s on you to create a project connected to your main interest. And, as I heard, no one really made it besides getting a minimal sum to pass.
Basically, it needs effort and understanding from both sides.
Educational bureaucracy strikes again!
It’s likely that you will learn the same exact thing when you’re 35 and need to improve your trade skills, but as a self-study and not an university course with zero relation to real life.
The field of programming is vast, and you totally can learn only the tiny part that is useful to you and ignore everything else. And learning CS to write programs is like learning to design combustion engines to drive a car.
And learning CS to write programs is like learning to design combustion engines to drive a car.
Sometimes.
But often people will “write programs” without a decent understanding of the underlying layers and principles or foundation on which the technology is built. (Even some CS majors will do this.) this will result in weird bugs and behaviors they cannot understand or debug. Meanwhile their peers and managers have begun to use and rely on these programs and even integrate them into larger processes and workflows. Once the bugs start showing up, now you’ve got a big problem.
There are also some basics you’d probably won’t even register breaking without experience, going as far as pushing user credentials and personal data to an open git repository. I did that in my second pet project with just my temp keys to the cloud API, and github flagged that immediately. I guess, having at least the briefiest knowledge could’ve helped newbies avoid errors like that.
I don’t know if it’s bullshit or not, but I discovered that not every person has the mentality of seeing everything through an algorythmic lense, like detecting a repetition in a mundane task - and guessing, if it can be solved with a macro. I invented a lot of simple solutions, like these, or just combos of programs to optimize the workflow in my office, and I see not only my colleagues struggle to use these, many work for years in the least optimal way, even if the program itself, e.g. Excel, provides automated math equations - some still use calculators and put in the result by hand. It got me thinking, maybe IT isn’t for everyone, and other learning\working styles won’t benefit from such education even if it’s given - while acing in something else entirely?
The Uni I graduated from introduced basic coding into every programm, from engineering to humanities to arts. Everyone used chatgpt to get through it without a second glance because they didn’t even understood why they need that. Even management didn’t, I guess, but they wanted to check a box of ‘being modern and progressive’.
It should be explained and deeply inserted into each program with at least a couple of mixed half-IT disciplines, like Databases in Law Practice or Computer vision in QA or Automation in Accounting or MatPlotLib in Countative Studies or… As it was there, it’s an isolated course that’s the same for everyone, it’s on you to create a project connected to your main interest. And, as I heard, no one really made it besides getting a minimal sum to pass.
Basically, it needs effort and understanding from both sides.
Educational bureaucracy strikes again!
It’s likely that you will learn the same exact thing when you’re 35 and need to improve your trade skills, but as a self-study and not an university course with zero relation to real life.
The field of programming is vast, and you totally can learn only the tiny part that is useful to you and ignore everything else. And learning CS to write programs is like learning to design combustion engines to drive a car.
Sometimes.
But often people will “write programs” without a decent understanding of the underlying layers and principles or foundation on which the technology is built. (Even some CS majors will do this.) this will result in weird bugs and behaviors they cannot understand or debug. Meanwhile their peers and managers have begun to use and rely on these programs and even integrate them into larger processes and workflows. Once the bugs start showing up, now you’ve got a big problem.
There are also some basics you’d probably won’t even register breaking without experience, going as far as pushing user credentials and personal data to an open git repository. I did that in my second pet project with just my temp keys to the cloud API, and github flagged that immediately. I guess, having at least the briefiest knowledge could’ve helped newbies avoid errors like that.
I don’t know if it’s bullshit or not, but I discovered that not every person has the mentality of seeing everything through an algorythmic lense, like detecting a repetition in a mundane task - and guessing, if it can be solved with a macro. I invented a lot of simple solutions, like these, or just combos of programs to optimize the workflow in my office, and I see not only my colleagues struggle to use these, many work for years in the least optimal way, even if the program itself, e.g. Excel, provides automated math equations - some still use calculators and put in the result by hand. It got me thinking, maybe IT isn’t for everyone, and other learning\working styles won’t benefit from such education even if it’s given - while acing in something else entirely?