<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Standards on Caktus Group</title><link>https://www.caktusgroup.com/tags/standards/</link><description>Recent content in Standards on Caktus Group</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 28 Jul 2014 11:00:00 +0000</lastBuildDate><atom:link href="https://www.caktusgroup.com/tags/standards/index.xml" rel="self" type="application/rss+xml"/><item><title>A Culture of Code Reviews</title><link>https://www.caktusgroup.com/blog/2014/07/28/culture-code-reviews/</link><pubDate>Mon, 28 Jul 2014 11:00:00 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2014/07/28/culture-code-reviews/</guid><description>&lt;p>Code reviews are one of those things that everyone agrees are worthwhile, but sometimes don’t get done. A good way to keep getting the benefits of code reviews is to establish, and even nurture, a culture of code reviews.&lt;/p></description></item><item><title>Towards a Standard for Django Session Messages</title><link>https://www.caktusgroup.com/blog/2009/06/19/towards-a-standard-for-django-session-messages/</link><pubDate>Fri, 19 Jun 2009 15:31:13 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2009/06/19/towards-a-standard-for-django-session-messages/</guid><description>&lt;p>Django needs a standard way in which session-specific messages can be created and retrieved for display to the user. For years we&amp;rsquo;ve been surviving using &lt;code>user.message_set&lt;/code> to store messages that are really specific to the current session, not the user, or using the latest and greatest Django snippet, pluggable app, or custom crafted middleware to handle messages in a more appropriate way.&lt;/p></description></item></channel></rss>