mirsadm

I do this all the time but then you end up with really over engineered code that has way more issues than before. Then you're back to prompting to fix a bunch of issues. If you didn't write the initial code sometimes it's difficult to know the best way to refactor it. The answer people will say is to prompt it to give you ideas. Well then you're back to it generating more and more code and every time it does a refactor it introduces more issues. These issues aren't obvious though. They're really hard to spot.

I have already been doing this. I could keep doing it but I'm not going to. I want to be able to understand my own code because that is what let's me make sound higher level decisions.

My own observation is that the initial boost to productivity results in massive crippling technical debt.

I have an app which is fairly popular. This release cycle I used Claude Code and codex to implement all the changes / features. It definitely let me move much quicker than before.

However now that it's in the beta stage the amount of issues and bugs is insane. I reviewed a lot of the code that went in as well. I suspect the bug fixing stage is going to take longer than the initial implementation. There are so many issues and my mental model of the codebase has severely degraded.

It was an interesting experiment but I don't think I would do it again this way.

Even then there is no transparency on how it decides what runs on the ANE/GPU etc

Isn't the whole point for it to learn what features to extract?

This use to be the most embarrassing thing that could happen. A team member asks you why you did something a certain way during a PR and you can't provide an answer. This seems to be becoming the norm now.

This is yet to be seen. Certainly feels like I'm more productive but I'm not seeing any faster results. It would be nice for this to be studied more.

I know Anthropic is burning cash but I'm pretty sure they can afford to pay the developer fees for those platforms.

This seems like a bot comment.

I like to think I have some experience in this area. I have an app on Android that records RAW video (MotionCam Pro). We've compared large expensive cameras to phone sensors many times (you can see it on our YouTube channel if you like).

Not true. Phone sensors are amazing even without any processing. The difference is not as large as you might think.

What I've found out is that a lot of people don't actually care. They see it work and that's that. It's impossible to convince them otherwise. The code can be absolutely awful but it doesn't matter because it works today.

My issue with any of these claims is the lack of proof. Just share the chat and now it got to the discovery. I'll believe it when I can see it for myself at this point. It's too easy to make all sorts of claims without proof these days. Elon Musk makes them all the time.

But what if you want both on a shared memory system?

Vulkan is awful to work with and the drivers are buggy. Google's own phones are the worst for it. I have an app with a compute only vulkan pipeline and on the Google Pixel 10 the whole screen becomes corrupted with some fairly basic shaders.

Sure they can also code without the help of a model, probably not that much slower.

Yes but did you learn anything?

I can't tell if this is a serious conversation anymore.

I use Claude Code a lot but one thing that really made me concerned was when I asked it about some ideas I have had which I am very familiar with. It's response was to constantly steer me away from what I wanted to do towards something else which was fine but a mediocre way to do things. It made me question how many times I've let it go off and do stuff without checking it thoroughly.

Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently? It is an unorganised mess with multiple different case styling all over the place. I get this is not that important but I can't help feel it illustrates just how little care is taken behind the scenes. The whole thing seems like a nightmare to deal with.

I had a fresh install of Windows on a new computer which refused to install updates until I ran a bunch of commands in the "terminal". The whole thing is beyond fixing at this point.

I've used Claude Code to do the same (large refactor). It has worked fairly well but it tends to introduce really subtle changes in behaviour (almost always negative) which are very difficult to identify. Even worse if you use it to fix those issues it can get stuck in a loop of constantly reintroducing issues which are slightly different leading to fixing things over and over again.

Overall I like using it still but I can also see my mental model of the codebase has significantly degraded which means I am no longer as effective in stopping it from doing silly things. That in itself is a serious problem I think.

I think there is a big difference. You could and should have both knowledge. This applies to whether you're a lowly programmer or a CEO. Knowing the details will always help you make better decisions.

There's never been a case in my long programming career so far where knowing the low level details has not benefited me. The level of value varies but it is always positive.

When you use LLMs to write all your code you will lose (or never learn) the details. Your decision making will not be as good.

I would disagree on the huge boost to productivity but it is a very useful tool.

What are those settings? I have the same TV as my monitor.

They pay people to generate open source libraries? I'd love to see it

Very unlikely. The reason Garmin watches are successful is because they've carved out an audience (athletes, health and exercise focused). Pebble might have a nice UI but most people would be better off with an Apple Watch or whatever the current flavour of the week is on Android

Even the OLED Garmin watches last much longer than a day. My Venu 3 lasts for about 4 days with me running every day.

You're overestimating people's willingness to write code even if they don't have to do it. Most people just don't want to do it even if AI made is easy to do so. Not sure who you're talking to but most people I know that aren't programmers have zero interest in writing their own software even if they could do it using prompts only.