Live data from Hacker News

A few random notes from Claude coding quite a bit last few weeks

twitter.com

821–830 of 870 posts

Re: A few random notes from Claude coding quite a bit last few weeks

#821

Earlier quoted context omitted.

Lots of very scared, angry developers in these comment sections recently...

I see way more hype that is boosted by the moderators. The scared ones are the nepo babies who founded a vaporware AI company that will be bought by daddy or friends through a VC. They have to maintain the hype until a somewhat credible exit appears and therefore lash out with boomer memes, FOMO, and the usual insane talking points like "there are builders and coders".

society doesn't take kindly to the hyper-aware. tone it down.

Re: A few random notes from Claude coding quite a bit last few weeks

#822

Earlier quoted context omitted.

Learning human languages is not a similar process to learning programming languages at all. I've never been sure why so many people think it is.

I provided it as a counter example to the learning how to bike myth. Learning how to bike requires only a handful of skills, most of them are located in the motor control centers in your brain (mostly in the Cerebellum), which is known to retain skills much better then any other parts of your brain. Your programing skills are comprised of thousands of separate skills which are mostly located in your frontal-cortex (m…

Maybe something that keeps programming skills fresh is that after you learn to think like a programmer, you do that with problems away from the keyboard. Decomposition, logic... in the years I wasn't programming, I was still solving problems like a programmer. Getting back behind the keyboard just engaged the thought processes I was already keeping warm with practice.

Re: A few random notes from Claude coding quite a bit last few weeks

#823
The way I have managed junior engineers is 90% via PR and testing, 10% via reading code in an editor or IDE.

It’s hard to let go of being the keyboard jockey, but in so many cases it is better to describe plans and acceptance criteria and just review the diffs.

Re: A few random notes from Claude coding quite a bit last few weeks

#825

Earlier quoted context omitted.

Socrates was right about the effects. Writing did indeed cause us to loose the talent of memorizing. Where he was wrong though (or rather where this quote without context is wrong) is that it turned out that memorizing was by the most part not the important skill to have. When Socrates uses the same warnings about LLMs he may however be correct both on the effect and the importance of the skill being lost. If we loos…

You're misinterpreting the quote. Socrates is saying that being able to find a written quotation will replace fully understanding a concept. It's the difference between being able to quote the pythagorean theorem and understanding it well enough to prove it. That's why Socrates says that those who rely on reading will be "hard to get along with" - they will be pedantic without being able to discuss concepts freely.

Huh, I think you're right. I think I failed the litmus test. Thanks for explaining!

Re: A few random notes from Claude coding quite a bit last few weeks

#826

Earlier quoted context omitted.

Agreed. I don’t care for engineering or coding, and would gladly give it up the moment I can. I’m also running a one man business where every hour counts (and where I’m responsible for maintaining every feature). The fact of the matter is LLMs produce lower quality at higher volumes in more time than it would take to write it myself, and I’m a very mediocre engineer. I find this seperation of “coding” vs “building” s…

Would you accept 'people who like to make art, and people who like to commission somebody to make art and give them lots of notes in the process'?

I mean it’s closer, but I don’t think it’s right to equate commissioning an artist with paying a multi-billion dollar corporation to steal from artists.

These tools are just lazy shortcuts. And that’s fine, there’s no problem with taking the lazy way. I’m never going to put in the time to learn to draw, so it’s cool there’s an option for me.

I just take ire with pretending it’s something grand and refined, or spitting in the face of the ones who are willing to put in the work

Re: A few random notes from Claude coding quite a bit last few weeks

#827
post #754

Earlier quoted context omitted.

It takes about 30 seconds of thinking and/or searching the Internet to realize that people also predict doom when it actually happens - e.g. with people correctly predicting that TikTok will shorten people's attention spans. It's then quite obvious that the fact that someone, somewhere, predicts a bad thing happening has ~zero bearing on whether it actually happens, and so the claim that "someone predicted doom in th…

There is always some set of people predicting all sorts of dooms though. The saying about the broken clock comes to mind. With the right cherry picking, it can always be said that [some set of] the doomsayers were right, or that they were wrong. As you say, someone predicting doom has no bearing on whether it happens, so why engage in it? It's just spreading FUD and dwelling on doom. There's no expected value to the…

Did you actually read what you're responding to?

> And "other people in the past predicted doom about something like this and it didn't happen" is a fallacious non-argument even when the things are comparable.

> the claim that "someone predicted doom in the past and it didn't happen then so someone predicting doom now is also wrong" is absurd

It's pretty clear that I'm not defending engaging in baseless negative speculation, but refuting the dismissal of negative speculation based purely on the trope that "people have always predicted it".

Someone who read what they were responding to would rather easily have seen that.

> As you say, someone predicting doom has no bearing on whether it happens

That is not what I said. I'm pretty sure now that you did not read my comment before responding. That's bad.

This is what I said:

> It's then quite obvious that the fact that someone, somewhere, predicts a bad thing happening has ~zero bearing on whether it actually happens, and so the claim that "someone predicted doom in the past and it didn't happen then so someone predicting doom now is also wrong" is absurd.

I'm very clearly pointing out (with "someone, somewhere") that a random person predicting a bad thing has almost no ("~zero") impact on the future. Obviously, if someone who has the ability to affect the future (e.g. a big company executive, or a state leader (past or present)) makes a prediction, they have much more power to actually affect the future.

> so why engage in it? It's just spreading FUD and dwelling on doom.

Because (rational) discussion now has the capacity to drive change.

> There's no expected value to the individual or to others.

Trivially false - else most social movements would be utterly irrelevant, because they work through the same mechanism - talking about things that should be changed as a way of driving that change.

It's also pretty obvious that there's a huge difference between "predicting doom with nothing behind it" and "describing actual bad things that are happening that have a lot of evidence behind them" - which is what is actually happening here, so all of your arguments about the former point would be irrelevant (if they were valid, which they aren't) because that's not even the topic of discussion.

I suggest reading what you're responding to before responding.

> Personally, I don't think "TikTok will shorten people's attention spans" qualifies as doom in and of itself.

You're bringing up "doom" as a way to pedantically quarrel about word definitions. It's trivial to see that that's completely irrelevant to my argument - and worth noting that you're then conceding the point about people correctly predicting that TikTok will shorten people's attention spans, hence validating the need to have discussions about it.

Re: A few random notes from Claude coding quite a bit last few weeks

#828

Earlier quoted context omitted.

That is interesting because your mental abilities seem to be correlated with orchestrating a bunch of abstractions you have previously mastered. Are these tools making us stupid because we no longer need to master any of these things? Or are they making us smarter because the abstraction is just trusting AI to handle it for us?

Does a student become smarter by hiring a smarter student to write his essays and take his tests for him?

We can also invert that by asking: does a student become smarter by writing their essay on their own?

I would argue that the answer to questions is no. It depends on how you define “smarter”, though. You would likely gain knowledge writing the essay yourself, but is gaining knowledge equivalent to getting smarter?

If so, you could also just read the essay afterwards and gain the same knowledge. Is _that_ smarter? You’ve now reached the same benefit for much less work.

I think fundamentally I at least partially agree with your stance. That we should think carefully before taking a seemingly easier path. Weighing what we gain and lose. Sometimes the juice is, in fact, the squeeze. But it’s far from cut and dry.

Re: A few random notes from Claude coding quite a bit last few weeks

#829
post #570

Earlier quoted context omitted.

> An LLM is always going to be a black box that is neither predictable nor visible (the unpredictability is necessary for how the tool functions; the invisibility is not but seems too late to fix now) So basically, like a co-worker. That's why I keep insisting that anthropomorphising LLMs is to be embraced, not avoided, because it gives much better high-level, first-order intuition as to where they belong in a larger…

Sort of except it seems the more the co-worker does the job it atrophies my ability to understand.. So soon we'll all be that annoyingly ignorant manager saying, "I don't know, I want the button to be bigger". Yay?

Only if we're lucky and the LLMs cease being replaced with improved models.

Claude has already shown us people who openly say "I don't code and yet I managed this"; right now the command line UI will scare off a lot of people, and people using the LLMs still benefit from technical knowledge and product design skills, if the tools don't improve we keep that advantage…

…but how long will it be before the annoyingly ignorant customer skips the expensive annoyingly ignorant manager along with all us expensive developers, and has one of the models write them bespoke solution for less than the cost of off-the-shelf shrink-wrapped DVDs from a discount store?

Hopefully that extra stuff is further away than it seems, hopefully in a decade there will be an LLM version of this list: https://en.wikipedia.org/wiki/List_of_predictions_for_autono...

But I don't trust to hope. It has forsaken these lands.

Re: A few random notes from Claude coding quite a bit last few weeks

#830
post #829
post #570

Earlier quoted context omitted.

Sort of except it seems the more the co-worker does the job it atrophies my ability to understand.. So soon we'll all be that annoyingly ignorant manager saying, "I don't know, I want the button to be bigger". Yay?

Only if we're lucky and the LLMs cease being replaced with improved models. Claude has already shown us people who openly say "I don't code and yet I managed this"; right now the command line UI will scare off a lot of people, and people using the LLMs still benefit from technical knowledge and product design skills, if the tools don't improve we keep that advantage… …but how long will it be before the annoyingly ign…

> using the LLMs still benefit from technical knowledge and product design skills, if the tools don't improve we keep that advantage…

I don't think we will, because many of us are already asking LLMs for help/advice on these, so we're already close to the point where LLMs will be able to use these capabilities directly, instead of just for helping us drive the process.

Post reply on HN