For the last four years I have been jumping back and forth between Python and Go. The majority of the […]

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We had an outage on Friday 15th March caused by an innocent-looking change, where the “related name” of a Django

We’ve published our in-house coding conventions in a public Github repo: github.com/octoenergy/conventions. It contains guidelines for: Python and Django code;

We’ve published our in-house coding conventions in a public Github repo: github.com/octoenergy/conventions. It contains guidelines for: Python and Django code;

We’ve published our in-house coding conventions in a public Github repo: github.com/octoenergy/conventions. It contains guidelines for: Python and Django code;

We’ve published our in-house coding conventions in a public Github repo: github.com/octoenergy/conventions. It contains guidelines for: Python and Django code;

We’ve published our in-house coding conventions in a public Github repo: github.com/octoenergy/conventions. It contains guidelines for: Python and Django code;

We are trialing out a new feature that can send you a notification when the patches you send to the