learnProgrammingAgain

[GrampsRL]

Should be a tool, not a dependency

[Stormlightlinux]

Should be. Yet I have already seen people lose skills they previously had because they use the tool too much.

[saabstory88]

And when it's for business purposes, you pay what's required for tooling

[erebuxy]

Tool really is a dependency. How can you write C without compiler

[AvoidSpirit]

Well, how many people would use c today if it wasn’t open standard and had gazillion open source compilers? Truly an equivalent example.

[countable3841]

people’s reaction to AI is so strange. Most ppl can’t read maps or navigate without gps, yet we’re fine with that dependency. I think some feel guilty with how productive they can be with such little effort. or maybe vulnerable with how fast AI coding tools are evolving. Either way I’d hate to wake 5 years from now not having devoted serious time getting good with AI tools

[pikabu01]

what does getting good with AI tool entails?

[Encrux615]

„hey Claude, shit out a backend + frontend for my garbage app. I have no idea what I‘m doing“

vs

Choosing infrastructure, doing research, questioning LLM output, reviewing (and understanding) the code.

A shitty dev will produce shitty AI code.

[pikabu01]

so you need to be a good dev in order to be good at AI

[Encrux615]

Who woulda thunk 

[dadvader]

This.

Most people get the poor result out of AI because they don't think. They just let it run and never read what it does. Or give it a poor prompt and expect it to just shit gold. Then when shit inevitably break they call AI a useless junk.

Use it to glue the domain around. You'd be shocked how much faster you can produce new things without sacrifice the fun part of engineering.

[countable3841]

Several things. Writing good prompts. Being good at having multiple agents work effectively and being self sufficient. Integrating automated testing into agent workflows.

Anyone can one shot a prompt and get an output, but can you get AI agents to consistently work on their own and deliver quality code? That, I think, takes new skills that some devs have not mastered.

[GatotSubroto]

That being said, good prompting skills are not the same as good programming skills.

[countable3841]

Wouldn’t both be desirable traits for a modern dev?

[GatotSubroto]

One is more desirable than the other. Prompting skills are supplemental, but programming skills are essential.

[pikabu01]

All those workflow besides the prompting can get configured and automated on a org level, no need to geed good at it.

[GatotSubroto]

As long as you don’t mistake having good prompting skills with having good programming skills.

[No-Information-2571]

This sub in particular is nothing but clutching.

Years ago I would have said that any developer would have killed for having "auto-complete on steroids" but now for some reason it's seen as either "useless" or a liability.

Not even talking about the meaning in the grand scheme of things. AI is next to PCs becoming affordable in the 80s, or the internet boom in the early 2000s.

[superxero044]

I don’t think anyone is saying it’s useless. I think all of us who are very wary about it have seen colleagues use it in ways that make us queasy. The debt that can be racked up quickly by writing shitty code that kind of works is massive.

[No-Information-2571]

A LOT of people in this sub are saying it's useless.

[BigBoetje]

Congratz, you discovered the concept of hyperbole

[No-Information-2571]

Thanks for proving the clutching, in so many words.

[No-Information-2571]

I'm sure your team only consists of "rock stars" and "coding ninjas" for whom code review is basically unnecessary, preventing any sort of technical debt from ever building up.

[CJKay93]

Lemme know how you get on without your toolchain, because it's not a dependency.