- 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
When they first built the University of California at Irvine they just put the buildings in. They did not put any sidewalks, they just planted grass. The next year, they came back and put the sidewalks where the trails were in the grass. Perl is just that kind of language. It is not designed from first principles. Perl is those sidewalks in the grass.
--Larry Wall
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
The really good programmers spend a lot of time programming. I haven’t seen very good programmers who don’t spend a lot of time programming. If I don’t program for two or three days, I need to do it. And you get better at it—you get quicker at it. The side effect of writing all this other stuff is that when you get to doing ordinary problems, you can do them very quickly.
--Joe Armstrong
Think twice, code once.
--Waseem Latif
Not only is this incomprehensible, but the ink is ugly and the paper is from the wrong kind of tree.
--Professor W.
First solve the problem. Then, write the code.
--Waseem Latif
The real nightmare, worse than the one in which the Big Machine wants to kill you, is the one in which it sees you as irrelevant, or not even as a discrete thing to know.
--Benjamin H Bratton
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
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
Einstein repeatedly argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer.
--Frederick P. Brooks Jr.
When in doubt, do something.
--Harry Chapin
One knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?
--Brian Kernighan
Know the rules well, so you can break them effectively
--Dalai Lama XIV
Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
--Paul Graham
--Larry Wall
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
The really good programmers spend a lot of time programming. I haven’t seen very good programmers who don’t spend a lot of time programming. If I don’t program for two or three days, I need to do it. And you get better at it—you get quicker at it. The side effect of writing all this other stuff is that when you get to doing ordinary problems, you can do them very quickly.
--Joe Armstrong
Think twice, code once.
--Waseem Latif
Not only is this incomprehensible, but the ink is ugly and the paper is from the wrong kind of tree.
--Professor W.
First solve the problem. Then, write the code.
--Waseem Latif
The real nightmare, worse than the one in which the Big Machine wants to kill you, is the one in which it sees you as irrelevant, or not even as a discrete thing to know.
--Benjamin H Bratton
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
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
Einstein repeatedly argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer.
--Frederick P. Brooks Jr.
When in doubt, do something.
--Harry Chapin
One knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?
--Brian Kernighan
Know the rules well, so you can break them effectively
--Dalai Lama XIV
Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
--Paul Graham