lincolnloop.com Blog

Lincoln Loop Retreat 2013

Over the last couple months been busy tying up loose ends and preparing for our first “official” company-wide retreat. Even though we’re a fully distributed team, we’re big believers in the power of meet-ups and face-time. They form bonds, build trust, and create a level of personal understanding that can’t be replicated online.

Playing with Pickle Security

Reading about the latest vulnerabilities in Rails, got me thinking about a similar issue we have in Python. It is well known that using pickle on untrusted data is insecure to the point of allowing arbitrary code execution. Or at least it should be…

/dev/loop4

Django Settings Parity: You're Doing It Wrong

A common paradigm in Django is to create different settings files for different environments (local, production, staging, etc.). Everyone has their own opinion on how to set these up (see ours here), that’s not what this post is about. Instead, I’d like to point out the inherent danger in this technique and how to prevent shooting yourself in the foot.

Time Saved Working From Home

One perk Lincoln Loop and other companies with remote staff regularly cite is the lack of a commute. Nothing beats taking the Pajama Freeway to your home office. While reviewing my time entries for last year I started to wonder what the real impact to my available time was by not commuting.

/dev/loop3

2012 Year in Review

2012 was another amazing year at Lincoln Loop. I’m incredibly proud of the work we accomplished and the growth and development we’ve made as a company. A few of the highlights…

Making the Distributed Workplace Work

In our last installment, I introduced our distributed workplace and why we prefer it over a traditional office. Over the years, we’ve learned a lot about how to make a distributed workplace, well… work.

Introducing Learn with Lincoln Loop

Test Coverage in Go

An important part of the process process of learning a new language is to learn the ecosystem that helps you to write better code. In a previous article I covered gdb integration with Go. Next on my list is to find an equivalent of the fantastic Python coverage tool coverage.py. The Go equivalent is called gocov.