Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,19 @@
# Git Practice
A simple project to practice a few git/github workflows. Replace the contents of this file with the contents indicated in the [instructions](./instructions.md).
A simple project to practice a few git/github workflows. Replace the contents of this file with the contents indicated in the [instructions](./instructions.md).


# Git Practice

## Interesting Software Engineering Article

[Technical Debt — Martin Fowler](https://martinfowler.com/bliki/TechnicalDebt.html)

### Why I Found It Interesting

This article explains the idea of **technical debt** and how decisions made during software development can affect a project later. Comparison between technical debt and financial debt was interesting: taking a shortcut may make development easier in the short term, but it can create additional work when the software needs to be changed or extended.

This topic is relevant to software engineering because writing code is not only about making something work once. Developers also need to think about maintainability, readability, and how easily other developers can modify the system in the future. it made me consider more carefully about the trade-offs between developing features quickly and keeping a codebase easy to maintain.

Comment by Linh Tran

I also found the comparison between technical debt and financial debt interesting. It shows how taking shortcuts can save time in the beginning but create more work later. As someone learning software development, it makes me think more about balancing the need to develop features quickly with keeping code readable and maintainable.