Do you vote thumbs up for short code?

Question

While trying to come up with some coding ideas, I noticed that I might turn short example code, like a list comprehension, or tuple iteration, into my votable code.

Do you think this is good practice in terms of going in with all the unvoted on short code like that from the tutorials that people copy and paste in?

Also, do you think the code should have a certain length?

Answer 1

If you want people to notice your code, a crucial part in the SoloLearn system is that you have to blend into the community, get to know where the active users are. By getting followed, your code gets noticed because people get notified for codes by people they subscribe to. It starts off hard at first, but by providing quality content, you will get rewarded in no time.

All the best. (≧▽≦)/🍪

Answer 2

I admire short codes which has good functionalities. This means that the programmer has a concise and precise way to get the job done.

While the end product is of utmost importance, a short code triumphs a longer code of similar functionalities.

If you are asking if short codes are 'liked' on SoloLearn in general, I have a few really short codes which have got great response from our users. Just go ahead and show us what you've got. :>

Answer 3

Yes, but in my mind it seems to bog down the voting system if I want to have the following practice code voted on:

[print(value) for value in range(0,100)]

Although I did spend time years back learning this, should it really be votable code when it's just condensed python code, instead of the complex graphics code that seems to get voted on in the "non-scripting" languages?

Answer 4

I'm, personally, for something like a *Critic's Badge*, which would encourage people to run, and vote on new code, whether it's small, or large.

Answer 5

There's a group of people who compete on who will complete a task with shortest code possible. Of course that only concerns scripting languages which do not carry redundant syntax ;)

Hint: Sssss....🐍

Answer 6

It sure can be fun to make or see short code. But the most important features of code must be
1. its usability
2. its readability
3. its comments
and last but important
4. ease of maintenance.

Short code doesn't necessarily mean effective code. Effective meaning that saving a few bytes or clock cycles may not mean that you save time adapting the code for a new project or upgrading an existing project.

So I would suggest smart code. Smart code fulfills the above list and is adapted for what it's doing.

When I make routines I can often see on its look on the screen, without reading it, if it's smart or not. If it looks neat and pretty it usually works like charm.

But many times I leave it rather ugly looking and then I have problems maintaining it with ease. ☺

So I would vote for smart code. 😆