Fascinating read, and it touches upon a problem that seems to exist in every programming organization: you can't say why, but you just kn...
Fascinating read, and it touches upon a problem that seems to exist in every programming organization: you can't say why, but you just know who the best developers are. Sure, that statement is somewhat trivial when experience and ability vary wildly, but when the skill levels begin to converge there is a lot more self-organization among the developers such that they somewhat rank themselves. To me the problem comes when looking for new developers to add to the organization. In the thirst to determine what a "good" developer is we've instead settled on choosing those who seem to have studied the hardest while learning how to program. The fact that this knowledge is rarely directly applied in most tech orgs (how many basic CRUD apps are hurt by poor algorithm choices, after all?), but is still the only thing approaching a reliable barometer of basic competence is a pain point for any programmer hunting for a job. Programming is a creative endeavor in many ways, which means subjectivity is involved in the selection of "best" and "worst". Figuring out how to codify that into an objective ranking is something that, when solved, will take the computing job market by storm. Or then again, that could just be wishful thinking on my part.
Posted by JacobHarrington on Dec 23, 2014, 1:49 AM
Tags
Related issues
- I mean that's the problem though.
- I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
- The biggest problem with AI isn't being able to do things.
- I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
- Of course not, those are clearly scams.
- Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
hackernews (EdTech)
I mean that's the problem though.
I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
The biggest problem with AI isn't being able to do things.
I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
Of course not, those are clearly scams.
Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Effectively everyone is building the same tools with zero quantitative benchmarks or evidence behind the why / ideas … this entire s...
> creating and operating a small company in Germany is a nightmare To be fair, I think the problem operating in Germany is its federated...
Fascinating read, and it touches upon a problem that seems to exist in every programming organization: you can't say why, but you just kn...
Fascinating read, and it touches upon a problem that seems to exist in every programming organization: you can't say why, but you just know who the best developers are. Sure, that statement is somewhat trivial when experience and ability vary wildly, but when the skill levels begin to converge there is a lot more self-organization among the developers such that they somewhat rank themselves. To me the problem comes when looking for new developers to add to the organization. In the thirst to determine what a "good" developer is we've instead settled on choosing those who seem to have studied the hardest while learning how to program. The fact that this knowledge is rarely directly applied in most tech orgs (how many basic CRUD apps are hurt by poor algorithm choices, after all?), but is still the only thing approaching a reliable barometer of basic competence is a pain point for any programmer hunting for a job. Programming is a creative endeavor in many ways, which means subjectivity is involved in the selection of "best" and "worst". Figuring out how to codify that into an objective ranking is something that, when solved, will take the computing job market by storm. Or then again, that could just be wishful thinking on my part.
Comments (0)
No comments yet. Start the discussion.