This is a very interesting poll for me. As a software architect who works in big tech, what I find the most fascinating is that most of the core component/backend developers tend to lean conservative or non-political, whilst the front-end developers tend to lean more left.
Now, this is not to say that all front-end developers are liberal and all back-end are conservative, but with nearly 20 years of experience in this field, it has been my experience to find them coalesced in separate groups like this at larger companies.
Here is a very high level summary of what frontend/backend consist of:
Backend: Things like network transport layers, container orchestration, kernel development, core database development, things that are written in assembly, C or C++. The foundation or infrastructure of things so-to-speak.
Frontend: Web languages like HTML, Javascript, UI, API things, elevated languages such as C#, Python, etc.
It makes sense that Oracle, being a huge database and core development platform, and with a large emphasis in direct hardware programming (think Sun Microsystems acquisition), has such a large base of conservatives in comparison to everything else out there in the big tech world. Also, willing to bet that most of the 8.3% of conservatives that work at Microsoft are mostly in kernel, cloud and operating system development.
To build something complex requires thinking outside of the box, something that the left seemingly has a hard time doing. I find my more liberal leaning colleagues copying and pasting code from stack exchange, albeit slightly modified to fit whatever project they are working on and calling it a day a good chunk of the time (in most cases, it doesn't work as they had confusingly intended and requires intervention on the commit, hence the common stereotypical jokes with regard to stack exchange).
They also ask the most questions directed to backend things that have been answered before numerous times, as if it didn't "click", when pressed as to why their push to production didn't execute as flawlessly as they had intended. Commonly blaming the infrastructure, or the OS, or anything else they deem as problematic, rather than looking to themselves as the problem.
The conservatives are the "Atlas" holding up the world, if Atlas shrugs, everything else falls apart.
Very interesting poll indeed.
This is a very interesting poll for me. As a software architect who works in big tech, what I find the most fascinating is that most of the core component/backend developers tend to lean conservative or non-political, whilst the front-end developers tend to lean more left.
Now, this is not to say that all front-end developers are liberal and all back-end are conservative, but with nearly 20 years of experience in this field, it has been my experience to find them coalesced in separate groups like this at larger companies.
Here is a very high level summary of what frontend/backend consist of:
Backend: Things like network transport layers, container orchestration, kernel development, core database development, things that are written in assembly, C or C++. The foundation or infrastructure of things so-to-speak.
Frontend: Web languages like HTML, Javascript, UI, API things, elevated languages such as C#, Python, etc.
It makes sense that Oracle, being a huge database and core development platform, and with a large emphasis in direct hardware programming (think Sun Microsystems acquisition), has such a large base of conservatives in comparison to everything else out there in the big tech world. Also, willing to bet that most of the 8.3% of conservatives that work at Microsoft are mostly in kernel, cloud and operating system development.
To build something complex requires thinking outside of the box, something that the left seemingly has a hard time doing. I find my more liberal leaning colleagues copying and pasting code from stack exchange, albeit slightly modified to fit whatever project they are working on and calling it a day a good chunk of the time (in most cases, it doesn't work as they had confusingly intended and requires intervention on the commit, hence the common stereotypical jokes with regard to stack exchange).
They also ask the most questions directed to backend things that have been answered before numerous times, as if it didn't "click", when pressed as to why their push to production didn't execute as flawlessly as they had intended. Commonly blaming the infrastructure, or the OS, or anything else they deem as problematic, rather than looking to themselves as the problem.
Very interesting poll indeed.