bro's post is as messy as gahoo code
unreadable
neo-luddites won't shut up about ai slop code, but they never mention the human slop code that got into floss from programs like gsoc. throwback to r2con 2016: gsoc students presented their projects on stage. One of these projects was about stepping backwards in esil, the emulation engine of radare2. the guy had idk how many months just to go on stage, present shitload of awful code and say something like "stepping backwards is really hard, and it doesn't fully work yet". During the q&a i stood up and explained that esil had hooks for recording write access to memory and registers and that all he needed to do was to push old values on a stack on write access. I get that life is shit most of the time, people have depression or other problems, and sometimes you don't manage to get anything done in years. This was nothing like that. The guy had no idea what he was doing and therefor came up with some bullshit that we just managed to cleanup this year. Tbh i don't blame this guy, i blame universities, where students are taught how to draw uml diagrams instead of programming and i blame programs like gsoc who bait people with no experience into projects and put time pressure on them to get things done. Please don't say, that we should have given him an easier task. Backstepping was a really low hanging fruit, which later took me 2-3h when i rewrote it (i'm very slow at typing).
The code that he submitted was human slop code, and this was not the only case. Nothing good has ever come out of gsoc for radare2. But why is that? I don't think that the guy is a bad programmer per se, but that a lack of familiarity and experience with a codebase combined a deadline will almost always lead to bad code. I'm so glad that radare2 is no longer doing gsoc.


Argyl
in reply to Bricky • •WhiteExodite
in reply to Bricky • • •TLH
in reply to WhiteExodite • • •