Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Always fix errors in reverse order, from the bottom of the file to the top. That way the line numbers don't change as you go.


Oh I learnt the opposite lesson, as later errors might be spurious and just exist because of earlier errors, especially in single pass compiled things like C

But I also do M-x compile, and emacs is clever enough to still find the right line when doing next-error, even if I edit things before.


"Just fix the first error in the list" greatly reduced my anxiety about pages of errors being kicked out when compiling a C program.


Import transaction history into spreadsheet reversing the rows if necessary to start with 1st Jan at the top. This way you can make calculations mid year or mid month then complete them after receiving full statement only by appending rows, hitherto row numbers remain unchanged.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: