Answer the question
In order to leave comments, you need to log in
What skills do you often use in your work?
Good day.
I am interested in the following question: what skills (not counting the knowledge of the programming language itself, as well as English) do you often need in your work? For example, the theory of algorithms, the theory of automata, mathematical analysis and others.
Answer the question
In order to leave comments, you need to log in
A very important skill is to stifle your perfectionism and do what you can on time, and not how beautiful.
touch typing, you have to type a LOT of text, erase and type
arithmetic again, often have to count + 1-1 + 1-1, rarely more
good memory - variables, calls - everything that you wrote you need to remember
a trained ass and bladder - two hours To sit in one place, completely distracted from the material, is fraught,
but seriously, various theories help either when thinking about architecture or when analyzing bugs.
When writing code, simple (listed above) skills are more important
The ability to apply patterns to the place.
And, well, as they said above, stifle your excessive perfectionism, and just write, fucking code .
The theory of creation of a software product (TSPP), let's glorify decomposition. <chaos theory> (TX) - not it specifically, but everything that protects the reader of the code from the growth of informational entropy of the brain.
Until GameDev was thrown out of science:
Algorithms, higher mathematics, discrete mathematics, computational linguistics, kinematics, optics, "a bunch of other mathematicians."
And now I’m trying to make websites - I don’t use anything (except TSPP and TX).
I remember with a kind word the teachers of the Russian language, matan and terver - three areas of knowledge that help to understand people, solve problems and set them.
When working with 3D graphics, three-dimensional algebra and geometry helps: count any intersections of polygons, intersections of rays with triangles, write projection formulas for shadows, calculate lighting models, and the like.
When I code physics, it is necessary for physics and mechanics to remember - impulses, forces, moments of forces, moments of inertia.
Building business processes. Within the framework of the university and the specialty, it was an absolutely useless and stupid course, but now I use it, because. I don't work in my profession.
To be able to close oneself from the outside world and not be distracted by external stimuli.
Very often, you need to build something, while not missing something else. And you have to keep a lot of things in your head.
Try to solve the Einstein's Riddle in your mind.
And if at such moments they are distracted, nothing good comes out.
But you also need to be able to switch between tasks.
Increasingly, recently, algorithms are required that are beautifully described by Knuth.
Googling helps a lot when you don’t know something (here are questions on the stack or habré).
Version control systems.
Mathematics is different, of course, depending on the tasks.
Sometimes to prove your case, they explain that what you offer is good or what others offer is nonsense. To do this, weigh the pros and cons. Do not be afraid to express your opinion or point of view, sometimes even when you are not asked. In the meantime, don't lose patience.
Reading someone else's code (code of colleagues or products used).
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question