Nowadays if that's all you know: you're hosed.
I know, because my 20 year career in IT ended 12 years ago when the green-screen, green-bar paper printout disappeared.
NOW a coder needs to know OOP, i.e., everything is a class, and all things belong within their class. It is when the objects of a particular class become instantiated with values that they take on the essence of becoming. Once they are no longer necessary, they no longer are; everything is ethereal.
It is so strange to discover that procedures can be defined inherently as objects within a "class", e.g., "making coffee". What's really and truly bizarre are "overloading" of procedures (let alone operators). In object oriented programmimg the procedure of such fundamental conecpt as addition can be "overloaded". What's so cool 'bout that is that you don't have to worry 'bout the sequence of code; just define WHAT needs to be done and the compiler and CPU determines how and when it gets done when what needs to get done is actually needed. Isn't that that rat's ass?
Rat’s ass indeed. OOP never made any sense to me.
I mostly wrote code in C and a little assembly. All very straightforward and logical, especially to a hardware guy like me who had some software jobs dumped in his lap.
I tried OOP, my brain locked up.
I love my green screen and green bar paper system. It works.
They’ve been trying to take it away from me for 14 years. They keep taking small bites. “Oh yeah, we forgot to tell you that that file has been migrated to the new system”
Sounds like Java. That class stuff is weird.