- 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
What is a university/college when the students lose interest?
--Isaac Traxler
Know the rules well, so you can break them effectively
--Dalai Lama XIV
The most important property of a program is whether it accomplishes the intention of its user.
--C.A.R. Hoare
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
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
--Martin Fowler
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
It's got to be the going not the getting there that's good.
--Hary Chapin
[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
How do you expect to succeed if you do not know the rules?
--Anonymous
The best way to predict the future is to invent it
--Alan Kay
The issue of finding the best possible answer or achieving maximum efficiency usually arises in industry only after serious performance or legal troubles.
--Steven S. Skiena
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
First solve the problem. Then, write the code.
--Waseem Latif
--Isaac Traxler
Know the rules well, so you can break them effectively
--Dalai Lama XIV
The most important property of a program is whether it accomplishes the intention of its user.
--C.A.R. Hoare
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
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
--Martin Fowler
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
It's got to be the going not the getting there that's good.
--Hary Chapin
[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
How do you expect to succeed if you do not know the rules?
--Anonymous
The best way to predict the future is to invent it
--Alan Kay
The issue of finding the best possible answer or achieving maximum efficiency usually arises in industry only after serious performance or legal troubles.
--Steven S. Skiena
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
First solve the problem. Then, write the code.
--Waseem Latif