DDD 101 — The 5-Minute Tour

Articles about DDD. It seems to be a good introduction to DDD concept

• What is it?
  • A book 📚
  • An article 📄
  • Other
• What topic or topics does it cover? (check out the topic:* related labels if you need some inspiration)
  • software-design
• Link to:
  • DDD 101 — The 5-Minute Tour

📚Book proposals

@daviceitor: "Working with legacy code"
@SantiMA10: "Agile Technical Practices Distilled" (facilitator)
@fernandofreije: "Extreme programming"
RobertoM: "Head first designing patterns"

🤔 Retro

😱 One thing that surprised me:

@daviceitor: The extreme programming philosophy looks really nice, I would like to start to read it in the next weeks
@fernandofreije : It seems like all the books we have read have a lot of "good practices" in common, like they are all going in the same direction.
@SantiMA10: Everything is connected, I mean there are a lot of references between each book: same vocabulary(pair programming, TDD...), one book recommends another book, (Agile Technical Practices Distilled -> Working with legacy code)...

🤓 One thing that I learn:

@daviceitor: I should start to be more aware of the patterns on the development process and be more conscious about which pattern I'm applying and why.
@fernandofreije Revisiting old patterns that I already had forgotten. as @daviceitor said, we should be more aware of their existence.
@SantiMA10: Everything needs its time, a super interesting book may not be the one you have to read at that time.

😅 One thing that I would like to do differently:

@daviceitor: We should have some preparations before the bookclub in order to keep it shorter(the last session long about 1 and a half hour)
@fernandofreije: Just timings and finding a way to make books more available for remote guests.
@SantiMA10: As @daviceitor and @fernandofreije we need to improve timing and remote assistance.

More info about the book.

Left here just for reference purposes.

Learn to spot red flags in your React/JavaScript code

Use this description to give us as much information as you can about your proposal!

• What is it?

  • A book 📚
  • An article 📄
  • Other

• Link to: https://medium.freecodecamp.org/learn-to-spot-red-flags-in-your-react-javascript-code-d52d5fac85f4

Link

A Comprehensive Guide To Mobile App Design

• What is it?

  • A book 📚
  • An article 📄
  • Other

• Link to: smashingmagazine.com

Clean Architecture: A Craftsman's Guide to Software Structure and Design

I've not been a big fan of Uncle Bob recently but this book might be helpful for us to read...

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://www.amazon.es/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164

How to deal with dirty side effects in your pure functional JavaScript

Use this description to give us as much information as you can about your proposal!

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link:
  https://jrsinclair.com/articles/2018/how-to-deal-with-dirty-side-effects-in-your-pure-functional-javascript/
• It is quite long so I would consider to split it into two sessions.

Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems

Data is at the center of many challenges in system design today. Difficult issues need to be figured out, such as scalability, consistency, reliability, efficiency, and maintainability. In addition, we have an overwhelming variety of tools, including relational databases, NoSQL datastores, stream or batch processors, and message brokers. What are the right choices for your application? How do you make sense of all these buzzwords?

In this practical and comprehensive guide, author Martin Kleppmann helps you navigate this diverse landscape by examining the pros and cons of various technologies for processing and storing data. Software keeps changing, but the fundamental principles remain the same. With this book, software engineers and architects will learn how to apply those ideas in practice, and how to make full use of data in modern applications.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://dataintensive.net/

Arquitectura de código en NodeJS

Es una serie de 3 artículos. No son excesivamente largos, por lo que quizás podamos leer los 3 de una tacada.

• What is it?

  • A book 📚
  • An article 📄
  • Other

• Link: https://ivanguardado.com/posts/2018-06-08/arquitectura-codigo-nodejs.html (podéis ver los enlaces a las 3 partes al final del artículo del enlace)

Info about the book @ Amazon.

Left here just for reference purposes.

Introducing Hooks

Hooks are a new API proposed by React which have created a good level of noise on Twitter and the blogosphere.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://reactjs.org/docs/hooks-intro.html

“Mismatch: how inclusion shapes design”- Kat Holmes

Sometimes designed objects reject their users: a computer mouse that doesn't work for left-handed people, for example, or a touchscreen payment system that only works for people who read English phrases, have 20/20 vision, and use a credit card. Something as simple as color choices can render a product unusable for millions. These mismatches are the building blocks of exclusion. In Mismatch, Kat Holmes describes how design can lead to exclusion, and how design can also remedy exclusion. Inclusive design methods―designing objects with rather than for excluded users―can create elegant solutions that work well and benefit all.

Holmes tells stories of pioneers of inclusive design, many of whom were drawn to work on inclusion because of their own experiences of exclusion. A gamer and designer who depends on voice recognition shows Holmes his "Wall of Exclusion," which displays dozens of game controllers that require two hands to operate; an architect shares her firsthand knowledge of how design can fail communities, gleaned from growing up in Detroit's housing projects; an astronomer who began to lose her eyesight adapts a technique called "sonification" so she can "listen" to the stars.

Designing for inclusion is not a feel-good sideline. Holmes shows how inclusion can be a source of innovation and growth, especially for digital technologies. It can be a catalyst for creativity and a boost for the bottom line as a customer base expands. And each time we remedy a mismatched interaction, we create an opportunity for more people to contribute to society in meaningful ways.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• What topic or topics does it cover?
  • UX
  • Design
  • Accessibility
• Link: https://mitpress.mit.edu/books/mismatch
• The author is currently the UX Design Director @ Google

Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series)

Accountability. Transparency. Responsibility. These are not words that are often applied to software development.

In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process.

The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years. This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a program of continuous improvement based on:

• Five core values consistent with excellence in software development
• Eleven principles for putting those values into action
• Thirteen primary and eleven corollary practices to help you push development past its current business and technical limitations

Whether you have a small team that is already closely aligned with your customers or a large team in a gigantic or multinational organization, you will find in these pages a wealth of ideas to challenge, inspire, and encourage you and your team members to substantially improve your software development.

You will discover how to:

• Involve the whole team—XP style
• Increase technical collaboration through pair programming and continuous integration
• Reduce defects through developer testing
• Align business and technical decisions through weekly and quarterly planning
• Improve teamwork by setting up an informative, shared workspace

You will also find many other concrete ideas for improvement, all based on a philosophy that emphasizes simultaneously increasing the humanity and effectiveness of software development.

Every team can improve. Every team can begin improving today. Improvement is possible—beyond what we can currently imagine. Extreme Programming Explained, Second Edition, offers ideas to fuel your improvement for years to come.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• What topic or topics does it cover?
  • Economics of software development, cost of change.
  • Planning, development, design, testing and facilities strategies.
  • Implementing XP (adopting, retrofitting, lifecycle, roles, limits…)
• Links:
  • Available at Amazon, O'Reilly, IT Revolution…
  • 90+ excerpt available at Nicole's website
  • Reviews at goodreads
• Dave Thomas (The Pragmatic Programmer) says:

"This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there's an excellent chapter on 'primary practices, ' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change.' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk."

More info about the book @ Amazon.

Left here just for reference purposes.

More info about the book.

Left here just for reference purposes.

Accelerate

The science of lean software and DevOps: building and scaling high performing technology organizations

Accelerate your organization to win in the marketplace.

How can we apply technology to drive business value? For years, we've been told that the performance of software delivery teams doesn't matter―that it can't provide a competitive advantage to our companies. Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance―and what drives it―using rigorous statistical methods. This book presents both the findings and the science behind that research, making the information accessible for readers to apply in their own organizations.

Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance. This book is ideal for management at every level.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• What topic or topics does it cover?
  • Software delivery (performance)
  • DevOps
  • Lean Software
  • Scaling high-performing technology organizations
• Links:
  • Available at Amazon, O'Reilly, IT Revolution…
  • 90+ excerpt available at Nicole's website
  • Reviews at goodreads
• Martin Fowler says: "2018 Software Book of the Year".

SacrificialArchitecture

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://martinfowler.com/bliki/SacrificialArchitecture.html

Testing Microservices, the sane way

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16

Presentational and Container Components

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0?source=linkShare-b0980ca6228-1533533073
• I would recommend to read this along with this small piece from the Redux documentation:
  https://redux.js.org/basics/usagewithreact#presentational-and-container-components

Link.

Left here just for reference purposes.

More info @ Amazon

Left here just for reference purposes.

JS Objects Series

a serie of three articles related to JS "inheritance".

All articles can be read in a week as they are not too long.

• What is it?

  • A book 📚
  • An article 📄
  • Other

• Link to:

  • Part 1: JS Objects: Inherited a Mess
  • Part 2: JS Objects: Distractions
  • Part 3: JS Objects: De"construct"ion

More info about the book.

Left here just for reference purposes.

An Overview of JavaScript Testing in 2018

Use this description to give us as much information as you can about your proposal!

• What is it?

  • A book 📚
  • An article 📄
  • Other

• Link to: https://medium.com/welldone-software/an-overview-of-javascript-testing-in-2018-f68950900bc3

It is quite long so, I would suggest to read the article in two weeks

Info about the book.

Left here just for reference purposes.

Inversion of Control Containers and the Dependency Injection pattern

[...] In this article I dig into how this pattern works, under the more specific name of "Dependency Injection", and contrast it with the Service Locator alternative. The choice between them is less important than the principle of separating configuration from use.

• What is it?
  • A book 📚
  • An article 📄
  • Other
• Link: https://martinfowler.com/articles/injection.html