This reminds me of Steve Yegge's discussion of "n00b programmers". Yegge has more broadly reckoned there are two types of programming styles: fast/prototyping (wherein you just fix problems as they come up when you run the code), and slower/careful (wherein you try to ensure there are no problems before deploying the code).
Yegge describes the 'n00b' programmer as 'scared' of code. Putting as little code on the screen as possible, and ensuring everything you need to understand the code is as close to the code is possible. (In contrast, Yegge reckoned someone familiar with the code can work with a dense clump of spaghetti). https://steve-yegge.blogspot.com/2008/02/portrait-of-n00b.ht...
OP's suggestion to the extent of "I prefer fully qualified names, so I don't have to guess whether the item was imported or defined in the same file" reminds me of that.
I think with at least Rust, though.. Rust has great tooling; but I'd say practically requires good tooling to use. (Especially if you're unfamiliar with Rust).
Yegge describes the 'n00b' programmer as 'scared' of code. Putting as little code on the screen as possible, and ensuring everything you need to understand the code is as close to the code is possible. (In contrast, Yegge reckoned someone familiar with the code can work with a dense clump of spaghetti). https://steve-yegge.blogspot.com/2008/02/portrait-of-n00b.ht...
OP's suggestion to the extent of "I prefer fully qualified names, so I don't have to guess whether the item was imported or defined in the same file" reminds me of that.
I think with at least Rust, though.. Rust has great tooling; but I'd say practically requires good tooling to use. (Especially if you're unfamiliar with Rust).