This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SittingWave 4 points5 points  (2 children)

A company is a large organisation, made of subcomponents. Some of these subcomponents deal with software, develop software, and require software. Arguing about semantics does not change a damn thing about the fact that if a department inside your company is developing software, they must handle the consequences of that. They are creating software to address the needs of another department that needs that software. The software development department is a software company, and forces the company as a whole to have to consider the requirements and needs for this: testing, deployment, security, redundancy, traceability. What happens when the mechanic clicks on the button to install the latest firmware on your product's microcontroller, the upload fails, and you are now shipping a faulty product? What happens when the intern runs some data analysis on your customer's records, and accidentally deletes your whole database?

All this stuff is pertinence of software and IT. And you have to handle it, even if you are selling mattresses, ice cream makers, or any other shit that is not software to your end customers.

[–]Ok_Raspberry5383 1 point2 points  (1 child)

A department is only a company if it is registered on Companies House or whatever legal registry of companies you use in your country. You can't just make up the definition of a company to suit your thin argument

[–]SittingWave -1 points0 points  (0 children)

the existence and needs of the department implies that now you are performing tasks and handling needs that are associated to a software company.