Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

That's been my idea: come up with something viable, solid so that people could see it in action and feel something real is in place. However, a friend of mine suggested to invite other devs from day-1, in order to avoid a lot roadmap changes later on.

Gelmir
– Gelmir

2011-03-07 14:22:09 +00:00
Commented Mar 7, 2011 at 14:22
13

@Shehi Why would someone join a project without a single line of code written and just vaporware? I've seen projects with working products struggling to get more developers. I wouldn't waste time trying to find developers without something to show.

Vitor Py
– Vitor Py

2011-03-07 14:51:02 +00:00
Commented Mar 7, 2011 at 14:51

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »