Live data from Hacker News

The rise of judgement over technical skill

notsocommonthoughts.com

161–170 of 176 posts

Re: The rise of judgement over technical skill

#161

Earlier quoted context omitted.

> but OTOH "never improve much" seems unrealistic, given the insane progress of the field in the last 3ish years The point is that no one should hire an intern or a junior because they think it will improve their team's productivity. You hire interns and juniors because there's a causal link between "I hired an intern and spent money training them" and "they joined my company full time and a year later are now produc…

Precisely - AI getting better or not has nothing to do with my burning cycles using it. My juniors do improve based on my effort. I can free ride on AI getting good enough later (wait) whereas I cannot with my own team of juniors. > 1 technical founder and a team of contract labor, trying to build that first MVP or cranking out early features in a huge rush Having worked in environments with a large number of junior…

To your last point -- I didn't say large number of junior contractors would write good code or whatever. The change that is happening in the startup scene now, as compared to say 10 years ago, is more about lowering the barrier to MVP and making it easier/cheaper for startups to experiment with finding product market fit, than anything to do with "productivity" or code quality or whatever.

We're probably just talking past each other, because the thing you care about is not the thing I care about. I am saying that, it used to cost some reference benchmark of $X/idea to iterate as a startup and experiment with ideas, but then it became 0.5X because gig workers or overseas contractors became more accessible and easier to work with, and now it's becoming 0.1X because of LLMs and coding agents. I am not making any sort of argument about quality being better/good/equal, nor am I making any sort of conversion chart between 10 interns or 100 LLM agents equals 1 senior engineer or something... Quality is rarely (never?) the deciding factor, when it comes to early pre-seed iteration as a startup tries to gasp and claw for something resembling traction. Cost to iterate as well as benefits of having more iterations, can be improving, even if each iteration's quality level is declining.

I'm simply saying, if I was a founder, and I had $10k to spend to test new ideas with, I can test a helluva lot more ideas today (leveraging AI), vs what I could have done 5 years ago (using contractors), vs what I could have done 10-20 years ago (hiring FTEs, just to test out ideas, is frankly kind of absurd when you think about how expensive that is). I am not saying that $10k worth of Claude Code is going to buy me a production grade super fantastic amazing robust scalable elegant architecture or whatever, but it sure as heck can buy me a good enough working prototype and help me secure a seed round. Reducing that cost of experimentation is the real revolution (and whether interns can learn or will pay off over time is a wholly orthogonal topic that has no bearing to this cost of experimentation revolution).

Re: The rise of judgement over technical skill

#162
post #13

Human judgement is like a house built on sand, it is basically provably feeble [0]. I've literally never in practice seen a human update their beliefs using Bayes' formula. I suspect we'll find that at some point fairly soon AIs will just have better judgement than us because they can be programmed to incorporate formal statistical concepts while humans have to rely on evolving grey goop which we haven't quite master…

If there is one thing AI is currently shockingly bad at, it's updating its assumptions when it is confronted with evidence that they are incorrect. It will tirelessly spin its wheels (seemingly) forever laboring under a false assumption, running into dead end after dead end without ever coming to the conclusion that it should reexamine its assumptions.

Re: The rise of judgement over technical skill

#163

Earlier quoted context omitted.

I like to do a good job on small stuff. It works nicely for me, but doesn't really bring accolades (but a hell of a lot of folks actually rely on stuff I authored; they just don't know it, or care -which is just fine).

We cannot build great things on poor foundations If your small stuff contributes to a strong foundation for other people, then they should care It's a shame people lose sight of the ground beneath their feet when reaching to the sky I'm very guilty of this too, partly because any time I try to look down the people I work with rush in to discourage me from doing that - it's not part of the sprint, after all Anyways, I…

We have built _a lot_ of things on top of shaky foundations. It is one of the tragedies of human society, that we are too resistant to rebuilding parts and accept the status quo too easily. There are network effects at play and probably other effects as well. Basing our work on solid foundations, we shouldn't need to look towards the ground, when reaching up.

Re: The rise of judgement over technical skill

#164

Earlier quoted context omitted.

We cannot build great things on poor foundations If your small stuff contributes to a strong foundation for other people, then they should care It's a shame people lose sight of the ground beneath their feet when reaching to the sky I'm very guilty of this too, partly because any time I try to look down the people I work with rush in to discourage me from doing that - it's not part of the sprint, after all Anyways, I…

We have built _a lot_ of things on top of shaky foundations. It is one of the tragedies of human society, that we are too resistant to rebuilding parts and accept the status quo too easily. There are network effects at play and probably other effects as well. Basing our work on solid foundations, we shouldn't need to look towards the ground, when reaching up.

I remember reading a rather silly fantasy book, back in the '90s.

It was obviously written by a UNIX guy, and it featured a software geek that gets transported into a realm where magic works.

He then started to build a foundation of spells, even giving them UNIX names like "Grep," and "Sed."

It was all about how he built a powerful magic system, from scratch, starting with basic components, and combing them, into more ambitious components, and so on.

Most of my published work is components; usually, Swift Package Manager packages. Each one is carefully written and documented, then tested like crazy. It means that I can leverage them, without a second thought, as to Quality, or features.

Here's what I'm working on, now[0]. It still has a long way to go, but it's coming along nicely. It's a "swipeable" tab bar controller, so that iOS apps can behave like Android apps. I have been doing this by hand, in many of my latest apps, and I thought that it was a good candidate for commoditization.

I'll spend a lot of time, testing and documenting it, so it will be a "drop in" module that I'll be able to use for future apps.

[0] https://github.com/LittleGreenViper/SwipeTabController

Re: The rise of judgement over technical skill

#165

Earlier quoted context omitted.

Precisely - AI getting better or not has nothing to do with my burning cycles using it. My juniors do improve based on my effort. I can free ride on AI getting good enough later (wait) whereas I cannot with my own team of juniors. > 1 technical founder and a team of contract labor, trying to build that first MVP or cranking out early features in a huge rush Having worked in environments with a large number of junior…

To your last point -- I didn't say large number of junior contractors would write good code or whatever. The change that is happening in the startup scene now, as compared to say 10 years ago, is more about lowering the barrier to MVP and making it easier/cheaper for startups to experiment with finding product market fit, than anything to do with "productivity" or code quality or whatever. We're probably just talking…

Yeah in this context I get what you are talking about. I got through your first paragraph and thought of the startup founders using overseas / gig workers a decade ago to test ideas.. which is exactly where you went!

Re: The rise of judgement over technical skill

#166
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…

This would be at least the third time in history we've tried to shunt writing code to low paid labor. We'll see if it's successful this time. The problem tends to be that small details affect large details which affect small details. If you aren't good at both you're usually shit at both.

Someone told me AI was like having a bunch of junior coders. You have to be very explicit in telling it what to do and have to go through several iterations to get it right. Though it was cheaper.

Re: The rise of judgement over technical skill

#167
post #107

A side note to the general point of the article, but I hate how the tech industry uses the word "democratization" to mean "lowering the barrier to entry". These concepts differ from each other but many use the former term because in doing so they justify their actions as driven by some sort of moral imperative when in reality, the development of LLMs is morally neutral, not inherently bad by any stretch, but as much…

I agree with you however I've also not found a better substitute. Any candidates?

Re: The rise of judgement over technical skill

#168

Earlier quoted context omitted.

I like to do a good job on small stuff. It works nicely for me, but doesn't really bring accolades (but a hell of a lot of folks actually rely on stuff I authored; they just don't know it, or care -which is just fine).

We cannot build great things on poor foundations If your small stuff contributes to a strong foundation for other people, then they should care It's a shame people lose sight of the ground beneath their feet when reaching to the sky I'm very guilty of this too, partly because any time I try to look down the people I work with rush in to discourage me from doing that - it's not part of the sprint, after all Anyways, I…

> It's a shame people lose sight of the ground beneath their feet when reaching to the sky

Shakespeare:

> 'tis a common proof \ That lowliness is young ambition's ladder, \ Whereto the climber-upward turns his face; \ But when he once attains the upmost round, \ He then unto the ladder turns his back, \ Looks in the clouds, scorning the base degrees \ By which he did ascend.

(Brutus, of Caesar, Julius Caesar)

Re: The rise of judgement over technical skill

#169

Earlier quoted context omitted.

We cannot build great things on poor foundations If your small stuff contributes to a strong foundation for other people, then they should care It's a shame people lose sight of the ground beneath their feet when reaching to the sky I'm very guilty of this too, partly because any time I try to look down the people I work with rush in to discourage me from doing that - it's not part of the sprint, after all Anyways, I…

We have built _a lot_ of things on top of shaky foundations. It is one of the tragedies of human society, that we are too resistant to rebuilding parts and accept the status quo too easily. There are network effects at play and probably other effects as well. Basing our work on solid foundations, we shouldn't need to look towards the ground, when reaching up.

> We have built _a lot_ of things on top of shaky foundations.

[Technical] debt is a choice, and the gene that makes "perfect" the enemy of "good" misses opportunities for inheritance!

As a dev--as an adult!--I still need to learn to relax and embrace shaky foundations--and technical debt!

Re: The rise of judgement over technical skill

#170
post #169

Earlier quoted context omitted.

We have built _a lot_ of things on top of shaky foundations. It is one of the tragedies of human society, that we are too resistant to rebuilding parts and accept the status quo too easily. There are network effects at play and probably other effects as well. Basing our work on solid foundations, we shouldn't need to look towards the ground, when reaching up.

> We have built _a lot_ of things on top of shaky foundations. [Technical] debt is a choice , and the gene that makes "perfect" the enemy of "good" misses opportunities for inheritance! As a dev--as an adult!--I still need to learn to relax and embrace shaky foundations--and technical debt!

One of the things that we learn, as we mature, is that "It Depends" is a mantra for life.

A good filter is the "How Important is It?" filter.

If I'm adding dependencies to an app, a styling dependency is less crucial than an algorithm one. I may just apply some fairly basic checks to a styling dependency, and maybe use injection, to make it easy to swap out. I may also look for free, or low-cost ones.

For the algorithm, which may be my bread and butter, I might be a hell of a lot more demanding, and I may consider using a commercially-backed product.

I sort of touch on that, in this posting: https://littlegreenviper.com/concrete-galoshes/

Post reply on HN