Jim Lewis has 3 audiobooks on Listento.it, narrated by 3 narrators. The most-rated is Domain Driven Design.
Hacking: Book 2
Summary
Have you heard of Kali Linux and want to use the application to safeguard against hackers? Do you want to learn penetration testing using Kali Linux and, at the same time, ensure that your Kali Linux system is safeguarded from the outside world? Do you want to build strong core Linux fundamentals so that you can adapt to any Linux flavor available today? Then, this is the right book for you. This will prove to be valuable knowledge, specifically when you are working with a time constraint. This depth of knowledge is useful when you are troubleshooting issues, struggling to customize a tool as per your project’s requirement, or using Kali Linux in a large-scale environment. If you are looking to go deep-sea diving into the ocean of intellectually rich information and are curious about Kali Linux as your gear, this book will definitely help you with the swim. This book takes into account first-time Kali Linux users who are looking for a place to start with, as well as experienced Kali Linux users who want to deepen their knowledge and understanding. The book is also bound to teach something new to users who have been with Kali Linux for years but are looking to organize their need for Kali Linux and expand it further by filling the gaps in their understanding. The Kali Linux skills in this course will help you understand Linux better and also serve as a platform to launch you into the world of information security. In this audiobook, you will learn: How to download Kali Linux and install it Fundamentals of Linux Configuration of Kali Linux Securing Kali Linux Penetration testing Creating firewalls And much more... The book has been designed in a way so that you can understand Kali Linux from its beginnings. You don’t have to complete the entire book to get started, as each and every chapter has its own module for Kali Linux pragmatically. There are code snippets throughout the book so that you can put every chapter to practice on a real computer as you progress with each chapter, one by one. If you’re interesting in learning the tips and tricks to hacking with Kali Linux, then what are you waiting for? Click the "buy now" button to get started today!
©2020 Jim Lewis (P)2020 Jim Lewis
Domain-Driven Design
Summary
Have you always wondered if there is a better way to build a software or application? Did you want to see if you can avoid using the waterfall model and focus more on the business value? Do you want to see how you can use the domain knowledge of the business when you write the code? If you answered yes to these questions, you have come to the right place. Domain-driven design will help you tackle various complexities in software development. This book does not talk about any specific languages or technologies. It provides information on what domain-driven design is and its systematic approach. It will present you with an extensive set of experience-based techniques, best practices, and some fundamental principles to help you develop various software projects that use complex domains. This book incorporates different examples based on applications to illustrate the use of domain-driven design in software development. You can learn to use domain models to make the development effort dynamic and focused. The standard patterns and best practices will provide a common language for the development team. DDD not only helps you refactor the code but also the underlying model in the logic using the Agile development model. This provides teams with a deeper insight into the model and domains. It will also improve the communication between a developer and a domain expert. DDD addresses modeling and design for various complex systems. In this book, you will learn about: What is domain-driven design? How does DDD add value to the business? Why is strategic thinking important? Some challenges faced in DDD Introduction to some attributes in DDD-domains, subdomains, bounded contexts, aggregates, entities, value objects, and factories Using context maps to understand the boundaries in the code Understanding domain events, repository patterns in DDD and more Using DDD, you can improve the development of software or applications. What are you waiting for? Grab a copy of this book now!
©2020 Jim Lewis (P)2020 Jim Lewis
Domain Driven Design
Summary
Let's address the critical question right off the bat: why do you have to read this book? If you have a knack for software development, please do not throw this opportunity away. Now is your chance to become an expert. When reliable approaches function without domain-driven design, such denial of this technology or market environment become costly. Even medium-sized mobile apps benefit immensely from the structure of the application of this amazing architecture. Too often, developers only chuck lines of code at problems that can be fixed with vital structural changes. Domain Driven Design does a great job in incorporating industry conditions into aspects of software development. For example, this book focuses on how the accuracy of the model driven design involves constant communication in multiple occasions, and developers separated by team/locations do not participate in continual contact. Recommendations are provided on segmenting the software as a consequence of the market reality. This will enable efficient modeling across independent teams. Such approaches also take political problems within groups into consideration, as well as the collaboration of overburdened departments and legacy systems. In fact, the book points out a claim that many developers are protesting against, but this is particularly true: Not all developers in a group need to pursue the same approach. The claim does not mean that developers are expected to use arbitrary solutions; it implies that programmers are not allowed to tie each other to a unique solution if they can address fundamentally different problems. Two teams working on your device may have a "user" category and may have a consumer category. But perhaps, Team A wants a customer as part of the payment process, or Team B needs a customer as part of a support system. Should we use all departments in the same customer class? Perhaps not. Maybe, they should have consumer-grade billing and support. Then, each consumer includes only the actions they need for the job they have to do. Nevertheless, you will find considerable resistance to solutions like this. Critics are complaining of "unnecessary duplication", but in fact, it is not replication, and it is needed. For similar reasons, the book tends to support the possibility of locking "bounded context." Furthermore, this beginner's guide is right on the money when it comes to structuring code in a manner that allows for business structure. The book also emphasizes concentration and project management in a sense that also helps teams to operate independently without the dictator and the design.
©2019 Jim Lewis (P)2020 Jim Lewis