Where you find coding answers is a function of expertise.
When you first start learning, Stack Overflow will have your exact question and a perfect answer.
Then you’ll find that people have only asked similar questions, so you have to piece together a solution from multiple partial answers.
As you level up, you’ll find less on Stack Overflow, and you start to have to read API documentation and specifications.
When that fails, you read code. Declarations, then implementations. And if you’re hard pressed, decompiled binaries.
It’s not a straight line of course, and you’ll often be at different levels for different projects—or even different parts of the same project.
The important thing to remember is that as a programmer, you’ll never know what you’re doing. Once you’ve solved some programming problem, you never have to solve the same problem again because the code already exists.
The difference between an expert and a novice isn’t that the expert knows what they’re doing. It’s that the expert doesn’t know what they’re doing at a higher level.
jimbocoin / jimbocoin 🃏
npub1v9…x9q3h
2024-08-20 09:32:43
in reply to nevent1q…psaf
Author Public Key
npub1v9qy0ry6uyh36z65pe790qrxfye84ydsgzc877armmwr2l9tpkjsdx9q3hPublished at
2024-08-20 09:32:43Event JSON
{
"id": "79a0f5218b43af1e4abe3d686199dff0a427c5d12708a7395f7e54a2c949691a",
"pubkey": "6140478c9ae12f1d0b540e7c57806649327a91b040b07f7ba3dedc357cab0da5",
"created_at": 1724146363,
"kind": 1,
"tags": [
[
"e",
"7af72778450d9f5abc3ff526cbbd95ab220da6732bd61e358bf6e75d80da2bec",
"",
"root"
],
[
"p",
"61066504617ee79387021e18c89fb79d1ddbc3e7bff19cf2298f40466f8715e9"
]
],
"content": "Where you find coding answers is a function of expertise.\n\nWhen you first start learning, Stack Overflow will have your exact question and a perfect answer.\n\nThen you’ll find that people have only asked similar questions, so you have to piece together a solution from multiple partial answers.\n\nAs you level up, you’ll find less on Stack Overflow, and you start to have to read API documentation and specifications.\n\nWhen that fails, you read code. Declarations, then implementations. And if you’re hard pressed, decompiled binaries.\n\nIt’s not a straight line of course, and you’ll often be at different levels for different projects—or even different parts of the same project.\n\nThe important thing to remember is that as a programmer, you’ll never know what you’re doing. Once you’ve solved some programming problem, you never have to solve the same problem again because the code already exists.\n\nThe difference between an expert and a novice isn’t that the expert knows what they’re doing. It’s that the expert doesn’t know what they’re doing at a higher level.",
"sig": "c5c0189217ce854e9a93834d048c33600a1833417ddaacdcdb2f90e93fe1260c474e3da5834001f956c73b415433184e104be147178194b64d9c1a10c4b651d9"
}