Live data from Hacker News

I'm OK being left behind, thanks

shkspr.mobi

701–710 of 800 posts

Re: I'm OK being left behind, thanks

#701

Earlier quoted context omitted.

But it's so easy to try something like Claude Code. It's not like you need to get up to speed. There is no learning curve*, that's the nature of AI. Just start using it and you'll see why it has attracted so much hype. *I should qualify that "using" CC in the strict sense has no learning curve, but really getting the most out of it may take some time as you see its limitations. But it's not learning tech in the tradi…

I've been playing with it on weekends for the last few months. 9 out of 10 projects, it's failed. Projects as simple as "set up a tmux/vim binding so I can write prompts in one pane and run claude in the other". Fails. I've been coding for over 20 years. If there is no learning curve, why doesn't it work for me? You can't say I'm not using it right, because if that was true, then all I need to do is climb the learnin…

There definitely is a learning curve. Not sure what you're doing. Are you trying to one-shot it?

I think a decent place to start is: given a small web app, give it a bug report and ask it what causes the bug.

Re: I'm OK being left behind, thanks

#702
post #33

> If this tech is as amazing as you say it is, I'll be able to pick it up and become productive on a timescale of my choosing not yours. Broadly speaking, I think this is a wise assessment. There are opportunities for productivity gains right now, but it I don't think it's a knockout for anyone using the tech, and I think that onboarding might be challenging for some people in the tech's current state. It is safe to…

i thought so too. but now we are onboarding project managers in non-tech fields to Claude Code and they are crushing it. on a terminal. vs code. the first thirty min is the hard part, after that the feedback loop kicks in. they ask for what they really want, they get it.

Re: I'm OK being left behind, thanks

#703
post #678

Earlier quoted context omitted.

Broadly speaking, LLMs are destined to fail. Why? Because all the folks involved have created a technology in search for a problem to solve. That never, ever works. Steve Jobs of all people left this piece of wisdom behind. Its amazing how few actually apply it. The internet was never this - its origins go back to the need to able to transmit data - darpa. And this is what we still do now...

Can you stop using them? https://news.ycombinator.com/item?id=47462767

I dont use them.

Re: I'm OK being left behind, thanks

#704

Earlier quoted context omitted.

> Cloud had a very similar vibe when it was really running advertising to CIO/CTOs hard. Everything had to be jammed into the cloud, even if it made absolutely no sense for it to be run there. 100% accurate - some of us are old enough to have lived through a few of the mini-revolutions in between the mega-revolutions of Internet/Web in the 1990s and now AI/LLM in the 2020s. We are in the "stupid phase" of adoption st…

I think the feel bad moment here is how impersonal everything got in 3 decades. During the dotcom bust you still had to meet and talk to people to get interviews started. Now you can make a perfectly tailored resume, apply to 50 jobs in a day, and it's not unexpected to not get any response from those in 2 weeks. You don't know if it's your resume, the company, or the economy. And no one wants to admit the latter two…

"And no one wants to admit the latter two are problems."

Im working on building something to address this. That's all I'll say lol.

Re: I'm OK being left behind, thanks

#705

I actually think the opposite approach might be the most optimal one, at least from a monetary perspective. That is, be on the cutting-edge of something, but be willing to bail out at the moment its future starts seeming questionable. Or even more specifically, maximize your foothold in it while minimizing your downside. Bitcoin is a good example: if you bought it 15 years ago and held it, you're probably quite wealt…

> be on the cutting-edge of something, but be willing to bail out at the moment its future starts seeming questionable The problem is this leaves you undifferentiated from every hype chaser in Silicon Valley. Our world is littered with folks who went to coding school, traded Bitcoin, did something in the metaverse and blogged about AI. That jack-of-all-trades knowledge can be useful. But only if you’re making unlikel…

> Having the same cutting-edge familiarity as every tech journalist doesn’t that make.

You are giving too much credit to tech journalists. How many of them truly understand Bitcoin or AI?

Re: I'm OK being left behind, thanks

#707

There's value in being early - in the right thing. - If you'd invested in Bitcoin in 2016, you'd have made a 200x return - If you'd specialized in neural networks before the transformer paper, you'd be one of the most sought-after specialists right now - If you'd started making mobile games when the iPhone was released, you could have built the first Candy Crush Of course, you could just as well have - become an Acti…

Wow, shots fired here for me. I was ahead of the game with my intimidate expertise in ActionaScript and Silverlight! I made 3D engines in browsers well before WebGL was a spec. It was quite profitable for a few years, then poof . Dead end lol

Shockwave director studio even!?

I think these ideas are similar to long-term relationships. Identify when it's clear it's worth your time, like the author, and commit appropriately, and then when it's time to move on move on.

AngularJS, Backbone, Knockout, YUI, were all a wave of pretty groundbreaking frontend technology. It was absolutely worth experimenting with and committing to once they had some uptake, but probably not before then unless you wanted to work on the teams building them. Time went on, they had years of longevity that overlapped with the next wave of Vue, React, and the rest, and those became worth investing in long-term. Along the way, fundamentals in underlying web technologies were crucial, programming, logic, networking, markup, design.

Actionscript was totally worth investing in, until it ran it's course, and then other things came along and you would have adapted your game programming and engine programming skills yo a different platform.

Re: I'm OK being left behind, thanks

#708

Earlier quoted context omitted.

Sure, in the same way I can always quit being an engineer and become a farmer. It can work for some, but not everyone. FWIW I do client work on the side. Full time client work has always been more draining than just having a regular job IME. Maybe I just can't find the right clients, but that's not something I have to worry about when I work for a company.

I wasn’t talking to everyone I was talking to you. And becoming a contractor is a lot more viable than becoming a farmer. Client work is hard, but you have to decide if the freedom to work the way you want is worth it.

Oh. Well personally I don't mind using AI, and I use AI when I do client work as well (they know and some clients who use AI apps like lovable expect it).

But I know not everyone is in my shoes which is where my comment is coming from.

Re: I'm OK being left behind, thanks

#709
Why not do fads in moderation? I've always done this.

Don't convert it all to xhtml, just start closing your

Don't go full UML code generation mode, just use it to illustrate core business logic.

Don't buy an iPhone, get an n8.

Don't be a cryptobro, just get one, set it aside.

Don't go full TDD, but use it for bug fixes.

Don't go full knowledge graph/org mode, just have a captain's log.md and an assets/ folder.

Don't go full microservices, create modular monoloths.

Don't go full agent teams, just use normal cli.

etc. etc.

Re: I'm OK being left behind, thanks

#710

Earlier quoted context omitted.

> If people really counted [...] Exactly. I counted and reported my results in a previous thread [0]. [0] https://news.ycombinator.com/item?id=47272913

I've started "racing" Claude when I have a somewhat simple task that I think it should be able to handle. I spend a few minutes writing out detailed instructions, which I already knew because I had to do initial discovery around the problem domain to understand what the goal was supposed to be. It took a while to be thorough enough writing it down for Claude, which is time I did not need to spend if I had just starte…

I've done the racing thing too. Or I just reject its suggestions, do it better, and have it review and tell me why I did better.

And writing those instructions when I race it..it's more cognitive effort for me than coding!

Post reply on HN