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.

But when you are participating in a competition let's say some coding competition or interview process, then speed matters right? And that too a lot I feel.

Vaibhav Agarwal
– Vaibhav Agarwal

2012-10-12 16:42:18 +00:00
Commented Oct 12, 2012 at 16:42
@cdkMoose that's good but can you also suggest me how to start competitive programming means from where to start?

Vaibhav Agarwal
– Vaibhav Agarwal

2012-10-12 16:55:00 +00:00
Commented Oct 12, 2012 at 16:55
@VaibhavAgarwal Project Euler problems 1 to 50: while it isn't competitive (unless you are trying to be one of the first people to solve the most recent problem), it is challenging and the type of question one might expect in a coding competition or interview process.

user40980
– user40980

2012-10-12 17:00:51 +00:00
Commented Oct 12, 2012 at 17:00
@Vaibhav, I would start competitive programming the way I would start any other competition: Practice, Practice, Practice.

cdkMoose
– cdkMoose

2012-10-12 17:02:48 +00:00
Commented Oct 12, 2012 at 17:02
1

@Vaibhav: You posted that you want to learn programming. If that is the stage you are at, I personally don't think you should be concerned with competitive programming at all. That can come after you have developed your skills. As far as interviewing, I don't ask my interview candidates to write complete programs. I am more concerned with their understanding and thought processes. I am trying to develop a confidence that they could solve the problem, not that they would solve it in record time.

cdkMoose
– cdkMoose

2012-10-12 17:06:01 +00:00
Commented Oct 12, 2012 at 17:06

| Show 1 more 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 »