Remix.run Logo
▲ truncate a day ago

Most SWE who "oppose AI" in my experience, don't oppose AI but oppose its how its being adapted or used. All gas no brakes. You can't really say "lets think about it a bit" without becoming AI denier/opposer or whatever.

We make aggressive decisions, based on overly optimistic bet on "AI will fix it" mindset. I think it should be more towards, given what we have now and may put in little bit of optimism around AI how can go forward without completely dismissing decades of engineering principles we developed. If AI really goes 10x better than what it is now, then we can just build stuff much faster then anyway, but it didn't we made something reliable today as well something we can keep building on 5/10 years from now.

▲stinkbeetle a day ago | parent [-]

> You can't really say "lets think about it a bit" without becoming AI denier/opposer or whatever.

What does "lets think about it a bit" even mean though? You want other people to stop using productive tools? Or you want to be able to opt out of using productive tools without an employer worrying about it? There always seems to be either a shifting of burden to others, or a denial that AI tools increase productivity.

People can think about AI and use AI with all gas and no brakes. Or you can opt out of using AI for as long as you like to think about things.

▲truncate a day ago | parent | next [-]

>> You want other people to stop using productive tools?

This is the EXACTLY the kind of BS you get. No, not asking you to stop using those tools. Its not 0 or 1 thing. Its not a choice between "all gas no brake" and "I wont use AI". But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.

The alternative is don't go all gas, work strategically thinking a bit longer term like we always had in past, and maybe you loose little velocity in short term, but you are likely better off in long term.

AI is always ready to implement something, or generate code, and make decisions, and it will do whatever you ask it to do. However, to make right decisions you need to understand the problem/context etc etc. And that was always significant portion of work, and you can be little faster with that with AI, but I think that part is still kind of slow but we as industry are in denial about that, and just not doing that part that well anymore.

▲stinkbeetle a day ago | parent [-]

> This is the EXACTLY the kind of BS you get. No, not asking you to stop using those tools. Its not 0 or 1 thing. Its not a choice between "all gas no brake" and "I wont use AI".

No, THIS is exactly the kind of BS you get. All that and you didn't answer the question at all. What exactly do you want?

> But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.

Yep, people do think about it. Don't you? Do you not like how others think about it, or do you not like the conclusions they reach? Would you rather they do something differently? Without the BS, let's hear it. What do you want?

▲lanstin a day ago | parent | prev | next [-]

You can go out and take a walk around the block/quad/building still. And come back knowing the exact prompt to use to find the true explanation for some puzzling data anomaly/code behavior/failure mode.

▲jimbokun a day ago | parent | prev | next [-]

> What does "lets think about it a bit" even mean though?

Don't push code no human has read into production.

▲stinkbeetle a day ago | parent [-]

Well I asked the OP, but appreciate your opinion and contribution too.

> Don't push code no human has read into production.

So you don't want to do that in your production environments? Or do you want others to not do that in their production environments?

▲jimbokun 4 hours ago | parent [-]

Both.

▲wholinator2 a day ago | parent | prev | next [-]

Surely those aren't the only two options though? What if "let's think about it a bit" is about your coworkers going head first into a design that you know will fail, and then maybe let's think about how we can do a better design before we lock in a shit one. The AI does build _exactly_ what you ask, whether it's a smart choice or not. Surely you can just automate that choice to the AI as well, why not? "Think about all the ways to design this and pick the best". But possibly we are being led blind into a tar pit. So maybe, just maybe, we can spend a seconds of our lives to try to involve our human domain knowledge and hard won expertise at this job and its systems to guide the AI in a more productive route. Or is this scenario really just about slowing down everyone around you because you're secretely an indignant, neolithic, asshole.

▲stinkbeetle 21 hours ago | parent [-]

> Surely those aren't the only two options though?

(EDIT) I didn't mean to imply those as only two options, just points of a spectrum.

> What if "let's think about it a bit" is about your coworkers going head first into a design that you know will fail, and then maybe let's think about how we can do a better design before we lock in a shit one. The AI does build _exactly_ what you ask, whether it's a smart choice or not. Surely you can just automate that choice to the AI as well, why not? "Think about all the ways to design this and pick the best". But possibly we are being led blind into a tar pit. So maybe, just maybe, we can spend a seconds of our lives to try to involve our human domain knowledge and hard won expertise at this job and its systems to guide the AI in a more productive route. Or is this scenario really just about slowing down everyone around you because you're secretely an indignant, neolithic, asshole.

Having different perspectives and advocating for what you think works best, how to use tools, how to approach problems, has always been a thing and always will be. People where I work have a lot of different ways of using AI and share ideas and techniques, for example. Telling someone to not do what they have found to work with things like "let's think about it a bit" doesn't work though, that's not collaborative, you don't just tell others to stop and think, you have to actually do some thinking yourself and come up with constructive ideas. Doomsaying or vaguely handwaving at how bad things might be doesn't work either. It's like telling farmers they shouldn't sow their crops because you're concerned the gods might be angry and smite the village so they should stop and think about it a bit.

The reality is that AI is a very productive tool and it is never going to be stopped now. Bad things could come of using AI, bad things could come of not using AI, a bad thing could happen when you walk down the street tomorrow. A lot of people are scared by it, but really just saying things like "let's think about it a bit" betrays the lack of thought that has gone in to understanding why other people use it and how people react to that kind of thing in general. Not really surprising OP has seen a bit of apathy or hostility to their message.

▲Tanjreeve 17 hours ago | parent | prev [-]

I think ops point is the tools are irrelevant. What comes out is the only thing that matters. Making grandiose assumptions about the arc of history is the job of pundits and linkedin influencers.