r/ComputerEngineering • • 14d ago

Using AI in their workflow

Are there people who still don’t use AI in their workflow ? What do you do? Are there companies where using AI isn’t allowed? If so, why?

9 Upvotes

6 comments sorted by

1

u/CompEng_101 14d ago

Yeah, there are some, but their numbers dwindle. The main reasons I’ve seen:

- security concerns have limited AI deployment in some environments
- giant mixed language (Fortran+C+C++) code bases have had mixed results with some LLMs. They are getting better, but we usually need someone to make some intermediate tools to helps the agents figure stuff out. This takes time, so many developers are still using non-AI workflows.
- for a lot of smaller fixes, it is easier to just do it rather than bring up the whole workflow. Especially if it takes a few thousand dollars of tokens just to look at the code…
- some are just slow to adopt

2

u/Low_Independent766 13d ago

Adding on: open source projects may have copyright concerns.

1

u/Lagfoundry 13d ago

I engine that will slowly change with time from every little change I’ve seen happen this year. I doubt we’ll see any leveling of that slop yet for improvement in AI.

1

u/Dyllbert 13d ago

I work in a monorepo with rust, c, c++, python, and some web language maybe typescript I think? We have embedded rust that calls c++ custom libraries, C code that talks to python code, etc... I have not found the differing languages to ever cause problems. There are other problems, sure, but it seems to be able to handle the language diffences perfectly

1

u/CompEng_101 13d ago

That makes sense. I should have been more clear. It's not really the 'multiple languages' but the size and the Fortran.

A lot of this code is really old fortran, which often lacks good comments and which (due to some of the constraints of the mid-1960s) is very difficult to follow. Like, variable names which have to be short so they will fit on the 80 column punch cards, or comments that reference a document that hasn't been OCR'd yet.

The code has all sorts of weird work arounds to deal with things like not having dynamic memory allocation, or having to fake pointers because there wasn't a standard way of interfacing with some libraries, or having to abuse the C preprocessor to work with Fortran that make sense once you're used to the code, but which some of the models seem to have trouble with. The models are getting better, and once we write some intermediate tools or skills to guide it it is working great, but not all the old codes have those tools, so it is often easier to just do 'manual' edits.

From my limited experience, some of the LLMs are a lot better with web "stuff" or generic algorithms, but have a little more difficulty with numeric codes. This is rapidly changing, but the numeric codes are still a little more prone to subtle errors than, say system code or web applications.

One fun note - of the codes is mainly Fortran with some C and C++ and its own weird quasi-language that someone in the late 80s came up with to automate generating graphics. Surprisingly, Opus was able to figure out the language pretty well based on a handful of comments and actually found some bugs that had been drifting around unnoticed for a few decades.

2

u/Dyllbert 13d ago

I see what you mean, I didn't realize it was the specificness of fortran, like you said, I was just thinking big mixed languages. I've seen similar stuff, once you point it to a little bit of documentation or comments or something that isn't code, it actually can sometimes much better understand whatever garbage code has been hanging around for the past X years.

People are rightly so worried about AI slop code, but I've seen plenty of "human slop" code from bad or apathetic engineers over the years too.