The core philosophy of a Pragmatic Programmer includes taking responsibility for your work, continuously learning, and thinking beyond the immediate problem to understand the bigger picture. Pragmatic Programmers are adaptable, inquisitive, and realistic, and they strive to improve their craft continuously.

DRY stands for "Don't Repeat Yourself." It is important because it encourages reducing duplication in code, which helps to minimize maintenance efforts and the risk of introducing inconsistencies and errors.

Orthogonality in software design means that changes in one part of the system should not affect other parts. This principle promotes modularity and reduces the complexity of the system, making it easier to understand, maintain, and extend.

The Broken Window Theory suggests that visible signs of neglect, such as messy or poorly written code, can lead to further degradation of the codebase. Addressing small issues promptly helps maintain a high standard of quality and prevents the accumulation of technical debt.

Tracer bullets are a technique for developing software by implementing a thin, end-to-end slice of functionality to validate the overall approach. This allows developers to test assumptions, gather feedback early, and adjust the design as needed.

Prototypes are used to explore ideas and validate concepts quickly without committing to a full implementation. Post-it Notes can help in brainstorming, organizing thoughts, and planning tasks visually, making it easier to communicate and iterate on ideas.

Version control is important for tracking changes, collaborating with others, and maintaining a history of the codebase. Best practices include committing frequently, writing meaningful commit messages, and using branching strategies to manage different features and releases.

Rubber duck debugging is a method where a programmer explains their code and problem to an inanimate object (like a rubber duck) to clarify their thinking and identify issues. This technique helps in understanding the problem better and often leads to finding the solution.

A pragmatic team values communication, collaboration, and continuous improvement. Team members take responsibility for their work, share knowledge, and support each other in achieving common goals. They focus on delivering high-quality software and adapting to changing requirements.

Automation is important because it reduces manual effort, minimizes errors, and ensures consistency in repetitive tasks. Automated tests, builds, and deployments help maintain a high level of quality and allow developers to focus on more complex and creative aspects of development.

Duplication leads to increased maintenance efforts, inconsistency, and a higher likelihood of introducing bugs. It makes the codebase harder to understand and evolve. Avoiding duplication by reusing code and applying the DRY principle helps maintain a clean and efficient codebase.

Tips for better estimates include breaking down tasks into smaller, manageable pieces, considering potential risks and uncertainties, using historical data for reference, and involving the team in the estimation process. It's also important to regularly review and adjust estimates based on progress and new information.