Post History

> the answer is incredibly long

It really isn't - though it might look that way because of the extensive use of large font headlines. I think it is a good answer - there's no problem in discussing multiple ways of doing something, addressing every angle. That's good engineering, rather.

> Would it make more sense to split the content up and make a separate answer for each?

No, because that would fragment the explanations and answers don't get displayed in any particular order. It would just make it harder to compare the different possible techniques.

Overall I don't think there's a problem here. Someone who can't be bothered to read 1-2 pages of technical text shouldn't work with technology in general and not with programming in particular. Rather, you are expected to read some 500 to 1000 pages of technical text before you can title yourself "naive beginner in programming language x".

> Leave the question and answer as is

I think so, it is fine. 

Also some article category won't really change anything here. For example have a look at this similar "paper category" post I wrote over at Electrical Engineering: [Why should I not use dynamic memory allocation in embedded systems?](https://electrical.codidact.com/posts/286121) It's essentially just a Q&A still, but one single post. Like in your case I needed to make a list of various practices and fragmenting it over multiple posts would only make it less readable.