I don't believe anyone of us is done learning nor is there one correct way to approach the field. I started programming professionally in high level languages myself. But languages being leaky abstractions, I eventually had to dive into the nitty gritty. Stack vs GC heap allocations. Array locality. Locking and concurrent programming. And so on.
While there could be something to your article about cultural trends, this line struck me as particularly more about your perspective than about cultural shifts: "I hope all this comes as a cold splash of reality for you." There are an endless parade of technical details in our field. Why does your preferred set need to be everyone's path?
There are an endless parade of technical details in our field. Why does your preferred set need to be everyone's path?
I never said that my preferred set needs to be on everyone's path. If you read my article again, you'll notice that I'm not holding up any language as "the one answer". I am merely making the point that all programmers need to eventually master the underlying principles of programming, yet too many avoid them.
Build your career in JS if you like. Or Rust. Or Haskell. Or COBOL, if you are so inclined. Whatever path you take, learn to code well.
In the end coding well probably matters less than making a product that does what people need. Otherwise, no beginners could exist in our field. Although I agree that it is a worthy lifetime endeavor, at least for me.
Coding well is a necessary step to ensuring software is stable and maintainable, both of which are necessary parts of making a product that does what people need.
Beginners certainly don't need to grasp every topic I've outlined right away. The point is simple: if you want to succeed as a programmer, you must pursue it. Avoiding it is a lose-lose scenario.
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.
I don't believe anyone of us is done learning nor is there one correct way to approach the field. I started programming professionally in high level languages myself. But languages being leaky abstractions, I eventually had to dive into the nitty gritty. Stack vs GC heap allocations. Array locality. Locking and concurrent programming. And so on.
While there could be something to your article about cultural trends, this line struck me as particularly more about your perspective than about cultural shifts: "I hope all this comes as a cold splash of reality for you." There are an endless parade of technical details in our field. Why does your preferred set need to be everyone's path?
I never said that my preferred set needs to be on everyone's path. If you read my article again, you'll notice that I'm not holding up any language as "the one answer". I am merely making the point that all programmers need to eventually master the underlying principles of programming, yet too many avoid them.
Build your career in JS if you like. Or Rust. Or Haskell. Or COBOL, if you are so inclined. Whatever path you take, learn to code well.
In the end coding well probably matters less than making a product that does what people need. Otherwise, no beginners could exist in our field. Although I agree that it is a worthy lifetime endeavor, at least for me.
Coding well is a necessary step to ensuring software is stable and maintainable, both of which are necessary parts of making a product that does what people need.
Beginners certainly don't need to grasp every topic I've outlined right away. The point is simple: if you want to succeed as a programmer, you must pursue it. Avoiding it is a lose-lose scenario.