WIP: Starting book proposal #2

gwincr11 · 2019-01-18T21:31:45Z

No description provided.

gwincr11 · 2019-01-18T21:35:16Z

book/proposal/proposal.md

+
+## Why is your book different?
+
+Design thinking books are often aimed at hard D design. This book will focus instead on using design thinking tools to create a different sort of outcome then is 


It is different, it really is.... But what to say what to say...

:)

your perspectively is always uniquely yours. Start with your experience and how that experience led up to this way of thinking.

.....your experience gives you a ton of credibility to your views....and your views on design thinking (especially the language/rosetta stone style concept) will prove extremely valuable to others....even those doing design thinking (or thinking they are designedly thinking :))

gwincr11 · 2019-02-04T21:38:15Z

book/proposal/outline.md

+
+## Chapter 1: Organic Software with Design Thinking and Domain Driven Development
+
+Organic software is the modern ideal and a quality needed if we seek to perpetuate the success and social responsibility of open source to a wider set of problems. We seek to serve the whole of life, seeking solutions which effortlessly enhance our environments in a informed, thoughtful and responsible manner.


I am not sure I want to call it organic. Much of this idea is aadopted from the evolution of organic architecture as seen in the early nineteens hundreds. I like the parallel ideas and think they encompass what I am going for well.

I would choose to focus on Domain Driven Development but I am concerned about escaping the dogmatic focus on implementation detail. I like the idea of having a parallel idea in another field to draw comparison with. How we define environment in our scenario is of vital importance however, as software is not organic in the sense of being one with the natural world instead we seek a oneness with the natural environment of the software.

From a softwares perspective the natural environment should be a combination of the hardware environment it is running on and the problem it is solving. Bridging the gap between domain expert and computer hardware is the realm of the programming combining these two disparate worlds into a single environment is the challenge.

The programmer is the god of this natural world, crafting the tools in which the problem solution lives. Any responsible god should focus on the constituents it is affecting more so then the tools which create such a world.

Now I will go watch Tron 😆

I can't believe I missed the Tron reference 😂

Cg book proposal

bruce · 2019-02-14T18:19:26Z

book/proposal/outline.md

@@ -0,0 +1,125 @@
+# Outline for Design Thinking for Developers
+
+## Chapter 1: Organic Software with Design Thinking and Domain Driven Development


Perhaps just "Introduction"

bruce · 2019-02-14T18:22:51Z

book/proposal/outline.md

+
+## Chapter 1: Organic Software with Design Thinking and Domain Driven Development
+
+Organic software is the modern ideal and quality needed if we seek to perpetuate the success and social responsibility of open source to a wider set of problems. We seek to serve the whole of life, seeking solutions which effortlessly enhance our environments in an informed, thoughtful and responsible manner.


I think this persuasive, philosophical description of "organic software" is better placed after the itemized, concrete definition below (otherwise you may lose the reader, who may be thinking "What is this 'organic software' that's the modern ideal? How have I not heard of it before?")

bruce · 2019-02-14T18:24:33Z

book/proposal/outline.md

+
+In this chapter, we will outline how to conduct a successful interview and how to do job shadowing. This includes 
+
+- Using our stakeholder map and context bounding to identify interviewees.


I like the itemized lists in some of the chapters describing the topics you'll dig into. Perhaps do this consistently across the outline?

Reason: Makes it easier for editors/reviewers to scan through to see the scope.

bruce · 2019-02-14T18:26:56Z

book/proposal/outline.md

+
+Often times our problem statement is handed to us due to business needs, however, the process by which we choose the problem to work on and state the problem are often difficult tasks that can be aided by the process. There are also situations in which we may be using design thinking to explore a new process inside our development processes.
+
+Defining a problem statement can be political and difficult to write. Our Rose, Bud, Thorn and Affinity Clustering activities have exposed a number of areas which we can focus on but picking one to focus on is a matter of aligning people. When we do define it we need to ensure the language we use is open enough to encourage our creative process, yet bounded enough to keep us focused on our problem area.


bruce · 2019-02-14T18:32:54Z

book/proposal/proposal.md

@@ -0,0 +1,99 @@
+# Proposal for Design Think for Developers


It's possible the publisher won't want to run with "Design" in the title, as it's easy to mistake for "Visual Design." In any case, you'll almost certainly be asked to provide several titles & subtitles for the book as part of your early interaction with your development editor.

It might be good to prepare some options. (This was one of the more surprisingly difficult tasks for me—besides writing the marketing copy and picking out a cover).

bruce · 2019-02-14T18:37:03Z

book/proposal/proposal.md

+- Unintended consequences of poorly modeled data.
+- Incorrect prioritization.
+
+Our workflows and structures create communication barriers we must break down in order to move our implementations closer to their domains. As developers, our goals should include moving ourselves and our code closer to the domain. This requires understanding not only the problem being solved by a feature but also, more broadly an understanding of the field we are working in.


"As developers, our goals should include moving ourselves and our code closer to the domain." ❤️

bruce · 2019-02-14T18:44:18Z

book/proposal/proposal.md

+- How to evaluate what to build given competing priorities.
+- Understanding the business domain they work in the day-to-day.
+- Building long-lived communication tools that impact internal/external communication and code design.
+


Might make sense to take pains to indicate that these tools will be as "real world" and "actionable" as possible, using examples, concrete situations, etc.

bruce · 2019-02-14T18:46:01Z

book/proposal/proposal.md

+
+## Why we should get excited about your topic:
+
+In the Cathedral and the Bazaar a number of important ideas were set forth related to working more closely with our stakeholder:


Footnote (or inline) full reference to book.

bruce · 2019-02-14T18:50:05Z

book/proposal/proposal.md

+
+In the Cathedral and the Bazaar a number of important ideas were set forth related to working more closely with our stakeholder:
+
+1. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.


Although Markdown will take care of numbering during render, they'll probably read this as plain text. I'd suggest either number using incrementing numbers or (preferably) just use an unordered list.

bruce · 2019-02-14T18:50:59Z

book/proposal/proposal.md

+1. To solve an interesting problem, start by finding a problem that is interesting to you.
+1. Provided the development coordinator has a communications medium at least as good as the Internet and knows how to lead without coercion, many heads are inevitably better than one.
+
+Interestingly it contradicts itself pointing out a major issue with the way we develop software:


"it" -> "the book"

bruce · 2019-02-14T18:52:55Z

book/proposal/sample chapter.md

+After working through these exercise with our domain experts we will look to develop internal documents that can be leveraged for current implementation, future on-boarding and to guide conversations and decisions in the future. We will examine interviewing and job shadowing as our two main methods. 
+
+## Aside on note taking
+Each of these will provide notes and insights we can capture simply. I like to collect these notes on post it's sometimes I color code them for context but this is up to you. Note taking can be simple scratches of words, crude drawings or complex long form notes. 


"post-it notes"

bruce · 2019-02-14T18:55:31Z

book/proposal/sample chapter.md

+
+That being said, interviewing properly is important for the output of the interview.
+
+## Your bias, So am I


"You're biased, and so am I" ?

bruce · 2019-02-14T18:56:54Z

book/proposal/sample chapter.md

+If you start to see questions that can be thought of as confirming an idea or seeking evidence of a belief you are probably in the middle of confirmation bias. Also be cognizant of the tendency humans have to ignore disconfirming information, this is how stereotypes perpetuate.
+
+#### Survivorship biases
+During WW2 the US Military was attempting to strengthen the armor on planes. In order to do this they took stock of where the bullet holes on the planes where located and placed more armor in those locations. This is a great example of the problem with survivorship bias. 


Great anecdote. The more of this type of thing in the book, the better.

bruce · 2019-02-14T18:59:00Z

book/proposal/sample chapter.md

+
+## Asking for permission.
+
+We always need the participants permission when conducting an interview. Seeking permission often takes setup, this is a good time to set expectations. Why are you interviewing people, how will the interviewee be compensated, how many people are you interviewing, where will the interview take place, what will you talk about with them, will you be recoding, who else will be at the interview and any other relevant information is nice. When setting expectations you want to be clear about what you are doing, but don't get to specific. You can start to color response even before you have an interview.


Itemize list

…through-code into cg-book-proposal

starting book proposal

94e0dd7

gwincr11 changed the title ~~starting book proposal~~ WIP:starting book proposal Jan 18, 2019

gwincr11 changed the title ~~WIP:starting book proposal~~ WIP: Starting book proposal Jan 18, 2019

gwincr11 commented Jan 18, 2019

View reviewed changes

gwincr11 added 14 commits January 18, 2019 16:36

addintional excitement

eaf1e85

starting chapter outline

4d2387b

more work on chapter outlines

537f3b9

more proposal

bd23f78

chapter outline

9f2a1e0

chapter #

dd4a2d2

combine first 2 chapters

88d028b

sample chapter started

845ebc3

organic

d84c92d

chapter work

2dc7dfe

more interviewing

195070c

sample chapter

c2d8bf3

editing

b224e3f

more editing

16194b1

gwincr11 commented Feb 4, 2019

View reviewed changes

gwincr11 and others added 11 commits February 5, 2019 20:07

language capture

37a7a43

second attempt at sample chapter

1bfb972

blocks

182d701

outline: minor typos

c805800

proposal: minor edit suggestions

fbc2abf

proposal: minor edit suggestion

ebb89ee

ch2 is so awesomegit push origin cg-book-proposal

cd72da7

ch2 is so awesomegit push origin cg-book-proposal

48eb451

ch2 interview topic

3e39d4d

ch2 who to interview

66230b7

Merge pull request #3 from acrlewis/cg-book-proposal

781ec07

Cg book proposal

bruce reviewed Feb 14, 2019

View reviewed changes

gwincr11 added 6 commits February 19, 2019 11:38

cccchanges

37a23fe

Merge branch 'cg-book-proposal' of github.com:gwincr11/Communicating-…

9695c47

…through-code into cg-book-proposal

update outline and proposal

600a896

book proposal

f15567c

Update proposal

e2c8fc8

update proposal

3cc1214

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WIP: Starting book proposal #2

WIP: Starting book proposal #2

gwincr11 commented Jan 18, 2019

gwincr11 Jan 18, 2019

acrlewis Jan 19, 2019

acrlewis Jan 19, 2019

gwincr11 Feb 4, 2019

gwincr11 Feb 4, 2019

gwincr11 Feb 4, 2019

acrlewis Feb 13, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019

bruce Feb 14, 2019


		## Why is your book different?

		Design thinking books are often aimed at hard D design. This book will focus instead on using design thinking tools to create a different sort of outcome then is


		## Chapter 1: Organic Software with Design Thinking and Domain Driven Development

		Organic software is the modern ideal and a quality needed if we seek to perpetuate the success and social responsibility of open source to a wider set of problems. We seek to serve the whole of life, seeking solutions which effortlessly enhance our environments in a informed, thoughtful and responsible manner.

		@@ -0,0 +1,125 @@
		# Outline for Design Thinking for Developers

		## Chapter 1: Organic Software with Design Thinking and Domain Driven Development


		In this chapter, we will outline how to conduct a successful interview and how to do job shadowing. This includes

		- Using our stakeholder map and context bounding to identify interviewees.


		Often times our problem statement is handed to us due to business needs, however, the process by which we choose the problem to work on and state the problem are often difficult tasks that can be aided by the process. There are also situations in which we may be using design thinking to explore a new process inside our development processes.

		Defining a problem statement can be political and difficult to write. Our Rose, Bud, Thorn and Affinity Clustering activities have exposed a number of areas which we can focus on but picking one to focus on is a matter of aligning people. When we do define it we need to ensure the language we use is open enough to encourage our creative process, yet bounded enough to keep us focused on our problem area.


		## Why we should get excited about your topic:

		In the Cathedral and the Bazaar a number of important ideas were set forth related to working more closely with our stakeholder:


		In the Cathedral and the Bazaar a number of important ideas were set forth related to working more closely with our stakeholder:

		1. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.


		That being said, interviewing properly is important for the output of the interview.

		## Your bias, So am I


		## Asking for permission.

		We always need the participants permission when conducting an interview. Seeking permission often takes setup, this is a good time to set expectations. Why are you interviewing people, how will the interviewee be compensated, how many people are you interviewing, where will the interview take place, what will you talk about with them, will you be recoding, who else will be at the interview and any other relevant information is nice. When setting expectations you want to be clear about what you are doing, but don't get to specific. You can start to color response even before you have an interview.

WIP: Starting book proposal #2

Are you sure you want to change the base?

WIP: Starting book proposal #2

Conversation

gwincr11 commented Jan 18, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment