You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the repository is growing I believe we need to take some care about how we structure and present the samples. I was thinking about following improvements:
Each concrete sample should have README file so when people browse the repository they should know what is the goal of a given module and what technologies (including testing) were used.
My**Impl is not really the most appealing strategy for the samples. Therefore I think we could either decide on the common model (eg. Beers ;)) or we leave it up to the sample creator, but with emphasis on giving something real instead of yet another My**Impl
The text was updated successfully, but these errors were encountered:
As the repository is growing I believe we need to take some care about how we structure and present the samples. I was thinking about following improvements:
README
file so when people browse the repository they should know what is the goal of a given module and what technologies (including testing) were used.My**Impl
is not really the most appealing strategy for the samples. Therefore I think we could either decide on the common model (eg. Beers ;)) or we leave it up to the sample creator, but with emphasis on giving something real instead of yet anotherMy**Impl
The text was updated successfully, but these errors were encountered: