borkborkbork

7 ms·

1. 31.▲
   by borkborkbork 10y ago

   The Chicago devs that work downtown ride public transit or commuter rail. The ones that don't work downtown don't have much traffic to deal with.
2. 32.▲
   by borkborkbork 10y ago

   Shameless plug
3. 33.▲
   by borkborkbork 10y ago

   Agreed
4. 34.▲
   by borkborkbork 10y ago

   Which companies? _trollface_
5. 35.▲
   by borkborkbork 10y ago

   This problem isn't specific to Rails 3.1. At some point, your frameworks need to be upgraded, because at some point the developers stop supporting your version. Django announced recently that 1.7 would no longer be getting security fix
6. 36.▲
   by borkborkbork 10y ago

   I went through the same upgrade process that the OP mentioned at scale. The company had 5 or 6 microservices that needed to be upgraded from Rails 3.1. While having 10,000+ unit tests was very helpful for reducing regressions, we still had