The Environment for the Software Engineer

1987 ◽  
pp. 78-86
Author(s):  
A. Nico Habermann
Keyword(s):  
Software Engineer

The 10 best practices for remote software engineering

2021 ◽  
Vol 64 (5) ◽  
pp. 32-36
Author(s):  
Vanessa Sochat
Keyword(s):  
Software Engineering ◽  
Best Practices ◽  
Software Engineer ◽  
Human Element

Focusing on the human element of remote software engineer productivity.

Computing in the statistical office

2021 ◽  
pp. 1-14
Author(s):  
Mark P.J. van der Loo
Keyword(s):  
Business Process ◽  
Process Model ◽  
Software Engineer ◽  
Business Process Model ◽  
Official Statistics ◽  
Research Software

Computing with data is at the hart activity of the statistical office. Yet, the area of technical computing often falls between the two stools of data analysts and IT developers. In this paper we analyze the importance of computational skills in the Generic Statistical Business Process Model. Next, we give an overview of computational topics that are of importance to the statistical office. Many of these skills turn out to be of highly technical nature. After this, we try to provoke a wider discussion on the role of technical computing by 1) introducing the role of the Research Software Engineer into the field of official statistics and 2) propose a six semester bachelor’s curriculum in official statistics.

Can your software engineer program your PLC?

2016 ◽  
Author(s):  
Alastair J. Borrowman ◽  
Philip Taylor
Keyword(s):  
Software Engineer

Can a Software Engineer Afford to be Ethical?

1997 ◽  
pp. 92-99
Author(s):  
Colin Myers ◽  
Tracy Hall ◽  
Dave Pitt
Keyword(s):  
Software Engineer

scholarly journals Patriarchy in the Digital Conjuncture: An Analysis of Google’s James Damore

2020 ◽  
Author(s):  
Ben Little ◽  
Alison Winch
Keyword(s):  
Scientific Method ◽  
Software Engineer ◽  
High Stress ◽  
Silicon Valley ◽  
High Status ◽  
The Core ◽  
Core Belief ◽  
The World ◽  
New Form

Our case study looks at the events surrounding the sacking ofGoogle engineer James Damore who was fired for authoring a memo which stated that women are biologically less suited to high-stress, high-status technical employment than men. Damore, asserting that his document ‘was absolutely consistent with what he’d seen online’, instantly became an ambivalent hero of the alt-right. Like the men who own and run the companies of Silicon Valley, the software engineer subscribes to the idea that the world can be understood and altered through the rigorous application of the scientific method. And as he draws on bodies of knowledge from evolutionary psychology and mathematical biology, we see how the core belief structures of Silicon Valley, when transferred from the technical to the cultural and social domain, can reproduce the sort of misogynistic ‘rationalism’ that fuels the alt-right. We argue that Damore’s memo is in line with Google’s ideology of ‘dataism’: that is the belief that the world can be reduced to decontextualised information and subject to quantifiable logics.Through its use of dataism, the memo reveals much about the similarities and continuities between Damore, the ideas laid out n his memo, and Google itself. Rather than being in opposition, these two entities are jostling for a place in the patriarchal structures of a new form of capitalism.

scholarly journals Introduction to Containerization

2020 ◽  
Vol 6 (12) ◽  
pp. 294-300
Author(s):  
Raghav Goel and Dr. Bhoomi Gupta
Keyword(s):  
Large Scale ◽  
Software Engineer ◽  
Service Oriented Architecture ◽  
Use Case ◽  
Production Environment ◽  
Code Base ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Multiple Services ◽  
Local Machine

Are you a software engineer/developer/coder or maybe even a tech enthusiast who is thinking of agility, parallel development and reducing cost. In the early twentieth century, we witnessed the rise of Service Oriented Architecture (SOA), which is a software architecture pattern that allows us to construct large-scale enterprise applications that require us to integrate multiple services, each of which is made over different platforms and languages through a common communication mechanism, where we write code and multiple services talk to each other’s for a business use case, but sometimes we end up with one big monolithic code base whose maintenance becomes difficult. Nowadays clients are using cloud and paying for on-demand services without effectively utilizing resources. These problems invite micro-services. In this paper, I am going to discuss how one should use scale application in a production environment and local machine

Sign in / Sign up

Export Citation Format

Share Document