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.
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.