Skip to content

Incluir descricao do nosso first keynote #49

@carlisia

Description

@carlisia

No ticket #48 eu proponho listar todos e somente os keynotes na pagina principal.

Da forma que imagino, deveria ter tambem a descricao do talk. Precisa fazer cada item nessa sessao bem menor do que estah. Como exemplo, segue: https://gophercon.com/

A descricao do talk do Bill vai abaixo (e o bio estah no #48):

What happens when your code can’t adapt to change? When the code is so coupled together that changing even one type or function creates a cascading effect of more code changes throughout the entire code base. When this happens, the software becomes unstable, and you face hours (if not days) of lost productivity. Recognizing and minimizing cascading changes across types, functions and methods is how to architect adaptability and stability in your software.

In this talk we will learn how to design software in Go with decoupling in mind. We’ll see how concrete and interface types can be composed together to provide different levels of decoupling and how functions and methods can use interfaces to abstract knowledge about themselves.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions