4 ms·

I definitively do not want to critique your workflow, that would be pretty dumb by me, just two comments to your points that I don't agree with in full. > Like

I definitively do not want to critique your workflow, that would be pretty dumb by me, just two comments to your points that I don't agree with in full. > Like? I have an 80 column width by default. To not let my code run the entire length of the screen for obvious reasons. Also, it is code smell IMHO if you have to write that much of code in a single line. What about a split view? I'd be far less productive if my screen wouldn't have space for 4 split view's for >> 80 columns in my editor + a small terminal split by terminal multiplexer. > Visual cues. I can immediately know if my linter finds something wrong. Hmm, while there are a few things like renames of variables/functions/... or (type) signature changes for that to happen outside the view one is currently editing in, it's only solving part of the problem — as other files can have those issues too and require changes, so one needs to run a check/lint test or build anyway.

KrishnaShripad 5y ago
> What about a split view? I'd be far less productive if my screen wouldn't have space for 4 split view's for >> 80 columns in my editor + a small terminal split by terminal multiplexer. This includes using split views. Of course I have to mention that I use Mac as my primary development machine (which comes with 5K retina display). So already have plenty of real estate. It might be an issue on laptops. But I haven't tried it to give feedback on that. I just gave my personal anecdote. > so one needs to run a check/lint test or build anyway If your entire team is already using lint from the start you wouldn't have to worry about it. Even if not, you would have typically run the linter when you cloned the repo. The build process should have lint as a pre-step anyways. So the chances of you having non linted files elsewhere is minimal. And when you rename functions/variables you can rename as symbol, which will change it in all files that reference it. If you have the right workflow setup you wouldn't have to worry about other files being affected.
KrishnaShripad 5y ago
> or (type) signature changes This I would consider as refactoring. It won't be just making normal edits anymore. Yes, when it comes to refactoring everything goes haywire. But that is a conscious decision isn't it? Then you'll for sure be running linter/tests anyways. So yes, in such cases what you said is valid. However, having a mini-map won't be a hindrance here. At least I don't see how it could be. It might be useless for this case. That I agree.

KrishnaShripad 5y ago

> What about a split view? I'd be far less productive if my screen wouldn't have space for 4 split view's for >> 80 columns in my editor + a small terminal split by terminal multiplexer. This includes using split views. Of course I have to mention that I use Mac as my primary development machine (which comes with 5K retina display). So already have plenty of real estate. It might be an issue on laptops. But I haven't tried it to give feedback on that. I just gave my personal anecdote. > so one needs to run a check/lint test or build anyway If your entire team is already using lint from the start you wouldn't have to worry about it. Even if not, you would have typically run the linter when you cloned the repo. The build process should have lint as a pre-step anyways. So the chances of you having non linted files elsewhere is minimal. And when you rename functions/variables you can rename as symbol, which will change it in all files that reference it. If you have the right workflow setup you wouldn't have to worry about other files being affected.

KrishnaShripad 5y ago

> or (type) signature changes This I would consider as refactoring. It won't be just making normal edits anymore. Yes, when it comes to refactoring everything goes haywire. But that is a conscious decision isn't it? Then you'll for sure be running linter/tests anyways. So yes, in such cases what you said is valid. However, having a mini-map won't be a hindrance here. At least I don't see how it could be. It might be useless for this case. That I agree.