CSE 110 ASU FALL PRACTICE QUESTIONS AND
DETAILED SOLUTIONS
◉ SWE > Coding.
Answer: Coding is only part of software work. SWE also includes
requirements, design, testing, communication, deployment,
operations, and maintenance.
◉ Socio-technical system.
Answer: Software is shaped by both technology and people: users,
devs, teams, managers, org culture, economics, laws, and incentives.
◉ Design Engineering.
Answer: The creative side: figuring out what to build, how users
think, possible designs, tradeoffs.
◉ Production/Process Engineering.
Answer: The disciplined side: building reliably, testing, deploying,
maintaining, and improving process.
◉ FAANG fallacy.
, Answer: Just because a big/successful company does something
does not automatically mean it is good engineering. Economic
success does not equal engineering quality.
◉ Technical debt.
Answer: Future cost created by skipping important work now, like
tests, documentation, code quality, architecture, or maintainability.
◉ Resume Driven Development.
Answer: Choosing tools/tech because they look good on your
resume, not because they are best for users or the project.
◉ Technical investment.
Answer: Spending time now on something like tests, automation,
docs, or architecture to save more time/risk later.
◉ 10x Developer.
Answer: A high-output developer, but the reading warns that "10x"
can be mythologized. A toxic high performer can cause 10x trouble.
◉ Postel's Law / Robustness Principle.
Answer: "Be conservative in what you send, liberal in what you
accept." Applied to SWE professionalism: control your own work
strictly, be adaptable with others.
DETAILED SOLUTIONS
◉ SWE > Coding.
Answer: Coding is only part of software work. SWE also includes
requirements, design, testing, communication, deployment,
operations, and maintenance.
◉ Socio-technical system.
Answer: Software is shaped by both technology and people: users,
devs, teams, managers, org culture, economics, laws, and incentives.
◉ Design Engineering.
Answer: The creative side: figuring out what to build, how users
think, possible designs, tradeoffs.
◉ Production/Process Engineering.
Answer: The disciplined side: building reliably, testing, deploying,
maintaining, and improving process.
◉ FAANG fallacy.
, Answer: Just because a big/successful company does something
does not automatically mean it is good engineering. Economic
success does not equal engineering quality.
◉ Technical debt.
Answer: Future cost created by skipping important work now, like
tests, documentation, code quality, architecture, or maintainability.
◉ Resume Driven Development.
Answer: Choosing tools/tech because they look good on your
resume, not because they are best for users or the project.
◉ Technical investment.
Answer: Spending time now on something like tests, automation,
docs, or architecture to save more time/risk later.
◉ 10x Developer.
Answer: A high-output developer, but the reading warns that "10x"
can be mythologized. A toxic high performer can cause 10x trouble.
◉ Postel's Law / Robustness Principle.
Answer: "Be conservative in what you send, liberal in what you
accept." Applied to SWE professionalism: control your own work
strictly, be adaptable with others.
