Programming Labs

Question

Programming

Programming labs are looked at mainly for design (solution method, external specification, problem statement), and programs are looked at in passing. They explain this by the fact that they are preparing us for writing technical specifications. Is this normal, do you really have to write this in TK?

Answer 1

       I think that both the ability to write technical specifications and the skills of writing good code are important, and most importantly, the ability to take mathematical or other knowledge to write really cool programs. In the university program, the main task is to teach how to formalize the task correctly, learn analytical thinking, and gain general knowledge in the basics of areas and directions for this specialty. The goal is not to teach students any particular programming language or sharpen them for any particular technology, because these are things that can be mastered very quickly with good basic knowledge.
       Although if the labs are in programming, then all the same, I think that it would be nice to do the slightest review of the code to identify errors and avoid their appearance in the future (whatever one may say, but the subject is still called programming).
       And now I’ll answer your specific question, that if you don’t want to work all your life as an ordinary “bydlocoder”, then you should be able to write technical specifications, but besides that, be able to apply mathematical methods and algorithms in practice.
       Thank you for your attention and success in your studies!

Answer 2

In many adequate firms, the programmer is spared unnecessary formalities, provided that he writes code well. But it all depends on the specialty. TK, coordination of specifications falls on the shoulders of the product manager.

Answer 3

Depending on who and where you will work. Programmers, as a rule, do not write technical specifications; analysts or someone acting in their duties (testers, for example) do this. Often development is carried out without technical specifications at all, just in the bug tracker the manager describes what he wants. So, in the first approximation, you are taught incorrectly.

Answer 4

Documentation skills in a career are not decisive, but useful.
It is very bad that programming is not actually taught in programming, but it is good that at least they are introduced to formalism.
Come in handy.

Answer 5

Don't count on labs, write for yourself and for yourself