Is it possible to program just for the sake of code?

Question

Programming

What if programming is attracted not by the ability to develop software, but by the fact that you are simply interested in inventing algorithms for tasks whose interface does not go beyond the command line? Is it possible to make money with this, and if so, what is the name of this position in the team, when all your work consists in writing exactly the algorithm? Is there such a position in general in its pure form, or is it in the aggregate part of the competence of a standard developer?

Answer 1

but the fact that you are just interested in inventing algorithms for puzzles whose interface does not go beyond the command line?

In fact, there is a suspicion that you solved a few simple problems, you succeeded, and it scares you that in order to go further, you need to learn a bunch of new things again.
To write algorithms and not program at the same time, you need to write very cool algorithms.
For example, write a sort that will work faster than quicksort ( https://ru.wikipedia.org/wiki/%D0%91%D1%8B%D1%81%D...
Write an archiving algorithm that will compress better than at least the default 7zip, but at least better than the default zip
Write your own implementation of sha2 encryption
And only then we'll see if you really like working with algorithms, or if you procrastinate in secret from yourself.

Answer 2

Most likely like this:
What you consider an achievement and what you want to earn money on - those tasks an ordinary programmer clicks every day on the top ten.
Therefore, no one needs your skill.
As Saboteur rightly said - in order to make money on this, you need to be able to invent things a couple of orders of magnitude more difficult.
If you are interested in pure theory, then this is such a science as "mathematics".

Answer 3

interesting to come up with algorithms

To be honest, most algorithms have already been invented this way, the question is the most efficient implementation
What specific problem are you solving? Find someone who needs to solve it.
The creator of the compiler/interpreter for the programming language)
A modern developer in high-level languages, frameworks often does not even know what is under the hood of certain functions, and probably ... he doesn’t need to know)

Answer 4

attracts? Yes. especially if these tasks are in demand in business. I will give a simple example, I am ready to offer 1500 for a code that would solve the "backpack problem" to obtain the optimal size / volume of the parcel.

Answer 5

A person who designs algorithms is called a "software architect". Its task is to implement the customer's wishes in the form of algorithms. This is a top position and a kid from the street is not taken there. To work in such a position, you need to be able to understand the client.
Programming for the sake of writing code is called shit coding, usually treated by a psychiatrist

Answer 6

Is it possible to make money with this, and if so, what is the name of this position in the team, when all your work consists in writing exactly the algorithm? Is there such a position in general in its pure form, or is it in the aggregate part of the competence of a standard developer?

I would first ask myself a few questions ...
What can you "give out to the mountain" that a standard developer cannot do?
The algorithm will be faster, less gluttonous to resources, more stable?
Again - what kind of algorithm will it be? If "take input data" -> "do it well" -> "return result" - then why should a standard developer be so happy? Detailing an algorithm to the point where it can be easily implemented is, you see, not so far from programming.