Materials for an "Intro to software engineering"
Open
Nobody has claimed this yet.
best-practice
learning/ teaching
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Answers:
- Jenny Bryan: https://github.com/jennybc/code-smells-and-feels#readme
- Hadley Wickham: https://mastering-shiny.org/best-practices.html
- Dean Attali: Clean code, by Bob Martin.
- Colin Fraser: The Missing Semester of Your CS Education
- kperese: The imposter handbook
- Vasant Marur: Research software engineering with python
- George Bergolio: https://www.edx.org/course/cs50s-introduction-to-computer-science
- Pete Jarvis:
- Software Engineering: A Practitioner's Approach, Roger S. Pressman
- Refactoring: Improving the Design of Existing Code, Martin Fowler
- Thinking in Systems, Donella H. Meadows
- Perspectives on Data Science for Software Engineering, Tim Menzies
- An Introduction to General Systems Thinking, Gerald M. Weinberg
- The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change, Camille Founier
- Emilie Schario: Also in podcast format: https://medium.com/basecs
- Jeremy Korwin: Read content from the authors of https://agilemanifesto.org/
- https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/acrobat-17.pdf
- https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-005-software-construction-spring-2016/
- Expanding the scope of statistical computing: Training statisticians to be software engineers: https://arxiv.org/abs/1912.13076
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository file, test, or concrete change; it provides a collection of introductory software-engineering materials and links. Start by reviewing the listed answers and existing repository structure, then clarify where these resources belong and what format is expected. Done means the agreed materials are added or organized consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100