Live data from Hacker News

Testing GPT 4's code-writing capabilities with some real world problems

tylerglaiel.substack.com

631–640 of 677 posts

Re: Testing GPT 4's code-writing capabilities with some real world problems

#631
post #605

Earlier quoted context omitted.

Wow. I never expected to be downvoted for such a comment. Downvotes please elucidate as to why we are in the asymptomatic phase with LLMs.

"Luddites" refusing to accept that we might be onto something that is going to change humanity forever... The sad thing is that real luddites would go out and actively sabotage AI development because they think it's a real threat. Yet these people just makes bold and false claims in online forums and continue to move the goalposts once they're proven wrong. Sad. Pathetic. (and obviously, I don't mind being downvoted.…

Seems very man of these here for some reason, trying to find whatever reasons and ways (gonna be licensing mostly) to spread FUD.

Re: Testing GPT 4's code-writing capabilities with some real world problems

#632
post #627

Earlier quoted context omitted.

Disagree -- I think chatGPT will make juniors more palatable to hire. ChatGPT will basically give juniors a free pair programmer to baby-sit their work/progress. Why pay extra for senior devs when juniors can become much more efficient thanks to ChatGPT becoming stack-overflow on steroids. I think the wage gap between junior and senior will actually drop massively. I predict teams will keep 1-3 architect level positi…

I predict the wage gap will actually widen. StackOverflow-on-steroids can only give your so much, so seniors will still be in demand for what they do. It's just the competition between juniors will be fiercer so junior wages will drop.

I think dev wages will stagnate across the board. I think the simple existence of the fear of being replaced by never-tiring, always-working AI will subconsciously prime devs to be willing to work for less. Devs have been in a market with a significant shortage of skilled labor; can we say that remains true after GPT hits the mainstream even more than it already has?

Re: Testing GPT 4's code-writing capabilities with some real world problems

#633

Earlier quoted context omitted.

I see it the other way around the senior engineer is expensive and costs a lot 2 juniors are cheap. Who cares if their code is crap they produce it really fast so they find a bug, just fix it quickly. If anything the time a Sr. spends thinking about things to do things "right" is seen as a waste of time. Whereas the jr. will produce an enormous amount of buggy code but they can fix the bugs quickly by just throwing a…

Because as soon as you tilt from producing features to fixing bugs, you are losing traction and your competitors will win and now you are bankrupt. I've seen entire businesses collapse because of this mentality.

> you are losing traction and your competitors will win

i mean, unless your competitor produces order of magnitude less bugs than you, how can this be true?

Re: Testing GPT 4's code-writing capabilities with some real world problems

#634
post #607

Earlier quoted context omitted.

Well, yes, it got down, but only from 12 mln to 5.5 mln people in agriculture.

Agriculture is still automating and the population has increased what, 4x since then

The US population increased about 15x in that period and one of the major reasons for that is the increase of productivity in agriculture [0]. Higher productivity created more demand.

[0] https://en.wikipedia.org/wiki/Green_Revolution

Re: Testing GPT 4's code-writing capabilities with some real world problems

#635

Earlier quoted context omitted.

The problem is, indeed, that Mr. Glaiel did not know the category of problem he was dealing with. A correct statement would be: "Given a solution set containing both the shortest path through fire and the shortest path avoiding fire, select the solution that fits within six tiles of movement, preferring the solution that avoids fire where possible." It's a constraint optimization problem in disguise: generate a solut…

Can you not do A* where it normally costs one point per tile, 10 points for a fire tile but 1000000 points for > 6 tiles, so you never explore the > 6 options unless you have run out of shorter routes?

If the parent's description of the problem is correct, then imagine this:

You have a solution of length 6, no fire; Solution of length 4, one fire; Ok sure you prefer the no fire one.

the score for the paths is 6 and 13, respectively

Your algorithm works! But as soon as you have a solution of length 10 (or some length bigger than the length you want), a* still prefers that to the solution without fire - but the answer must be less then or equal to six steps

You can modify to make fire cost 1.1. Now if you find a solution of length 6, you know it must be correct (it minimized the number of fire squares and ended up with a length six solve). But if it's not length 6, you need to increase the cost of fire and run again if there was any fire in your solution.

Re: Testing GPT 4's code-writing capabilities with some real world problems

#636
post #98

As a designer/non-coder, it feels like I'm just pair programming all the time. Stuff that usually took me a long time like regexes or Excel/Sheets formulas now take like two minutes. AND I'm learning how they work in the process. I can actually write regexes now that used to be wildly confusing to me a couple of months ago, because Copilot / ChatGPT is walking through the process, making mistakes, and me prodding it…

I don't feel like it's any faster for things I'm not really already familiar with. For instance I asked it to write me a Makefile. It wrote one. It looked plausible but I don't know enough about Make to know. So I had to do loads of reading about Make just to verify that the AI answer was correct. Basically the same amount as just learning anyway.

Re: Testing GPT 4's code-writing capabilities with some real world problems

#637
post #253
post #229

Earlier quoted context omitted.

I think the fear should be less about AI taking 100% of jobs but it should be AI making a single programmer do the job of 5, which would wipe a majority of the market out and make it a non-viable career option for most. Companies are already bloated, imagine when they realize one overworked highly paid senior can replace 10 juniors.

If increased productivity equaled job loss, there would be two programmers alive today, doing the same job as the fewer than 10000 programmers using punch cards as we entered the year 1950. A lot of projects today are not even greenlit because they would be too expensive to make. For instance, there are a lot processes in almost every country that require you to file paper forms, even though we have had web forms and…

yup just literally talked a client out of a nice little mobile project by telling him my rate. lets say I had AI by my side - I'd be quoting the same rate, but number of hours would be lower. project might be a go then.

Re: Testing GPT 4's code-writing capabilities with some real world problems

#638
post #253

Earlier quoted context omitted.

If increased productivity equaled job loss, there would be two programmers alive today, doing the same job as the fewer than 10000 programmers using punch cards as we entered the year 1950. A lot of projects today are not even greenlit because they would be too expensive to make. For instance, there are a lot processes in almost every country that require you to file paper forms, even though we have had web forms and…

If increased productivity equaled job loss, there would be two programmers alive today Increased productivity doesn't necessarily lead to overall job loss, but it will eventually in the area where the productivity is realized. Agricultural employment is a very clear example. https://cdn2.vox-cdn.com/assets/4565243/Ag_workforce.png

otoh the rise of ATMs seems to have increased the number of bank tellers

Re: Testing GPT 4's code-writing capabilities with some real world problems

#639
post #169

Earlier quoted context omitted.

> I really am in awe of how much work people seem willing to do to justify this as revolutionary and programmers as infantile, and also why they do that. It’s fascinating. Equally fascinating is all of the "this is fine" posts from programmers suddenly realizing they are not the gods they once thought. But fret not, programming is not the first industry that has been automated into a shell of itself. Yes, the industr…

"Yes, the industry is going to shrink massively" You meant "expand massively" i think. Did all the programmers manually making machine code get fired and the job of programmer disappear when compilers were invented and totally replaced these jobs? No, it just changed to use the new tool. There wont be any unprecedented mass layoffs, despite what the jaded STEM-hating twitter crowd wants. Companies will simply make th…

  > You meant "expand massively" i think. 
Nope, I meant what I said.

> There wont be any unprecedented mass layoffs

Baghdad Bob strikes again.

Re: Testing GPT 4's code-writing capabilities with some real world problems

#640
post #314
post #229

Earlier quoted context omitted.

I think the fear should be less about AI taking 100% of jobs but it should be AI making a single programmer do the job of 5, which would wipe a majority of the market out and make it a non-viable career option for most. Companies are already bloated, imagine when they realize one overworked highly paid senior can replace 10 juniors.

If as GP says AI could automate 1% of a single programmer's job (the boring part where you write code), then how on earth can you derive that a single programmer could do the job of 5 with AI? It's completely illogical.

many programmers (most?) spend hours a day coding and see it as the best part of their day?
Post reply on HN