Earlier quoted context omitted.
I'm actually very curious why AI use is such a bi-modal experience. I've used AI to move multi thousand line codebases between languages. I've created new apps from scratch with it. My theory is the willingness to baby sit and the modality. I'm perfectly fine telling the tool I use its errors and working side by side with it like it was another person. At the end of the day it can belt out lines of code faster than I…
I'm curious coming from the other end. I guess I can totally understand certain use cases where I'm generating fairly simple, self contained code in a language I'm unfamiliar with being good. But surely you must have experienced something where you're literally fighting with the model, where it continuously repeats its mistakes, and fixing a mistake in one place, breaks something else, and you can't seem to escape th…
GitHub cuts AI deals with Google, Anthropic
551–560 of 742 posts
Re: GitHub cuts AI deals with Google, Anthropic
#552Earlier quoted context omitted.
> But the idea of letting an LLM write/move large swaths of code seems so incredibly irresponsible. I think this is where the bimodality comes from. When someone says "I used AI to refactor 3000 loc" some take it to mean they used AI in small steps as an accellerator, and others take it to mean a direct copy/paste, fix compile errors and move on. Treat AI like a mid level engineer that you are pair programming with,…
It’s really far from mid level. It’s a weird mix of expert at things it trained on, and complete misleading idiot at anything outside. For a bash script or the first steps of something simple it’s great. For anything complex at all it’s worse than nothing.
Re: GitHub cuts AI deals with Google, Anthropic
#553Earlier quoted context omitted.
As a programmer of over 20 years - this is terrifying. I'm willing to accept that I just have "get off my lawn" syndrome or something. But the idea of letting an LLM write/move large swaths of code seems so incredibly irresponsible. Whenever I sit down to write some code, be it a large implementation or a small function, I think about what other people (or future versions of myself) will struggle with when interactin…
I'll take a stab at changing your mind. AIs are not able to write Redis. That's not their job. AIs should not write complex high performance code that millions of users rely on. If the code does something valuable for a large number of people you can afford humans to write it. AIs should write low value code that just repeats what's been done before but with some variations. Generic parts of CRUD apps, some fraction…
I think the question to ask is what do I do as a software engineer that couldn't be done by an AI based tool in a few years time? The answer is scary, but exciting.
Re: GitHub cuts AI deals with Google, Anthropic
#554Earlier quoted context omitted.
It's the subtle errors that are really difficult to navigate. I got burned for about 40 hours on a conditional being backward in the middle of an otherwise flawless method. The apparent speed up is mostly a deception. It definitely helps with rough outlines and approaches. But, the faster you go, the less you will notice the fine details, and the more assumptions you will accumulate before realizing the fundamental e…
I would love to find out where programmers are learning this idea: that writing code fast is ideal. If it takes 30 years to write one loc, it takes 30 years. Ideally, it takes 30 years to write zero lines of code.
>that writing code fast is ideal.
At places that pay them.
Re: GitHub cuts AI deals with Google, Anthropic
#555Call me eccentric but the only true or utilitarian use case I've found for AI so far is chatgpt. Rest all appear to be shiny toys just trying to bask in the AI glory but none solve any real human problem?
Re: GitHub cuts AI deals with Google, Anthropic
#556Earlier quoted context omitted.
I agree with you and its confusing to me. I do think there is a lot of emotion at play here - rather than cold rationality. Using LLM based tools effectively requires a change in workflow that a lot of people aren't ready to try. Everyone can share their anecdote of how an LLM has produced stupid or buggy code, but there is way too much focus on what we are now, rather than the direction of travel. I think existing m…
> Using LLM based tools effectively requires a change in workflow that a lot of people aren't ready to try This is a REALLY good summary of it I think. If you lose your patience with people, you'll lose your patience with AI tooling, because AI interaction is fundamentally so similar to interacting with other people
Re: GitHub cuts AI deals with Google, Anthropic
#557For all those believers in the power of AI who tested it in modifying their front-ends and writing a Python script, I have a test: ask AI to write an operating system kernel or a database. Of course, something simple. I never seen AI being used in writing system software. Perhaps there is a reason behind it?
Personally I have been making Velocity Proxy plugins for Minecraft where ChatGPT generates the bulk of the plugin and I fix all the incorrect imports, this is Java. My latest project was a whitelist plugin that uses Discord roles to allow/deny players to join.
Re: GitHub cuts AI deals with Google, Anthropic
#558I usually feel like i can confidently express a change I want in code faster and better than I can explain what I want an AI to do in English. Like if I have a good prompt, these tools work okay, but getting that prompt almost as hard as just writing the code itself often. Do others feel the same struggle?
LLMs have other problems though. The biggest problem for me is that it feels like I lose control of the codebase. I don't have the same mental mapping of the code.
Re: GitHub cuts AI deals with Google, Anthropic
#559Earlier quoted context omitted.
It's the subtle errors that are really difficult to navigate. I got burned for about 40 hours on a conditional being backward in the middle of an otherwise flawless method. The apparent speed up is mostly a deception. It definitely helps with rough outlines and approaches. But, the faster you go, the less you will notice the fine details, and the more assumptions you will accumulate before realizing the fundamental e…
Why aren't you writing unit tests just because AI wrote the function? Unit tests should be written regardless of the skill of the developer. Ironically, unit tests are also one area where AI really does help move faster. High level design, rough outlines and approaches, is the worst place to use AI. The other place AI is pretty good is surfacing api call or function calls you might not know about if you're new to the…
I'd rather see the need for integration tests and end to end tests. I want to test business logic not assert that 2 + 2 = 4.
Re: GitHub cuts AI deals with Google, Anthropic
#560Earlier quoted context omitted.
I have completely the opposite perspective. Unit tests actually need to be correct, down to individual characters. Same goes with API calls. The API needs to actually exist. Contrast that with "high level design, rough outlines". Those can be quite vague and hand-wavy. That's where these fuzzy LLMs shine. That said, these LLM-based systems are great at writing "change detection" unit tests that offer ~zero value (or…
The fact that you think "change detection" tests offer zero value speaks volumes. Those may well be the most important use of unit tests. Getting the function correct in the first place isn't that hard for a senior developer, which is often why it's tempting to skip unit tests. But then you go refactor something and oops you broke it without realizing it, some boring obvious edge case, or the like. These tests are al…
But code should change. What shouldn't change, if business rules don't change, is APIs and contracts. And for that we have integration tests and end to end tests.