[BOOK]: Human Factors in Systems Engineering by Alphonse Chapanis

Developed in 1996 with a 4.00 rating in goodreads.

This reference is concerned with how systems should be designed as opposed to a description of current practices. The author approaches design from the perspective of those human considerations--the human factors--that have to be taken into account to make machines and systems match the people who use and service them. Describes how to develop tools, machines, and systems so that they will be safe, comfortable and easy to use. Discusses the requirements for establishing a successful human factors program and includes 30 tables, 110 illustrations, and an extensive bibliography.

[BOOK]: To Engineer Is Human: The Role of Failure in Successful Design By Henry Petroski

Developed in 1985 with a 3.66 rating in goodreads, this amazing book talks about what is to be an Engineer in a very real way.

"Reading Petroski's fine book is not only a delight, it is a necessity." 

--Houston Chronicle

How did a simple design error cause one of the great disasters of the 1980s—the collapse of the walkways at the Kansas City Hyatt Regency Hotel? What made the graceful and innovative Tacoma Narrows Bridge twist apart in a mild wind in 1940? How did an oversized waterlily inspire the magnificent Crystal Palace, the crowning achievement of Victorian architecture and engineering? These are some of the failures and successes that Henry Petroski, author of the acclaimed The Pencil, examines in this engaging, wonderfully literate book. More than a series of fascinating case studies, To Engineer Is Human is a work that looks at our deepest notions of progress and perfection, tracing the fine connection between the quantifiable realm of science and the chaotic realities of everyday life. 

"Alert, inquisitive, unspecialized, wholly human...refreshingly eclectic." 

--The Spectator 

"Henry Petroski is an ardent engineer, and if he writes more good books like this, he might find himself nominated to become the meistersinger of the guild. [This is] a refreshing plunge into the dynamics of the engineering ethos...as straightforward as an I-beam." 

--Science

[VIDEO]: Software Engineer: Reality vs Expectations 2

From the popular Youtube channel "ENGINEERED TRUTH" 

You can also see the first part here.

Dave graduated from Carnegie Mellon with a masters in Computer Science & Electrical Engineering. He then worked for Qualcomm for 4 years in San Diego, CA. After that he started working for startups in New York where he continues to work today.

[VIDEO]: Software Engineer: Expectations vs Reality

From the popular Youtube channel "ENGINEERED TRUTH".

What's it really like doing Software Engineering? Let's see on the next video, is a very expensive one but is worth it!

The guest, Matthew Martin, has worked at Boku, Logitech, Xoom, and is now working on his own startup called Blosssom.

Table of Contents:

• 1st Card: I will write code all day 
• 2nd Card: Scaling is hard 
• What makes a crappy software engineer? 
• What do you like for when you hire people and how do you determine if they have that quality? 
• 3rd Card: College degree is necessary 
• Truth about Dev Bootcamps 
• 4th Card: Do developers right a lot of algorithms? 
• 5th Card: Does anyone really "Know a language"? 
• What's a good first programming language to learn? 
• What's your company, Blossom Finance, about? 
• What are the main positions that you hire for? 
• What's a typical day for you? 

[VIDEO]: Network Engineer: Expectations vs Reality

From the popular Youtube channel "ENGINEERED TRUTH" let's see this amazing video.

Interview with computer information engineer. What network engineers actually do vs what they thought they would be doing. Is management information systems a good career?.



Questions:

• How did you guys become Network Engineer 
• What do you guys do? 
• Do Network Engineers have to be social? 
• What are the real job duties? 
• Explain your job to a HS student 
• Is there varying work load? 
• Do you do the same sh*t over & over? 
• Is there a lot to learn? 
• Can one person know everything? 
• School vs Work 
• How secure are networks? 
• What car do you guys drive?

History of Systems Engineering

The term systems engineering can be traced back to Bell Telephone Laboratories in the 1940s. The need to identify and manipulate the properties of a system as a whole, which in complex engineering projects may greatly differ from the sum of the parts' properties, motivated various industries, especially those developing systems for the U.S. Military, to apply the discipline.

When it was no longer possible to rely on design evolution to improve upon a system and the existing tools were not sufficient to meet growing demands, new methods began to be developed that addressed the complexity directly. The continuing evolution of systems engineering comprises the development and identification of new methods and modeling techniques. These methods aid in the better comprehension and the design and development control of engineering systems as they grow more complex. Popular tools that are often used in the systems engineering context were developed during these times, including USL, UML, QFD, and IDEF0.

In 1990, a professional society for systems engineering, the National Council on Systems Engineering (NCOSE), was founded by representatives from a number of U.S. corporations and organizations. NCOSE was created to address the need for improvements in systems engineering practices and education. As a result of growing involvement from systems engineers outside of the U.S., the name of the organization was changed to the International Council on Systems Engineering (INCOSE) in 1995. Schools in several countries offer graduate programs in systems engineering, and continuing education options are also available for practicing engineers.

What is Systems Engineering?

Systems engineering is an interdisciplinary field of engineering that focuses on how to design and manage complex engineering systems over their life cycles. Issues such as requirements engineering, reliability,logistics, coordination of different teams, testing and evaluation, maintainability and many other disciplines necessary for successful system development, design, implementation, and ultimate decommission become more difficult when dealing with large or complex projects. Systems engineering deals with work-processes, optimization methods, and risk management tools in such projects. It overlaps technical and human-centered disciplines such as industrial engineering, control engineering,software engineering, organizational studies, and project management. Systems engineering ensures that all likely aspects of a project or system are considered, and integrated into a whole.

The systems engineering process is a discovery process that is quite unlike a manufacturing process. A manufacturing process is focused on repetitive activities that achieve high quality outputs with minimum cost and time. The systems engineering process must begin by discovering the real problems that need to be resolved, and identify the most probable or highest impact failures that can occur - systems engineering involves finding elegant solutions to these problems.