For a lot of code, I switched to generating code rather than using 3rd party libraries. Things like PEG parsers, path finding algorithms, string sanitizers, data type conversion, etc are very conveniently generated by LLMs. It's fast, reduces dependencies, and feels safer to me.

▲

troad 5 hours ago | parent | next [-]

Ah, so you've traded the possibility of bad dependencies for certainty.

▲

raddan 4 hours ago | parent | next [-]

Remember, our objective function here is “feels safe.”

▲

invaliduser 4 hours ago | parent | prev [-]

How can you come to that conclusion, given the specific examples I have given, which are tedious to write, but easy to proof-read and test?

▲

3 hours ago | parent | next [-]

[deleted]

▲

4 hours ago | parent | prev | next [-]

[deleted]

▲

senordevnyc 2 hours ago | parent | prev [-]

Because AI threatens the identity of many programmers.

▲

2 hours ago | parent [-]

[deleted]

	▲	2 hours ago \| parent [-]
		[deleted]

▲

tzs 4 hours ago | parent | prev [-]

Or find the best third party library and copy the code from a widely used version that has been out long enough to have been well tested into your source tree.

The problem is not third party libraries. It is updating third party libraries when the version you have still works fine for your needs.

	▲	estebank 2 hours ago \| parent [-]
		Don't do this. Use a package manager that let's you specify a specific version to pin against. Vendoring side steps most automated tooling that can warn you about vulnerabilities. Vendoring is a signal that your tooling is insufficient, 99% of the time.