TODO markers and typo fixes

This commit is contained in:
steveej 2015-10-20 19:50:47 +02:00
parent 3b73778483
commit 93e48d45bd

View file

@ -8,17 +8,17 @@ The most recent project that I want to name is called [embEDUx][embEDUx], and it
My main part within that project was to design the overall architecture of the build system and to develop the specification for the system archive and the method of processing it to a complete system archive.
Additional experience in this area comes from my work on projects for customers that consulted me to advise and administer their IT small-business infrastructure.
Altogether, I've had the chance to gather requirements and form certain expectations of the perspective of three major IT roles, the system administrator, the system architect and the application developer.
* What is a system administrator?
* What is an application developer?
* What do they focus on?
Altogether, I've had the chance to gather requirements and form certain expectations from the perspective of three major IT roles: the system administrator, the system architect and the application developer.
* TODO: What is a system administrator?
* TODO: What is an application developer?
* TODO: What do they focus on?
Typically the system administrator doesn't necessarily think about work-flow of an application developer and vise versa.
The system architect unfortunately isn't oftentimes involved in the decision making of the administrator and application developer.
This circumstance can and eventually will lead to applications running on systems that have undergone severe workarounds to make it work at all.
The DevOps movement, which is a modern term and attempt to combine the three aforementioned three roles, has been trying to solve the described problem with tools for automatic system configuration.
* Interface of these roles are
* TODO: describe interfaces of these roles
* OS configuration
* Network topology management
* Application and dependency deployment