Karl Evard
About Karl Evard
Karl Evard is a Staff Software Engineer at The New York Times, where he has worked since 2014. He specializes in Java-based web application environments and has a strong background in various programming languages and software development tools.
Work at The New York Times
Karl Evard has been employed at The New York Times as a Staff Software Engineer since 2014. In this role, he contributes to the development and maintenance of software systems that support the organization's digital platforms. His work involves applying his extensive knowledge of programming languages and software development practices to enhance the functionality and performance of applications.
Previous Experience at Bovis Lend Lease
Before his tenure at The New York Times, Karl Evard worked as an IT Department Intern at Bovis Lend Lease in 2004 for a duration of two months. This early experience provided him with foundational skills in IT and exposure to the software development environment, which he has built upon throughout his career.
Education and Expertise
Karl Evard studied at Stony Brook University, where he earned a Bachelor of Science degree in Computer Engineering and Computer Science from 2002 to 2007. His education laid the groundwork for his expertise in various programming languages, including Groovy, Scala, and Octave, as well as his proficiency in deploying and managing Java-based web application environments.
Software Development Skills
Karl Evard possesses a comprehensive understanding of the software development life cycle. He has hands-on experience in design, testing, deploying, documenting, and maintaining software. His skills extend to deploying and managing JSP web containers such as Tomcat, WebLogic, and Glassfish, as well as using multiple integrated development environments like Eclipse, NetBeans, and Talend.
Version Control Systems Experience
Karl Evard is experienced in using various version control systems, including SVN, CVS, and Git. This experience indicates a strong foundation in collaborative software development practices, allowing him to effectively manage code changes and collaborate with other developers in team environments.