171–175 of 175 posts
Earlier quoted context omitted.
To be fair, JS appears in 'loved' as Node.js.
Ah, I overlooked that. Though - without checking the original questions - that still suggests an element of "came for JS; stayed for Node".
Earlier quoted context omitted.
So... If one was a great developer through the 90s to today and didn't write C++, C#, Java, or a line of JavaScript, what the hell were they writing? PHP? Perl? Great developers are great because they love what they do, they're critical thinkers, and they've got an ability to find creative solutions to problems. Great developers are not great because they hate 'the man' and refuse to write code in the languages put f…
> If JavaScript wasn't the best we had available to us to create dynamic UIs in the biggest distribution platform in the history of civilization, we'd be using something else. This is circular: "Because we use the thing, it's the best. If it weren't the best, we wouldn't use it. We use it because it's the best." Companies use non-best things all the time, even when the better options are cheaper, easier, faster, safe…
Earlier quoted context omitted.
The thing is, with the ML code or the code for robotics that I've written over years, it's been predicated on the fundamentals of software development I've learned doing everything else. Good habits are good habits, disorganized code is disorganized code. In some ways all the C/C++ I've written for my various robots and gadgets have been easier than even web development UI code because my button is LITERALLY a button…
I agree with your point. When I said "development skills" it was not a judgement about talent, rather about "body count".
The upside for people that do this, as I alluded to, is that if you have these skills and want to do a new thing in a new field, it's an option. Things like SO will help you play with the new thing in the new field where you might otherwise not have any help.
Earlier quoted context omitted.
I think there are some big holes in the list of occupations. Let's say you work in a place with a "microservices" architecture. You write in Java or Ruby or another language. Which occupation are you on this list? Why is there a "backend web developer" but not "backend developer"?
What would be the front end in your example? You'd just be "a developer". I tend to avoid jobs which self describe as backend as I have no interest in web development and my experience is if it is listed as "backend developer" that it's probably too geared towards web development for my tastes.
> for the third year in a row, "full-stack developer" was the most common response [for occupation] Might be a loaded question, but doesn't full-stack mean just "web developer"? From the survey, "Full-stack developers are comfortable coding with 5 to 6 major languages or frameworks (vs. 4 for everyone else)" -- with knowing a bit of Wordpress that's fairly easy to collect: php, sql, html, javascript, css. Done. Or fu…
e.g., using common options:
- A front end web developer would be HTML/CSS.
- A back end web developer would be HTML/CSS/MySQL/PHP (or equivalent).
- Full-stack all of the above plus Apache and Linux.