Ryan Day

Posted on January 2, 2015 by

Configuration in the Environment

Moving Fast published this article, regarding the danger of using the environment to store secrets. I think that every time is a good time to re-evaluate design choices with security implications. So that’s what I’m doing here. My previous postĀ focused specifically onĀ the security implications of storing keys in your code repository. This was a particularly Read More

Posted on August 19, 2014 by

The Wrong Problems

Developers spend most of the day working on one, or maybe two, codebases. They run into the same day-to-day problems that all other developers do. They come up with solutions that most other developers will also come up with. They implement these solutions, and try to publicize them. If they are lucky, their solution will Read More

Posted on August 11, 2014 by

Lose The Employee Mentality

I still haven’t done this. I run into problems in almost every project because of it. I think a very long winded discussion about this basically boils down to: Employees need skills. Businesses need successes. Employees hand a resume to a company that has a list of skills on it; programming languages, frameworks, databases, other Read More

Posted on July 30, 2014 by

Log Errors to Github

Log files are great, but why not make errors front and center in your issue tracker. One thing I like to do is automatically log errors to Github. That way when something goes wrong, it is right in my face. class GithubError(logging.Handler): def __init__(self, token, repo_owner, repo): logging.Handler.__init__(self) self.token = token self.repo_owner = repo_owner self.repo Read More

Newer Posts
Older Posts