So, are software developers going to be like actors/musicians/gaffers/etc between jobs, waiting tables at a local bistro? I guess restaurant owners will appreciate having someone around who knows how to reboot the POS system and create new menus in PowerPoint.
I agree with the "specialization is for insects" idea but that doesn't seem to be borne out in the current job market. Most employers are looking for highly specific skill sets and using software to screen out resumes from anyone without those tight requirements. Interviews, if you get one, are usually focused on narrow language/framework trivia rather than concepts and previous project results.
Connections are important but maintaining them can be difficult for the typical introverted programmer. Given that bridges are often burnt both ways (example: security escorting the 'shamed' out the door) when departing a job and the paranoia of lawsuit prevention restrictive covenants, connections with previous jobs is also difficult in some cases.
Software developers are already doing "waiting tables" jobs. It is called low paying IT jobs until I launch my own products or go for higher studies. Patrick (well know as patio11 and kalzumeus.com) has described his initial jobs. He would work late into night, check into his rooms, develop his software. He launched the software. Ran a successful firm. One thing led to another and now he is in Stripe.
I'm generalizing here and quoting a well known example. I'm sure there are plenty of others who didn't succeed developing their own product (looking at myself). But the trend is becoming more and more common.
When I started development, a developer was expected to code db, server side, and front-end. And communicate with clients about the benefits. We started specializing and now we have bootstrap experts who can't figure out server side code even if it is in node.js. Am I talking about developers becoming experts in, say, medical science? No (well, unless they are working in healthcare). But a software developer should understand all layers of software architecture (UI, API, db ...) and do decent job in all layers, if needed.
From my own experience and from the examples I quoted, I definitely see a trend towards collaborative solution creation crossing the borders of corporate entities. The term Hollywood model might have anchored the debate on a different side than intended, but I don't know of any other metaphor which is closer to this point.
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.
So, are software developers going to be like actors/musicians/gaffers/etc between jobs, waiting tables at a local bistro? I guess restaurant owners will appreciate having someone around who knows how to reboot the POS system and create new menus in PowerPoint.
I agree with the "specialization is for insects" idea but that doesn't seem to be borne out in the current job market. Most employers are looking for highly specific skill sets and using software to screen out resumes from anyone without those tight requirements. Interviews, if you get one, are usually focused on narrow language/framework trivia rather than concepts and previous project results.
Connections are important but maintaining them can be difficult for the typical introverted programmer. Given that bridges are often burnt both ways (example: security escorting the 'shamed' out the door) when departing a job and the paranoia of lawsuit prevention restrictive covenants, connections with previous jobs is also difficult in some cases.
Software developers are already doing "waiting tables" jobs. It is called low paying IT jobs until I launch my own products or go for higher studies. Patrick (well know as patio11 and kalzumeus.com) has described his initial jobs. He would work late into night, check into his rooms, develop his software. He launched the software. Ran a successful firm. One thing led to another and now he is in Stripe.
I'm generalizing here and quoting a well known example. I'm sure there are plenty of others who didn't succeed developing their own product (looking at myself). But the trend is becoming more and more common.
When I started development, a developer was expected to code db, server side, and front-end. And communicate with clients about the benefits. We started specializing and now we have bootstrap experts who can't figure out server side code even if it is in node.js. Am I talking about developers becoming experts in, say, medical science? No (well, unless they are working in healthcare). But a software developer should understand all layers of software architecture (UI, API, db ...) and do decent job in all layers, if needed.
From my own experience and from the examples I quoted, I definitely see a trend towards collaborative solution creation crossing the borders of corporate entities. The term Hollywood model might have anchored the debate on a different side than intended, but I don't know of any other metaphor which is closer to this point.