I agree with the general ethos - good code doesn't get written by attending meetings all day, or fiddling with org mode. But like all advice, it needs caveats. If you're on a brownfield project where you have very little knowledge of the domain or legacy code, just jumping straight in and spending lots of time in your editor is probably going to result in a lot of frustration and wasted effort.
Comments
I agree with the general ethos - good code doesn't get written by attending meetings all day, or fiddling with org mode. But like all advice, it needs caveats. If you're on a brownfield project where you have very little knowledge of the domain or legacy code, just jumping straight in and spending lots of time in your editor is probably going to result in a lot of frustration and wasted effort.