- 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
A university is what a college becomes when the faculty loses interest in students.
--John Ciardi
Everyday life is like programming, I guess. If you love something you can put beauty into it.
--Donald Knuth
Simple things should be simple, complex things should be possible.
--Alan Kay
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues:
■ Programming language
■ Indentation style
■ Placing of braces
■ Choice of IDE
■ Commenting style
■ Efficiency vs. readability tradeoffs
■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities
■ Naming conventions
■ Use of gotos
■ Use of global variables
■ Measurements, especially productivity measures such as lines of code per day
--Steve McConnell
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
If the steps become to big, they become walls...
--Herb Sutter
[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
The most disastrous thing that you can ever learn is your first programming language.
--Alan Kay
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
Walking on water and developing software from a specification are easy if both are frozen.
--Edward V. Berard
A change in perspective is worth 80 IQ points
--Alan Kay
--John Ciardi
Everyday life is like programming, I guess. If you love something you can put beauty into it.
--Donald Knuth
Simple things should be simple, complex things should be possible.
--Alan Kay
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues:
■ Programming language
■ Indentation style
■ Placing of braces
■ Choice of IDE
■ Commenting style
■ Efficiency vs. readability tradeoffs
■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities
■ Naming conventions
■ Use of gotos
■ Use of global variables
■ Measurements, especially productivity measures such as lines of code per day
--Steve McConnell
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
If the steps become to big, they become walls...
--Herb Sutter
[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
The most disastrous thing that you can ever learn is your first programming language.
--Alan Kay
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
Walking on water and developing software from a specification are easy if both are frozen.
--Edward V. Berard
A change in perspective is worth 80 IQ points
--Alan Kay