Posts by Tags
You may click on a tag to discover related blog posts and programming quotes.
abstractions
- An extra level of indirection
- Another level of indirection
- Databases
- Pastafarianism
- Powers of abstraction
- The cost of abstraction
- The purpose of abstraction
accuracy
administrators
algorithms
amnesia
answers
anti-principle
api
arrays
arrogance
art
artificial-intelligence
assembly
assumptions
- Best practices
- Can’t possibly go wrong
- Ignorance is bliss
- Immutability
- No evidence
- The real world
- Things that should not work
- Tribal customs
- Wonderful languages
automatization
bad-code
bad-design
bad-habits
bad-ideas
bad-practices
bandwith
basic
beauty
- Beautiful solutions
- Clean and nice programs
- Complexity and beauty
- Programming and poetry
- Put beauty into it
- Simplicity and elegance
- Small and simple code
- The key to performance
- The most beautiful code
- Unformed people
benchmarking
berkeley
binary
blame
bliss
booting
brevity
brute-force
bugs
- Adding bugs
- Beware of bugs
- Bugs
- Cause and solution
- Complete code
- Debuggers
- Enough eyeballs
- Error-free programs
- Generic programs
- Heisenbugs
- No mistakes
- One bug
- Programming and debugging
- Software and carpenters
- Software design
- Software sucks
- System weaknesses
- Testing
- Theory and practice
- Twice as fast
- Unwritten code
- Writing code
business
buzzwords
bytes
c
- Bad programs
- C and C++
- Indentation
- Power and flexibility
- Quirky and flawed C
- Sinking
- Totally safe
- Hello world!
c-plus-plus
- C and C++
- Haskell
- New features
- Object-oriented programming
- Questions and answers
- The optimization operator
- Totally safe
c-sharp
cache
chaos
christmas
civilization
clarity
cobol
code
code-monkeys
comments
committees
communication
compatibility
compilers
compiling
complexity
- Accurate estimations
- Adding a feature
- Complex problems
- Complexity and beauty
- Complexity and computer science
- Complexity and maintainability
- Complexity and reliability
- Complexity and sophistication
- Complexity kills
- Complexity
- Controlling complexity
- Easy to use
- GNOME API
- Intelligent fools
- Modern computing
- New features
- Old programs
- Programmers at work
- Programming graphics in X
- Programming questions
- Simplicity and complexity
- Simplicity, complexity and intelligence
- Simplifying and complicating
- Stop digging
- The most complex things
- The purpose of software engineering
- Too much complexity
- Twice as hard
- Unix is so simple
- Using Haskell
- Worshipping rules
- Keep It Complex and Kludgy
computer-science
- A black art
- Another level of indirection
- Arrogance
- Complexity and computer science
- Computer science
- Computer scientists
- Education
- Giants and midgets
- Magic
- Snake oil
- The art of programming
- The dusty archives
- The purpose of computing
- The purpose of software engineering
- Turing tar-pit
- Two hard things
- Working well
computers
- A perfect match
- A smart terminal
- Addicted
- Answers
- Cause and solution
- Computer errors
- Computer science
- Computers users
- Distributed systems
- Doing lots of things
- Easy to use
- Faster mistakes
- Good programmers
- Hateful computers
- Making the world a better place
- Mind reading
- Old software
- The new super computer
- The right answers
- Thinking computers
- Windows
- Won’t do
- Writing code
concurrency
configuration
confusion
consistency
constants
constraints
conventions
corner-cases
correctness
cost
creativity
cruft
culture
curiosity
data-structures
databases
dead-end
deadlines
debugging
- Adding bugs
- Debuggers
- Debugging
- Debugging time
- Debugging tools
- Debugging
- Deleted code
- Monday’s code
- Programming and debugging
- Test-First
- Twice as hard
- Writing code
decimal
defaults
details
discovering
distributed-computing
documentation
- Bad comments
- Code and comments
- First Law of Documentation
- Incorrect documentation
- Lisp programs
- The proper use of comments
- Useless programs
- Wrong comments
dot-net
doubts
dsl
education
efficiency
encryption
engineering
engineers
entropy
error-recovery
errors
- Compatibility
- Computer errors
- Error-free programs
- Funny hardware
- Software and burgers
- Undetectable errors
- Working well
estimations
evil
evolution
exceptions
expectations
experts
failure
- Bad code
- Blame
- Can’t possibly go wrong
- Communication
- Distributed systems
- Generic programs
- Good comments
- Learning
- Not failing
- Operating systems research
- Programming languages
- Successfully failing
- The proper use of comments
- Working well
falacies
fallacies
fashion
feature-creep
features
fellowship
files
flexibility
focus
fortran
free-software
future
games
getting-things-done
gnome
good-code
- Clean and nice programs
- Good code
- Good code
- Good programmers
- Slow coding
- Small and simple code
- Wonderful languages
- Writing code
good-design
good-ideas
good-practices
good-programs
halloween
hardware
- Changing a light bulb
- Funny hardware
- Slower software
- Software and hardware
- Software efficiency
- Three dangerous things
haskell
hate
hello-world
honesty
hot-spots
html
humility
ide
ideas
imagination
imitation
immutability
implementation
indentation
indirection
industry
infinite-loops
infinity
ingenuity
innovation
input-output
inspiration
intelligence
internet
intuition
iteration
java
joke
- 10 types of people
- Blame
- Bytes and bits
- Changing a light bulb
- Good names
- Halloween and Christmas
- Localhost
- No comments
- No mistakes
- Powers of two
- Programmers and sex
- Programming is hard
- Testing
- The new super computer
- Three dangerous things
- Too literal
- Understanding the code
joy
kids
knowledge
- 10 types of people
- A deeper art
- Answers
- Being exact
- Blind faith
- Can’t do
- Constraints
- Experts
- How stuff works
- Imagination and knowledge
- Knowledge
- Knowledge and wisdom
- Knowledge
- Languages
- Misunderstanding
- One page principle
- Programming questions
- Sharing knowledge
- Something different
- That brain of mine
- The purpose of computing
- The right answers
- The right problem
- Understanding the specifications
lasagna-code
latency
latin
laws
- Complexity and maintainability
- Cost and time
- Expanding programs
- Manpower
- Obsolete programs
- One bug
- The value of a program
- Undetectable errors
- Useful programs
- Useless programs
layers
leadership
leaky-abstractions
learning
- Can’t do
- Good examples
- Learning Perl
- Learning to program
- Learning
- Not failing
- Programming questions
- Successfully failing
- The right problem
- Training
lies
linux
lisp
locking
logic
low-level
machines
magic
maintainability
- Complexity and maintainability
- How stuff works
- Life support
- Maintaining your code
- No comments
- Understanding the code
management
manpower
mathematical-science
memoization
memory
meta
methodologies
methodology
metrics
microsoft
mistakes
ml
monkeys
morons
- Any idiot could write it
- Artificial intelligence
- Computers users
- Consistency
- Don’t press the button
- Good programmers
- Idiocy disallowed
- Indentation
- Infinity
- Morons
- Perl
- Programming today
- Simplifying and complicating
- Software sucks
- The right answers
- Users are idiots
- Yes, my lord
multics
naming
networks
not-invented-here
notations
novelty
null-reference
oauth
object-oriented
- Implicit environments
- Object methodologists
- Object-oriented design
- Object-oriented programming
- Object-oriented programming
- Pastafarianism
- The object-oriented model
obsolescence
- Finished software
- New technologies
- Obsolescence
- Obsolete programs
- Old software
- Unix is dead
- Wearing out
- Wrong comments
octal
old-programs
open-source
operating-systems
opportunistic
optimization
- Bad habits
- Clean and nice programs
- Computing sins
- Faster code
- Optimizing
- Outsmarting compilers
- Premature optimizations
- Small efficiencies
- Speed
- The optimization operator
- Tuning for speed
- Twice as fast
- Using Haskell
- Keep It Simple, Stupid!
originality
overengineering
- Bells and whistles
- Chaotic XML
- Fixing problems
- Forward thinking
- Generic programs
- GNOME API
- Implicit environments
- Modern computing
- New features
- Not necessarily a good idea
- Standard XML
- The biggest program
- The essence of XML
- Too much complexity
- Using Haskell
- X-Windows
paradigms
passion
patterns
perfection
- Adequacy and excellence
- Designing perfection
- Perfection
- Reinventing the wheel
- Testing
- The best components
- Unsolved problems
performance
- Bad habits
- Cost and time
- Diligence
- Expanding programs
- Faster code
- Memory expansion
- Running time
- Slower software
- Software and hardware
- Software efficiency
- The key to performance
- The new super computer
- The three kinds of lies
- Tuning for speed
perl
persistence
phones
php
plan9
planning
poetry
politics
portability
power
practice
precision
predictions
price
principles
probability
problem-solving
- A big gap
- Beautiful solutions
- Do it both ways
- Misunderstanding
- Reinventing the wheel
- Software business
- Solving problems
- The hard part
- The right problem
- Violent XML
problems
- Blame
- Cause and solution
- Communication
- Complex problems
- Debugging
- Juggling
- Programming questions
- Regular expressions
- The hard part
- Things that should not work
- Totally safe
- Two hard things
- Unsolved problems
productivity
profiling
programmers
- A big gap
- A good programmer
- A perfect match
- Adequacy and excellence
- Any idiot could write it
- Bad and good programmers
- Best practices
- Cause and solution
- Changing a light bulb
- Clever tricks
- Complexity and maintainability
- Debuggers
- Education
- Fun
- Good and great programmers
- Good programmers
- Halloween and Christmas
- Handling exceptions
- Hateful computers
- HTML validation
- Indentation
- Low-level programming
- Mind reading
- Morons
- No comments
- Out of business
- Overlooked risks
- Perl
- Powers of abstraction
- Powers of two
- Programmers and sex
- Programmers at work
- Programming questions
- Programming today
- Sharing knowledge
- Software and carpenters
- The common language
- The proper lazyness
- Theory and practice
- Three dangerous things
- Too literal
- Training
- Understanding the code
- Understanding the specifications
- Unsolved problems
- User-friendliness
- Wearing out
- Won’t do
- Writing code
- Yes, my lord
programming
- Adding bugs
- Allocating memory
- Another level of indirection
- Array indices
- Bad and good programmers
- Bad comments
- Bad habits
- Bad programs
- Brute force
- Changing the world
- Code and comments
- Complete code
- Complexity and beauty
- Complexity and maintainability
- Computing sins
- Constants and variables
- Controlling complexity
- Cost and time
- Data structures
- Debugging time
- Debugging tools
- Deleted code
- Development time
- Error-free programs
- Expanding programs
- Faster code
- Fun
- Good and great programmers
- Good code
- Good code
- Good programmers
- Handling exceptions
- Heisenbugs
- Hours of planning
- Ideas
- Immutability
- Iteration and recursion
- Juggling
- Knowledge
- Learning Perl
- Learning to program
- Life support
- Lines of source code
- Localhost
- Low-level programming
- Mail me maybe
- Maintaining your code
- Manpower
- Monday’s code
- Object methodologists
- Object-oriented design
- Object-oriented programming
- Object-oriented programming
- Obsolete programs
- One bug
- Opportunistic refactoring
- Optimizing
- Outsmarting compilers
- Persistent objects
- Premature optimizations
- Programmers at work
- Programming and debugging
- Programming and poetry
- Programming graphics in X
- Programming is hard
- Programming questions
- Programming today
- Put beauty into it
- Regular expressions
- Requirements
- Sharing knowledge
- Show me
- Sinking
- Small and simple code
- Small efficiencies
- Solving problems
- Speed
- System weaknesses
- The art of programming
- The best code
- The hard part
- The key to performance
- The most beautiful code
- The most complex things
- The object-oriented model
- The optimization operator
- The proper use of comments
- The right data structures
- The value of a program
- Threads and signals
- Throwing it away
- Trust
- Tuning for speed
- Turing tar-pit
- Twice as fast
- Twice as hard
- Two hard things
- Type hierarchies
- Undetectable errors
- Unsolved problems
- Unwritten code
- Useful programs
- Useless programs
- Worshipping rules
- Writing code
- Wrong comments
- Yes, my lord
- Keep It Complex and Kludgy
- Keep It Simple, Stupid!
- Hello world!
programming-languages
- Bad code
- Bad programs
- Batteries included
- Bells and whistles
- C and C++
- Data structures
- FORTRAN
- Good comments
- Good names
- Haskell
- IDE features
- Idiocy disallowed
- Implicit environments
- Indentation
- Java and XML
- Languages
- Learning Perl
- Lisp
- Low level
- Mind crippling
- Object-oriented programming
- Old programs
- Perl
- Perl
- PHP and Perl
- PHP
- Piling features
- Power and flexibility
- Programming languages
- Python
- Questions and answers
- Quirky and flawed C
- Ruby
- So easy to implement
- Software business
- The optimization operator
- Totally safe
- Turing tar-pit
- Using Haskell
- Wonderful languages
- Yes, my lord
programs
project-management
proofs
proprietary
proprietary-software
public-relations
purpose
- Doing lots of things
- The purpose of abstraction
- The purpose of computing
- The purpose of software engineering
- Worshipping rules
python
quality
questions
radicalisms
randomness
readability
reading
real-world
recursion
refactoring
regular-expressions
reliability
- A quality money can’t just buy
- Any idiot could write it
- Complexity and reliability
- Correctness
- Enough time
- Faster mistakes
- Mind reading
- Reusable software
- Simplicity and reliability
- Simplicity and reliability
- Software and burgers
- Software and carpenters
- Software quality
- Speed
- The eight fallacies of distributed computing
- Trust
- Twice as fast
religion
requirements
research
resources
responsibility
reusability
rms
rsa
ruby
rules
rules-of-thumb
scheme
science
scope
security
semantics
sentience
sex
sgi
sharing
shipping
signals
simplicity
- A quality money can’t just buy
- As simple as possible
- Bandwidth
- Batteries included
- Designing perfection
- Doubts
- Faster code
- Fixing problems
- Getting things done
- Good code
- Intelligent fools
- KISS principle
- Misunderstanding
- Notations
- Occam’s razor
- One page principle
- Piling features
- Simplicity and complexity
- Simplicity and elegance
- Simplicity and reliability
- Simplicity and reliability
- Simplicity and sophistication
- Simplicity, complexity and intelligence
- Simplicity
- Simplifying and complicating
- Simplifying
- Small and simple code
- Ten seconds
- The best code
- The cost of abstraction
- The most beautiful code
- Unix is so simple
- Keep It Simple, Stupid!
slow
smells
snake-oil
software
- A black art
- A great team
- A quality money can’t just buy
- Adding a feature
- Adding bugs
- Adequacy and excellence
- An extra level of indirection
- Any idiot could write it
- Cause and solution
- Changing a light bulb
- Communication
- Complexity and beauty
- Complexity and maintainability
- Complexity kills
- Configuration
- Correctness
- Cost and time
- Debugging
- Diligence
- Enough eyeballs
- Error-free programs
- Expanding programs
- Faster mistakes
- Finished software
- First Law of Documentation
- Freedom
- Funny hardware
- Generic programs
- Giants and midgets
- Learning to program
- Learning
- Life support
- Lines of source code
- Manpower
- Memory expansion
- Mind reading
- Modern computing
- No mistakes
- Obsolescence
- Obsolete programs
- Old software
- One bug
- Portable programs
- Programming today
- Restricting the flexibility
- Reusable software
- Simplicity and reliability
- Simplicity and reliability
- Slower software
- Smart software
- Software and burgers
- Software and carpenters
- Software and entropy
- Software and hardware
- Software business
- Software design
- Software development
- Software efficiency
- Software quality
- Software sucks
- Software sucks
- Software today
- Speed, quality and price
- Standards
- Stop digging
- System weaknesses
- Team characteristics
- Test-First
- Testing
- The most beautiful code
- The most complex things
- The purpose of software engineering
- The value of a program
- Theory and practice
- Things that should not work
- Three dangerous things
- Too much complexity
- Undetectable errors
- Unix is dead
- Useful programs
- Useless programs
- User expectations
- Vacuumware
- Wearing out
- Working well
solaris
sophistication
source-code
- Bad and good programmers
- Beware of bugs
- Changing the world
- Code and comments
- Complete code
- Debugging time
- Deleted code
- Development time
- Faster code
- Good code
- Good comments
- Good programmers
- Indentation
- Lines of source code
- Maintaining your code
- Microsoft and internet
- Monday’s code
- No comments
- Programming and poetry
- Show me
- Slow coding
- Small and simple code
- Software sucks
- Solving problems
- The best code
- The most beautiful code
- The proper use of comments
- Throwing it away
- Trust
- Twice as hard
- Understanding the code
- Unwritten code
- Worshipping rules
- Writing code
- Wrong comments
spaghetti-code
specifications
speed
stability
stack-traces
standards
stupidity
success
- Fun
- Good names
- Learning
- Powers of abstraction
- Programming languages
- Quirky and flawed C
- Successfully failing
- Team characteristics
- True glory
symmetry
sysfs
systems-design
- A big gap
- Adding a feature
- As simple as possible
- Batteries included
- Compatibility
- Complexity and sophistication
- Complexity
- Constraints
- Designing perfection
- Don’t press the button
- Doubts
- Good design
- Idiocy disallowed
- KISS principle
- Learning to program
- Notations
- Object-oriented design
- Occam’s razor
- Piling features
- Reinventing the wheel
- Restricting the flexibility
- Simplicity and elegance
- Simplifying
- So easy to implement
- Software design
- Software development
- Stay away from the drugs
- The design of UNIX
- Unix
- Users are idiots
- X-Windows
talent
teaching
teamwork
technical-debt
technology
terminals
testing
theory
threads
time
- Accurate estimations
- Clean and nice programs
- Deadlines
- Development time
- Enough time
- Hours of planning
- Linux
- Pi seconds
- Predictions
- Running time
- Scope, time and cost
- Speed
- The proper lazyness
- Tuning for speed
- Twice as fast
- Work expansion
time-management
topology
tradition
training
turing-complete
tv
type-systems
universe
unix
- Berkeley
- GNOME API
- Have you tried turning it off and on again?
- Hidden
- Operating systems research
- RMS
- The design of UNIX
- Tomorrow’s Unix
- Unix
- Unix is dead
- Unix is so simple
- Unix
usability
useful-programs
useless
useless-programs
user-friendly
user-interfaces
users
- Computer errors
- Computers users
- Don’t press the button
- Finished software
- Handling exceptions
- Hateful computers
- Programming today
- Software sucks
- Ten seconds
- The customer is always right, right?
- The design of UNIX
- The right answers
- Three dangerous things
- User expectations
- Users are idiots
- Users
utility
vacuumware
validation
value
variables
weaknesses
windows
windows-nt
wisdom
work
worst-case-scenario
writing
- Bad programs
- Error-free programs
- Good programmers
- Learning to program
- No comments
- Programming and poetry
- Slow coding
- True glory
- Wonderful languages
- Worshipping rules
- Writing code
- Writing code