Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update README.md #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
azarboon wants to merge 2 commits into ochococo:master
base: master
Choose a base branch
Loading
from azarboon:patch-1
Open

Update README.md #129

azarboon wants to merge 2 commits into ochococo:master from azarboon:patch-1

Conversation

Copy link

@azarboon azarboon commented Jun 11, 2024

Before diving into any of the patterns, readers should be reminded of two fundamental laws in software architecture:

1.Everything is a trade-ff
2."Why is more important than the how"

So, readers face the nuances and reality of these patterns from the beginning. These two laws are coined by two thought leaders in software architecture: Mark Richards and Neal Ford. They have explained these two laws in various conference talks and books. For example, here you can read about these two laws here:

https://www.infoq.com/podcasts/software-architecture-hard-parts/

Also, here is a book for reference:
https://a.co/d/fKOodW9

  • Read CONTRIBUTING.md
  • Only edited files inside source folder (IMPORTANT) and commited them with a meaningful message
  • Ran generate-playground.sh, no errors
  • Opened playground, it worked fine
  • Did not commit the changes caused by generate-playground.sh
  • Linked to and/or created issue
  • Added a description to PR

Before diving into any of the patterns, readers should be reminded of two fundamental laws in software architecture:
1.Everything is a trade-ff
2."Why is more important than the how"
So, readers face the nuances and reality of these patterns from the beginning. These two laws are coined by two thought leaders in software architecture: Mark Richards and Neal Ford. They have explained these two laws in various conference talks and books. For example, here you can read about these two laws here:
https://www.infoq.com/podcasts/software-architecture-hard-parts/
Also, here is a book for reference:
https://a.co/d/fKOodW9 
Copy link
Owner

ochococo commented Aug 2, 2024

@azarboon Hi, thanks for contributing. Agreed with the comment, don't mind adding that.

Please follow instruction to only edit files in source folder, thank you 🙏

Copy link
Author

azarboon commented Aug 3, 2024

@azarboon Hi, thanks for contributing. Agreed with the comment, don't mind adding that.

Please follow instruction to only edit files in source folder, thank you 🙏

Thanks. I followed your suggestion and changed the source file.

FYI, I'm editing files on my browser. In case I added / removed unnecessary spaces, kindly please fix them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /