Python Forum
how many do side by side windows for coding? - Printable Version

+- Python Forum (https://python-forum.io)
+-- Forum: General (https://python-forum.io/forum-1.html)
+--- Forum: News and Discussions (https://python-forum.io/forum-31.html)
+--- Thread: how many do side by side windows for coding? (/thread-23306.html)



how many do side by side windows for coding? - Skaperen - Dec-21-2019

i'm curious how many coders do side-by-side windows for code comparing and other things like snipping code from examples (like how to build an email to send if it's your first time to code something that sends email). i've realized that over the past year i have never used a side-by-side display of code, even though my display is big enough to do so. i've been using a wider window so my code can go beyond 80 characters, which it needs to do often enough that i am gladi do it this way.

i guess the issue comes down to which is better to have, the ability to read two scripts in parallel or the ability to avoid wrapping code that uses many more longer names to the next line. i have needed the latter far more often (at least a dozen times a week) than the former (never in the past year).


RE: how many do side by side windows for coding? - Larz60+ - Dec-21-2019

I do it all the time using VSCode as an IDE


RE: how many do side by side windows for coding? - ichabod801 - Dec-21-2019

I rarely do it. I frequently have two windows open, but the second one is for running the code, not the code itself. The one time I do it is documentation reviews with large sections of code, like a class with a lot of methods. I'll leave one window on the docstring, and scroll through the code checking the docstring in the other window.


RE: how many do side by side windows for coding? - Skaperen - Dec-22-2019

how much do you put in the docstring?


RE: how many do side by side windows for coding? - ichabod801 - Dec-22-2019

For a class, I put in one line description with the parent class, any extra description I think is essential to understanding the class, and a one line description of every class attribute (with type), every instance attribute (with type), every method (with return type), and every overridden method.

I can often review that without two screens. But for the last release of t_games I had a GinRummy class with 800 lines of code. Scrolling back and forth to check/fix things became too tedious, so I opened another window.