I Don't Like Imports
Posted4 months agoActive4 months ago
kevincox.caTechstory
calmmixed
Debate
20/100
Programming PracticesCode OrganizationImport Statements
Key topics
Programming Practices
Code Organization
Import Statements
The author expresses frustration with import statements in programming, sparking a discussion on programming styles and code management.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
8h
Peak period
1
7-8h
Avg / period
1
Key moments
- 01Story posted
Aug 24, 2025 at 5:44 PM EDT
4 months ago
Step 01 - 02First comment
Aug 25, 2025 at 1:38 AM EDT
8h after posting
Step 02 - 03Peak activity
1 comments in 7-8h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 25, 2025 at 5:25 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45008088Type: storyLast synced: 11/20/2025, 11:53:21 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
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).