- 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
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
I'm not a great programmer; I'm just a good programmer with great habits.
--Kent Beck
College is a waystation - the last convenience store on the road to life-long responsibility.
--Dennis Miller
[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
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell
What is a university/college when the students lose interest?
--Isaac Traxler
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
People who are really serious about software should make their own hardware
--Alan Kay
Premature optimization is the root of all evil.
--Donald Knuth
With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.
--Richard Stallman
Think twice, code once.
--Waseem Latif
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
--Joshua Bloch
I'm not a great programmer; I'm just a good programmer with great habits.
--Kent Beck
College is a waystation - the last convenience store on the road to life-long responsibility.
--Dennis Miller
[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
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell
What is a university/college when the students lose interest?
--Isaac Traxler
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
People who are really serious about software should make their own hardware
--Alan Kay
Premature optimization is the root of all evil.
--Donald Knuth
With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.
--Richard Stallman
Think twice, code once.
--Waseem Latif
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