generated from nyu-software-engineering/git-practice
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e423442
commit 320adb4
Showing
1 changed file
with
10 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,10 @@ | ||
# 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). | ||
|
||
# NYU SWE INTRO | ||
|
||
This project is an introduction to github and git workflow practice. There is a link to an interesting article (IMO) on software engineering and why it is interesting. | ||
|
||
## Read this article!! | ||
|
||
[Interesting Article](https://anthony-dandrea.medium.com/the-value-of-having-no-strong-opinion-in-software-engineering-26bea1ebc181) | ||
|
||
I find this article intriguing because it delves into the nuanced world of opinions in software engineering, emphasizing the impact opinions have on design, implementation, and overall career growth. The piece skillfully navigates the progression of engineers from lacking strong opinions to developing and leveraging them for career advancement. What particularly caught my attention is the exploration of the value in not having a strong opinion, especially when dealing with less-than-critical decisions. The author's witty call back to the article title, humorously suggesting a more accurate but verbose alternative, adds a touch of lightheartedness to the complex subject. As someone who often grapples with the challenge of balancing opinions in collaborative environments, the article provides valuable insights into how embracing a "No Strong Opinion" stance can contribute to efficient decision-making, team dynamics, and individual growth in the software engineering realm. |