Success with Mendz.Data.* Packages
More than a month has passed since I published Mendz.Data. Many developers and teams are using Mendz.Data to guide them in developing contexts and repositories for their projects. Simplicity, consistency, productivity, quality and scalability are key motivators.
Mendz.Data provides the tools and guidance that can give projects structured architecture that is maintainable and supportable. Designed from experience, Mendz.Data offers a guiding strategy to let developers practice their own creativity, while at the same time not limiting themselves to "surprises" that future requirements might bring.
The team is central to Mendz.Data's design. It is not designed to enforce. It is designed to guide. I can't stress that enough. The Mendz.Data.Repository(.Async) interfaces can be used to create the basic CRUDS. The same signatures can be used to create variations of the CRUDS methods. For example, an initial Search() implementation can later co-exist with SearchByPartner(), SearchByLOB() or SearchByPeriod() versions using the same signature defined by IDbDataSearchable. It's that straightforward. Likewise, it's that flexible. The guidance is not meant to restrict. The guidance is truly meant to guide.
Mendz.Data is not a solution by itself. It can be used to create solutions. By using the tools and guidance suggested by Mendz.Data, teams can establish software development processes that can be predictable and measurable in terms of consistency, efficiency and quality. The truth is, developers have different styles. Regardless, when working in a team, everyone would still have to agree on some things. Mendz.Data can help start that conversation.
By design, Mendz.Data can help keep things simple without necessarily breaking when things get complicated. Teams can easily agree with Mendz.Data. Get Mendz.Data now and experience for yourself the benefits of starting it right the first time.
Mendz.Data provides the tools and guidance that can give projects structured architecture that is maintainable and supportable. Designed from experience, Mendz.Data offers a guiding strategy to let developers practice their own creativity, while at the same time not limiting themselves to "surprises" that future requirements might bring.
The team is central to Mendz.Data's design. It is not designed to enforce. It is designed to guide. I can't stress that enough. The Mendz.Data.Repository(.Async) interfaces can be used to create the basic CRUDS. The same signatures can be used to create variations of the CRUDS methods. For example, an initial Search() implementation can later co-exist with SearchByPartner(), SearchByLOB() or SearchByPeriod() versions using the same signature defined by IDbDataSearchable. It's that straightforward. Likewise, it's that flexible. The guidance is not meant to restrict. The guidance is truly meant to guide.
Mendz.Data is not a solution by itself. It can be used to create solutions. By using the tools and guidance suggested by Mendz.Data, teams can establish software development processes that can be predictable and measurable in terms of consistency, efficiency and quality. The truth is, developers have different styles. Regardless, when working in a team, everyone would still have to agree on some things. Mendz.Data can help start that conversation.
By design, Mendz.Data can help keep things simple without necessarily breaking when things get complicated. Teams can easily agree with Mendz.Data. Get Mendz.Data now and experience for yourself the benefits of starting it right the first time.
Comments
Post a Comment