Skip to content

Commit b7821f8

Browse files
authored
Polish About Us section
1 parent 001bcf6 commit b7821f8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -167,13 +167,13 @@ See our [`CONTRIBUTING.md`](https://github.com/the-whole-fruit/manifesto/blob/ma
167167
168168
## About
169169
170-
**Why?** This project is the result of many years of added frustration. Time and time again we've seen _great_ ideas, projects and developers who, due to poor communication, either put a ceiling on their success or turn a wonderful experience into a frustrating one. We've grown so frustrated with this, that we felt compelled to do something about it. We felt the urge to actually promote _the importance of good writing_ in web development.
170+
**Why?** We’ve been in the software industry for more than a decade. And we've seen too many developers who, due to poor communication, either put a ceiling on their success or turn a wonderful piece of code into unusable trash. We've grown so frustrated with this, that we felt compelled to do something about it. We felt the urge to speak up and promote _the importance of good writing_ as part of a developer’s work. And we hope you’ll help us spread the word.
171171
172-
**Who are we?** A [software developer](https://tabacitu.ro) and [a copywriter](https://ro.linkedin.com/in/andreiiordache). This is an unlikely alliance, we know. But it's probably the best mix for starting a project like this.
172+
**What's the plan?** To start a movement, baby! To make a dent in the developer’s world. To hammer in the idea that _words matter_ and that _it's not difficult_ to get decent at writing (definitely not more difficult than learning a new programming language). We want to see fewer and fewer projects that are _hurt_ by their communication. And long-term, we want to completely eliminate the stereotype that developers are bad at communication. In fact, we believe it could become the exact opposite. And we’re committed to build the tools to make that happen.
173173
174-
**What's the plan?** Ideally, to start a movement. To spread the word, little by little, that _words matter_ and that _it's not difficult_ to get decent at writing (definitely not more difficult than learning a new programming language). We want to see fewer and fewer projects that are _hurt_ by their communication. And long-term, we want to completely eliminate the stereotype that developers are bad at communication. In fact, we belive it could become the exact opposite!
174+
**Who are we?** A [software developer](https://tabacitu.ro) and [a copywriter](https://ro.linkedin.com/in/andreiiordache). This is an unlikely alliance, we know. But it's probably the best mix for starting a project like this.
175175

176-
**What's the catch?** No catch, really - we're doing this because we believe it needs to be done. In the spirit of full disclosure, though, we are [writing a book](https://writingfordevs.com) on this topic. A half-a-page `contributing.md` section can get you from _bad_ to _decent_. A book can probably take you from _decent_ to _good_. The book is mostly written - we've tried to cram all our writing experience inside it. But it's still a long way from launching, because now we want _other developers_ to tell us what _they've learnt_ makes better writing in software. We're not sure what form this feedback will take, but if this is a problem you've had to fix yourself, and feel you have something to say about this, please reach out to us at <a href="mailto:contact@writingfordevs.com">[email protected]</a>. We might even start an interview series, a podcast, something like that, where we try to learn as much as possible from others, and share that information with everyone.
176+
**How can I learn more about writing effectively?** We are [writing a book](https://writingfordevs.com) for software developers. So, if a brief `contributing.md` section can get you from bad to decent, think what a book can do for you. While we work on the book, we’re going to share a lot of useful titbits, so [follow us on Twitter](https://twitter.com/writingfordevs) and be sure to [subscribe to our newsletter](https://writingfordevs.com/#download). Also, we would love to hear your ideas - just drop us a line at [contract@writingfordevs.com](mailto:[email protected])
177177

178178
<br>
179179

0 commit comments

Comments
 (0)