How did people even proof read their thousands of lines of code while typing it

How did people even proof read their thousands of lines of code while typing it before AI LLMs? who the fuck has the patience for that?

人们在 AI LLM 之前打字时如何校对数千行代码？谁他妈有这个耐心？

图片: https://i.4cdn.org/g/1787255924072151.gif

typed languages and linters made everything fairly easy

类型化语言和 linter 使一切变得相当简单

hard part was keeping all that complexity in your head when writing the next part of those thousands of lines, or figuring out exactly which line caused a segfault

困难的部分是在编写这数千行的下一部分时，或者准确地找出哪一行导致了段错误时，请将所有复杂性牢记在心

>>109606369

Did you forget a commit was between 1 and like 30 lines long you bitch ass Nigger

你忘了提交是在 1 行到 30 行之间吗你个混蛋黑鬼

>>109606369

You don't proofread code, you write bugs and then debug.

你不校对代码，你写错误然后调试。

It is actually harder with AI than it is without.

使用人工智能实际上比没有人工智能更难。

>>109606369

Also, nobody was proof reading. Tech lead looked at the pull request to see if the coding style matches company guide lines and QA had to check if the shit works in most cases.

此外，没有人校对。技术负责人查看了拉取请求，看看编码风格是否符合公司指南，而质量检查必须检查这些狗屎在大多数情况下是否有效。

Clueless jobless Fucknigger

无知失业的混蛋

You wrote the code and thus it's probably correct. And if code you wrote isn't probably correct, you're fired for being bad.

您编写了代码，因此它可能是正确的。如果你编写的代码可能不正确，你就会因为不好而被解雇。

This is basically how shops without QA worked forever.

这基本上就是没有 QA 的商店永远运作的方式。

>>109606369

Without AI it's unsuprisingly much harder to write code while not knowing what the fuck you're doing.

如果没有人工智能，毫无疑问，在不知道自己在做什么的情况下编写代码会困难得多。

>>109606369

Does it compile? Does it do what it should? That's enough proof, no re-reading required.

它可以编译吗？它做了它应该做的事吗？证据已经足够了，无需重读。

>>109606369

I used linter or shellproofs

我使用了 linter 或 shellproofs

>>109606410

this is probably the best description of programming I've ever heard :D

这可能是我听过的关于编程的最好描述：D

>>109606369

That's the neat thing, no one did. That's why they're malding now that AI is poking around their code and telling them it's shit.

这真是一件好事，没有人这样做。这就是为什么他们现在因为人工智能正在研究他们的代码并告诉他们这是垃圾而感到愤怒。

>>109607995

trvke

>>109606369

Why do you think things like the bash bug and all the fucking CVE 999.99 linux vulns sat around in their open codebase for literally DECADES?

你认为为什么像 bash bug 和所有该死的 CVE 999.99 linux 漏洞这样的东西在他们的开放代码库中存在了数十年？

Even the people writing the code can't spot vulns or backdoors in their own shit.

即使是编写代码的人也无法发现自己​​的漏洞或后门。

>>109606369

times were different back then, frien

那时的时代不同了，朋友

>>109606410

If writing production code was still a part of my job, I would write the bugs myself and use AI to review my own code. These models are incredibly good at reviewing code even if they aren't all that good at writing it, and debugging my own code was always the worst part about the process.

如果编写生产代码仍然是我工作的一部分，我会自己编写错误并使用人工智能来审查我自己的代码。这些模型非常擅长审查代码，即使它们不太擅长编写代码，而调试我自己的代码始终是该过程中最糟糕的部分。

>>109608041

>These models are incredibly good at reviewing code

>这些模型非常擅长审查代码

it feels like it would just gaslight me like "A-HA! You're using strcpy instead of strncpy! Bad boy"

感觉就像“啊哈！你使用的是 strcpy 而不是 strncpy！坏小子”

>>109608109

some of them are kind of presumptuous about what they consider an actual bug, but for the most part you can tune that away by making them prove runtime assertions and security impact.

其中一些对于他们认为的实际错误有点自以为是，但在大多数情况下，您可以通过让它们证明运行时断言和安全影响来消除这一点。

>>109606369

Nobody pushed 1000's of lines at a time back then.

当时没有人一次推送 1000 行。