- Class
- Resources
- Contests
- SCUSA
- 2021 ACM South Central USA Regional
- 2020 ACM South Central USA Regional
- 2019 ACM South Central USA Regional
- 2018 ACM South Central USA Regional
- 2017 ACM South Central USA Regional
- 2016 ACM South Central USA Regional
- 2015 ACM South Central USA Regional
- 2014 ACM South Central USA Regional
- 2013 ACM South Central USA Regional
- 2012 ACM South Central USA Regional
- 2011 ACM South Central USA Regional
- 2010 ACM South Central USA Regional
- NA Qualifier
- NA Invitational
- SCUSA
- Isaac's Home Page
- Contact Info
- Office/Cell Phone:
225-578-1923 - Class mail:
class@isaac.lsu.edu - Class mailing list:
icpc-practice@isaac.lsu.edu - Work mail:
traxler@lsu.edu - Personal mail:
traxler@gmail.com - Office:
325 Frey Computing
Services Center - LinkedIn:
Isaac Traxler
- Office/Cell Phone:
- arduino
- BRMUG - Baton Rouge Macintosh User Group
- LSU Open
Source Mirrors
Along every step of our journey through life, our mind is being programmed. If we are not programming it ourselves, someone else is doing it to us.
--Joseph Rain
Think twice, code once.
--Waseem Latif
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell
[On identifying talented programmers] It’s just enthusiasm. You ask them what’s the most interesting program they worked on. And then you get them to describe it and its algorithms and what’s going on. If they can’t withstand my questioning on their program, then they’re not good. I’m asking them to describe something they’ve done that they’ve spent blood on. I’ve never met anybody who really did spend blood on something who wasn’t eager to describe what they’ve done and how they did it and why. I let them pick the subject. I don’t pick the subject, so I’m the amateur and they’re the professional in this subject. If they can’t stand an amateur asking them questions about their profession, then they don’t belong.
--Ken Thompson
First solve the problem. Then, write the code.
--Waseem Latif
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
But while you can always write 'spaghetti code' in a procedural language, object-oriented languages used poorly can add meatballs to your spaghetti.
--Andrew Hunt
--Joseph Rain
Think twice, code once.
--Waseem Latif
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell
[On identifying talented programmers] It’s just enthusiasm. You ask them what’s the most interesting program they worked on. And then you get them to describe it and its algorithms and what’s going on. If they can’t withstand my questioning on their program, then they’re not good. I’m asking them to describe something they’ve done that they’ve spent blood on. I’ve never met anybody who really did spend blood on something who wasn’t eager to describe what they’ve done and how they did it and why. I let them pick the subject. I don’t pick the subject, so I’m the amateur and they’re the professional in this subject. If they can’t stand an amateur asking them questions about their profession, then they don’t belong.
--Ken Thompson
First solve the problem. Then, write the code.
--Waseem Latif
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
But while you can always write 'spaghetti code' in a procedural language, object-oriented languages used poorly can add meatballs to your spaghetti.
--Andrew Hunt