| ▲ | summerlight 4 days ago |
| Well you know, all those fun and creative parts in software engineering has been taken over by vibe coding and now humans are supposed to do only tedious works, so probably the same thing applies here. |
|
| ▲ | larodi 4 days ago | parent | next [-] |
| Perhaps much of what humans be doing in this regard is - validation, and the physical work left. But we're not there yet, of course. Vibe coding takes a lot of manual labor, and it's nowhere near for the actually complex tasks such as... multi-part CTEs munching gigs of spatial-temporal data. Speaking of AI in music - well, perhaps many will welcome some tools when you have to: - clear hissing
- process levels in tedious clearing
- auto-removal of aaah, oooh, eeerrmm and similar
- podcast restoration, etc. but of course, nobody wants darn model singing in the mornings, and composers definitely don't need anyone to make up melodies, drum rolls, or bass lines for them. I see deepmind advance their offering, still I find it difficult to imagine any of my producer friends embracing such abomination, and particularly giving it is a remix tool before all else, and not a composition tool. People love details the same way a painter loves details.... dilettantes think all this irrelevant, they really can't be wrong more. |
| |
| ▲ | tmountain 4 days ago | parent | next [-] | | I’ve been writing software for 25 years and am “vibe coding” a fairly complex game in my spare time. It saves time on boilerplate but it is absolutely not capable of doing all the work. There’s still some assembly required and doing so requires domain knowledge and expertise. Also, prompting properly requires the same. If I were to compare the experience to building a house, I’m now the foreman—and no longer doing the manual labor. There’s a real risk of systems making it to production that nobody understands, but we have that today. | | |
| ▲ | larodi 3 days ago | parent | next [-] | | There’s no such thing as vibe composing music, even though experimenting with knobs is not writing notes, and even though writing notes seems like writing programs. À music score may be complete since very first attempts at it, while arrangement and sound désign may be added later. Writing actually catchy music is much more difficult than writing a todo app even though they may seem similar in engineering complexity. Coding is not composing and vice versa. Code which produces music scores is not what audio models do. | | |
| ▲ | tmountain a day ago | parent [-] | | My comment wasn’t in relation to music. It was a response to the parent comment about vibe coding. |
| |
| ▲ | nsteel 4 days ago | parent | prev [-] | | The scary thing is while a construction labourer knows how to properly lay bricks, an AI's output is reliably unreliable. Does the foreman have to go round checking every little thing on the site? That would be a waste of time. Using these AI tools for anything important is too high risk. | | |
| ▲ | tasuki 4 days ago | parent | next [-] | | There exist many problems for which it's easy to verify the inputs-outputs, but much harder to write the functions to convert the inputs into the outputs. Just write an executable spec and have the AI generate the code that fulfills it. Where is the risk? | | |
| ▲ | BobaFloutist 3 days ago | parent [-] | | I guess the risk would be that the cost of compute would explode out of control long before you got a viable solution. To give a bit of an absurd example, I imagine there's a reason it's not currently worth it to generate the code with a random character generator, even though hypothetically that would get you there eventually. If we consider AI a much, MUCH better version of a random character generator (let's say it's a million times faster. No, let's say that it'll get you the solution in quadratic time instead of factorial time), that doesn't necessarily mean it's actually worth it now. | | |
| ▲ | tasuki 3 days ago | parent [-] | | Just time box it then? | | |
| ▲ | BobaFloutist 3 days ago | parent [-] | | Ok in that case I guess the risk would be that it simply wouldn't work and you'd lose whatever time and compute happened in the time box. Which would be a pretty cheap price to pay, but I imagine you'd only try it a few times before giving up and using a different strategy. |
|
|
| |
| ▲ | taneq 4 days ago | parent | prev [-] | | > Does the foreman have to go round checking every little thing on the site? Uh, is that not half of the foreman’s job? They’re there to direct and coordinate the work, resolve unforeseen issues, and to enforce the required quality of work. | | |
| ▲ | nsteel 3 days ago | parent [-] | | I'm certain they don't check every brick. In the same way I shouldn't have to check simple maths. Today's "AI" can't even reliably add two numbers, it's ridiculous. |
|
|
| |
| ▲ | maccard 4 days ago | parent | prev [-] | | Are there any tools that do that better than our existing tools? Are there any companies that are working on that sort of thing? If so, great. If not, then I think the parents point stands. |
|
|
| ▲ | fkyoureadthedoc 3 days ago | parent | prev | next [-] |
| > Well you know, all those fun and creative parts in software engineering has been taken over by vibe coding and now Maybe on your YouTube shorts playlist but not in real life. People doing real work are not vibe coding. The previous perpetual react learner turned ai vibe coder certainly is doing vibe coding, but not for money from a job. |
|
| ▲ | lnenad 4 days ago | parent | prev [-] |
| > Well you know, all those fun and creative parts in software engineering has been taken over by vibe coding What? In what way? Fun and creative parts are thinking about arch, approach, technologies. You shouldn't be letting AI do this. Typing out 40 lines of a React component or FastAPI handler does not involve creativity. Plus nobody is forcing you to use AI to write code, you can be as involved with that as you'd like to. |
| |
| ▲ | cardanome 3 days ago | parent [-] | | > Plus nobody is forcing you to use AI to write code, you can be as involved with that as you'd like to. I had management "strongly encourage" me to use AI for coding. It will absolutely be a requirement soon for many people. The more generative AI you use the more dependent you become of it. Code bases need to be structured different to be friendly to LLM's. So even if you might work somewhere where you technically don't have to use AI, you will need it to even make sense of the code and be competitive. The job of an software engineer for the most part will change fundamentally and there will be no going back. We didn't know how good we had it. | | |
| ▲ | fkyoureadthedoc 3 days ago | parent [-] | | Using AI does not mean Vibe Coding though. You can use it in a variety of ways to make yourself more productive that fall short of vibe coding. |
|
|
