For most teams, dependency freshness is a pain that is often ignored. “If it works –don’t change it” is the prevailing attitude, but as a lot of applications become web-focused, dependencies inevitably start gaining traction. Why does dependency freshness matter, and how do we proactively stay on top of it?
Today we present Freshli - the dependency freshness tool we have been working on. The microphone goes to the team involved: Cassandra Carothers, Technical Sales Manager here at Corgibytes, and Catalina De la Cuesta, Chris Cumming, and Dave Farinelli, our Lead Code Whisperers. The Freshli tool captures historical libyear metrics about a project's dependencies. Freshli stays alongside your codebase and works together with code quality tools, showing where your project is going overtime. It is designed to work with multiple languages, and it currently supports Ruby, Perl, Python, PHP, and .NET.
If you are interested to know more about Freshli, make sure you reach out to our team on LinkedIn after you’ve listened to the episode.
Mentioned in this episode:
Cassandra Carothers at linkedin.com/in/cassandramcarothers/
Catalina De la Cuesta at linkedin.com/in/catalinadelacuesta/
Dave Farinelli at linkedin.com/in/dfar-io/
Chris Cumming at linkedin.com/in/chris-cumming/
Libyear at https://libyear.com
Corgibytes at https://corgibytes.com
Freshli at GitHub at https://github.com/corgibytes/freshli-lib
When developers talk about what they find exciting, they usually talk about new things. Very little content is about the actual job, about working in the existing system. When they do talk about legacy, they usually focus on how much they hate it. Where does that animosity come from and how do we confront it?
Today we get to the bottom of it with Barry O’Sullivan. Barry is a modern web development contractor with 15 years of experience in legacy web applications. He is the founder of DDIE and the co-organizer of PHP Dublin. We discuss the fear response to legacy code, the mocking of those who created it, and the ignorance of those who are quick to mock. We look at the common mistakes that lead to the fear of legacy code and discuss some common-sense solutions to overcome what is essentially a social and skill-based problem with technology.
When you are done listening to the episode, make sure you connect with Barry on LinkedIn, and follow him on Twitter and Github.
Mentioned in this episode:
Barry O’Sullivan on LinkedIn: https://www.linkedin.com/in/barryosu/
Barry O’Sullivan on Twitter: https://twitter.com/barryosull
Barry O’Sullivan on Github: https://github.com/barryosull
Barry O’Sullivan on the web: https://barryosull.com
PHP Dublin: https://www.meetup.com/PHP-Dublin/
Matthew Stewart, The Management Myth: Debunking Modern Business Philosophy: https://www.amazon.com/Management-Myth-Debunking-Business-Philosophy/dp/0393338525