Skip to content

Clean up structure of the book #2

@traviskaufman

Description

@traviskaufman

There needs to be a clear audience and a clear problem that they have which this book will help them solve. I have this in my head, I just haven't had the space to truly think through it. I feel like I need to "lean canvas" this...

Software Developers struggle to write maintainable code primarily because ???we're not taught how to translate human language to computer language???. This book teaches you how to do that.

This I believe is the entire hypothesis underlying the book and it needs to be laid out clearly. More specifically, it needs to be laid out in such a way as to be engaging and solve their problem.

My next steps are to look at career skills books I've read which have helped me (The Mom Test, Effective JavaScript, Pitch Anything, etc) and better understand the way in which the book presents its ideas, so that I can learn from it and apply it to this book to present the main idea state above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions