ChanServ changed the topic of #asahi-gpu to: Asahi Linux: porting Linux to Apple Silicon macs | GPU / 3D graphics stack black-box RE and development (NO binary reversing) | Keep things on topic | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-gpu
<chadmed>
Sobek[m]: are you saying your lecturer thinks documentation is only required when your code sucks?
<chadmed>
thats a pretty evil attitude to have, especially for low level stuff. we all like to think we write perfect unambiguous human-readable code but... we dont
darkapex1 has joined #asahi-gpu
darkapex has quit [Ping timeout: 480 seconds]
<alyssa>
chadmed: ah that's where you're wrong, 100% of the code I've written recently has sucked :3
<alyssa>
at least on some axis
<alyssa>
I think I just hate code now? :p
<matthewayers[m]>
chadmed: I agree. Documentation is extremely important for any kind of software engineering because it shows that you’re not only understand the code, but you can explain it to others in a way that makes sense and will ensure the maintainability of that code for years to come.
phiologe has joined #asahi-gpu
PhilippvK has quit [Ping timeout: 480 seconds]
Telvana has quit [Ping timeout: 480 seconds]
Telvana has joined #asahi-gpu
PyroPeter_ has joined #asahi-gpu
PyroPeter has quit [Ping timeout: 480 seconds]
<Sobek[m]>
<chadmed> "Sobek: are you saying your..." <- Nah, the OS staff would print our code, read every single line of it and use copious amount of red ink. They had high expectations on documentation quality (especially design documentation, documenting what isn’t in the code, such as why is the design the way it is)
<Sobek[m]>
(I don’t remember if it was the prof or one of the TAs (now working at a fruit company) that said that he taught us the way he did because some of us where very likely to write code he would end up running. I had a friend from that class who discussed recently the nvidia driver saying « oh that piece of code I started as an intern » so that prediction is pretty true too)