Live data from Hacker News

The rise of judgement over technical skill

notsocommonthoughts.com

61–70 of 176 posts

Re: The rise of judgement over technical skill

#61
post #49

A similar debate has happened in education where people seem to think that having ability to critically analyse texts is more important than knowledge. and to some degree that’s true but personally I think that without building on some decent level of foundational level of knowledge and having a mental model of a subject, you can’t tackle thorny questions because you don’t have enough to draw upon as examples and cou…

Education itself is supposed to teach us learning, not the mere facts/methods, not just the hard knowledge. Hard knowledge comes with it anyway as some sort of 'side product'. You cant learn on nothing, something will be used for it, that something forms the hard knowledge eventually. Typically broad set but shallow hard knowledge. Ironicly, this is what I feel chipping away in modern collaborative developments. The…

> You cant learn on nothing, something will be used for it, that something forms the hard knowledge eventually. Typically broad set but shallow hard knowledge.

As a counterpoint though, the way things have gone in the U.K. is to go deep on niche topics without building up appreciation of the broad strokes. To give an example, there’s a GCSE History course for 14-16 year olds where the syllabus is effectively “medicine through time” and “the American West” without ever going near the British Empire, colonialism, the Tudor or Elizabethan periods, the reformation, the Industrial Revolution, Irish home rule and independence, etc. etc. any one of which gives much more insight into the formation of the state and cultural affairs as it stands today.

To my mind it’s too narrow a focus at too young an age when teaching a subject that a lot of children take. It also means there are constantly “we don’t even teach that at school” debates.

Re: The rise of judgement over technical skill

#62
post #6

This echoes my experience with Claude Code. The bottleneck isn't the code generation itself—it's two critical judgment tasks: 1. Problem decomposition: Taking a vague idea and breaking it down into well-defined, context-bounded issues that I can effectively communicate to the AI 2. Code review: Carefully evaluating the generated code to ensure it meets quality standards and integrates properly Both of these require d…

So really the same two skills that a senior engineer needs to delegate tasks to juniors & review the results..

Re: The rise of judgement over technical skill

#65
post #60
post #6

This echoes my experience with Claude Code. The bottleneck isn't the code generation itself—it's two critical judgment tasks: 1. Problem decomposition: Taking a vague idea and breaking it down into well-defined, context-bounded issues that I can effectively communicate to the AI 2. Code review: Carefully evaluating the generated code to ensure it meets quality standards and integrates properly Both of these require d…

What the heck, the code generation _is_ absolutely still a bottle-neck. I dare anyone who making these arguments that LLMs have removed the need for actual programming skill, for example, to share in a virtual pair programming session with me, and I will demonstrate their basic inability to do _any_ moderately complex coding in short order. Yes, I think that's the only way to resolve this controversy. If they have so…

Indeed.

All this “productivity” has not resulted in one meaningful open source PR or one interesting indie app launch, and I can’t square my own experience with the hype machine.

If it’s not all hat and no cattle, someone should be able to show me some cows.

Re: The rise of judgement over technical skill

#66
post #60
post #6

This echoes my experience with Claude Code. The bottleneck isn't the code generation itself—it's two critical judgment tasks: 1. Problem decomposition: Taking a vague idea and breaking it down into well-defined, context-bounded issues that I can effectively communicate to the AI 2. Code review: Carefully evaluating the generated code to ensure it meets quality standards and integrates properly Both of these require d…

What the heck, the code generation _is_ absolutely still a bottle-neck. I dare anyone who making these arguments that LLMs have removed the need for actual programming skill, for example, to share in a virtual pair programming session with me, and I will demonstrate their basic inability to do _any_ moderately complex coding in short order. Yes, I think that's the only way to resolve this controversy. If they have so…

I don’t think AI marks the end of software engineers, but it absolutely can grind out code for well specified, well scoped problem statements in quarter-minutes that would take a human an hour or so.

To me, this makes my exploration workflow vastly different. Instead of stopping at the first thing that isn’t obviously broken, I can now explore nearby “what if it was slightly different in this way?”

I think that gets to a better outcome faster in perhaps 10-25% of software engineering work. That’s huge and today is the least capable these AI assistants will ever be.

Even just the human/social/mind-meld aspects will be meaningful. If it can make a dev team of 7 capable of making the thing that used to take a dev team of 8, that's around 15% less human coordination needed overall to get the product out. (This might even turn out to be half the benefit of productivity enhancing tools.)

Re: The rise of judgement over technical skill

#67

This blog post shows how not to use AI. The author would have been unlikely to write such a uselessly redundant conclusion if they had to type it themselves. Edit: I like the post, but it didn't need to be padded with fluff.

Where do you think LLMs learn to write “uselessly redundant conclusion”?

Re: The rise of judgement over technical skill

#68
Writing musical notation doesn't strike me as technically difficult but I'm unaware of any musical composers who weren't proficient in at least one instrument.

Good judgement is only accessible to those who've invested considerable time in the rudiments.

Re: The rise of judgement over technical skill

#69
post #6

This echoes my experience with Claude Code. The bottleneck isn't the code generation itself—it's two critical judgment tasks: 1. Problem decomposition: Taking a vague idea and breaking it down into well-defined, context-bounded issues that I can effectively communicate to the AI 2. Code review: Carefully evaluating the generated code to ensure it meets quality standards and integrates properly Both of these require d…

So really the same two skills that a senior engineer needs to delegate tasks to juniors & review the results..

Nope, dealing with juniors is way less frustrating because they learn. So overtime, you can increase the complexity of their tasks until they're no longer junior.

Re: The rise of judgement over technical skill

#70

Earlier quoted context omitted.

So really the same two skills that a senior engineer needs to delegate tasks to juniors & review the results..

Nope, dealing with juniors is way less frustrating because they learn. So overtime, you can increase the complexity of their tasks until they're no longer junior.

Agreed on that point, and my question for a lot of the AI bros has been "what would you actually do with unlimited interns who never improve much?"

For me, not much! Others may differ.

In my own experience interns are a net drag. New college hires flip positive after 3-6 months.. if they are really good. Many takes upwards of a year.

Post reply on HN