Same. There is a logic to all code choices. Even basic things like the placement of empty lines to group code into ‘idea blocks’ massively helps with readability. This idea block touches x, and this next idea block touches y.
A tool can’t perform perform even basic logic like that.
If you have a lot of semantic breakpoints (like the end of a concept) that don’t line up with syntactic breakpoints (like the end of a method or expression body) your code probably needs to be refactored. If you don’t, then automatic code formatting is probably all you need.
This is what kicks off the second Civil War in the United States. And just the like first time, those treasonous Emacs Confederates will be decisively defeated.
<span style="color:#323232;">gdb> break before it crashes
</span><span style="color:#323232;">gdb> record full
</span><span style="color:#323232;">gdb> continue
</span><span style="color:#323232;">(segfault)
</span>
Story time. Back at uni I had a c++ subject. Me being lazy as fuck I didn’t attend many classes and let alone do the practicals during the semester. Exam time comes around. I realise I can’t cram in a whole semester’s learning in a week. Luckily it’s open book exam. Big brain time, I print the whole c++ documentation to take into the exam. I frantically page through the hundreds of pages in my lever arch file looking for answers. I pretty much copy and write example code to questions. Very sad when I failed.
Hah, still relying on butterflies? Real programmers simply use the starting conditions of the universe to understand where their program will spontaneously compile
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.