I don't get the whole "all-in" mentality around LLMs. I'm an iOS dev by trade, I continue to do that as I always have. The difference now is I'll use an LLM to quickly generate a one-off view based on a design. This isn't a core view of an app, the core functionality, or really anything of importance. It's a view that promotes a new feature, or how to install widgets, or random things. This would normally take me 30-…
After months of coding with LLMs, I'm going back to using my brain
21–30 of 229 posts
Re: After months of coding with LLMs, I'm going back to using my brain
#22I don't get the whole "all-in" mentality around LLMs. I'm an iOS dev by trade, I continue to do that as I always have. The difference now is I'll use an LLM to quickly generate a one-off view based on a design. This isn't a core view of an app, the core functionality, or really anything of importance. It's a view that promotes a new feature, or how to install widgets, or random things. This would normally take me 30-…
Re: After months of coding with LLMs, I'm going back to using my brain
#23I don't get the whole "all-in" mentality around LLMs. I'm an iOS dev by trade, I continue to do that as I always have. The difference now is I'll use an LLM to quickly generate a one-off view based on a design. This isn't a core view of an app, the core functionality, or really anything of importance. It's a view that promotes a new feature, or how to install widgets, or random things. This would normally take me 30-…
Re: After months of coding with LLMs, I'm going back to using my brain
#24Re: After months of coding with LLMs, I'm going back to using my brain
#25For me, the magic of LLMs is that I already get an hour of coding via 30 minutes of prompting and finetuning the generated code. And I know that the ratio will constantly improve as LLMs become better and as I finetune my prompts to define the code style I prefer. I have been coding for pretty much all my life and I never felt more excited about it than I do now.
It would be cool if people shared their prompts and the resuling commits. If someone here is disappointed by the commits LLMs make, I would love to see the prompt, the commit, and which model made it.
Re: After months of coding with LLMs, I'm going back to using my brain
#26Re: After months of coding with LLMs, I'm going back to using my brain
#27Because if you just say it should solve some problem for you, it eagerly will generate a lot of code for you, or add a lot of code to the clean code which you provided.
Re: After months of coding with LLMs, I'm going back to using my brain
#28I get it and I see the same problems as the author. I'm working on a few toy projects and I am using LLM for 90% of it. The result is 10x faster than if I coded it "by hand", but the architecture is worse and somewhat alien. I'm still keeping at it, because I'm convinced that LLM driven code is where things are headed, inevitably. These tools are just crazy powerful, but we will have to learn how to use them in a way…
Just like you're mentioning "maybe better prompt engineering", I feel like we're being conditioned to think "I'm just not using it right" where maybe the tool is just not that good yet.
Re: After months of coding with LLMs, I'm going back to using my brain
#29So someone could come along and say "well don't do that then, duh". But actually a lot of people are doing this, and many of them have far fewer fucks to give than the author and I, and I don't want to inherit their shitty slop in the future.
Re: After months of coding with LLMs, I'm going back to using my brain
#30I don't use LLMs for my main pieces of work exactly due to the issues described by the author of the blogpost.