It took me ten years to get my first dev job (previously I was in Ops/SysAdmin role).
I had done OOP at University, but at the time the Gang of Four and Design Pattern didn't exist. Also I would say that I was more of a procedural based programmer (Pascal, C, COBOL and Assembly).
So fast forwards to my first dev job, I found myself struggling with concepts that peers took for granted. Nearly all my code looked more like procedural, rather than the message passing.
If I could do it all again, I would've asked my manager to send me on an OOP course rather than a .NET course which left me even more confused.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It took me ten years to get my first dev job (previously I was in Ops/SysAdmin role).
I had done OOP at University, but at the time the Gang of Four and Design Pattern didn't exist. Also I would say that I was more of a procedural based programmer (Pascal, C, COBOL and Assembly).
So fast forwards to my first dev job, I found myself struggling with concepts that peers took for granted. Nearly all my code looked more like procedural, rather than the message passing.
If I could do it all again, I would've asked my manager to send me on an OOP course rather than a .NET course which left me even more confused.