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.
Required fields*
- 1+1: I have yet to hear of a startup that has trouble finding people. I also have yet to hear of a startup that doesn't have trouble finding good people.Jason Baker– Jason Baker2010-11-08 21:56:03 +00:00Commented Nov 8, 2010 at 21:56
- 1Upvoting partly because that's the only idea I've had for hiring from the deep end of the talent pool, particularly if you can't judge properly yourself.David Thornley– David Thornley2010-11-08 21:57:17 +00:00Commented Nov 8, 2010 at 21:57
- 1+1 for great advice. i tend to avoid applying for jobs that put too much emphasis on a particular language skill because great programmers don't have trouble transitioning to a new language. that's why, for me a formal computer science background is very important.numan– numan2010-11-08 22:50:08 +00:00Commented Nov 8, 2010 at 22:50
- 7-1 for BS attitude towards C# and Java programmers. There's simply nothing magical about Haskell or LISP. As a C#/.NET developer, I'll stack my passion and commitment to excellence in software engineering against anybody's. And what's more, there will be a whole lot of others who feel as I do.Adam Crossland– Adam Crossland2010-11-09 00:27:02 +00:00Commented Nov 9, 2010 at 0:27
- 3Here's an analogy to point out what Adam & others are missing: Pick any well known sports team, talk to the fans, and you'll get everything from really passionate fans to disinterested glory hunters. Pick a small lesser known team, and almost all the fans will be of the passionate type. There might be more passionate fans for the big team, but they're like needles in haystacks compared to the smaller team.Peter Boughton– Peter Boughton2010-11-09 13:18:21 +00:00Commented Nov 9, 2010 at 13:18
| Show 7 more comments
How to Edit
- 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
How to Format
- 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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you