Yay , looks like I ' ll have to learn to skate well enough to run from the police Though then again , I drove a highly illegal ebike for years had throttle , did 50 kph and was never ever stopped no matter how blatant i made it . Like at a traffic light , accelerating away from a cop car with only one foot on a pedal , blatant <| sep |> I fit all of those qualifications <| sep |> They probably wouldn ' t if the could . Or if they did , they might end up using them wrong . <| sep |> Either she unmatched or he smashed . No middle ground on that play . <| sep |> Do you mind elaborating on what you mean here a bit ? If I need to scroll to see a whole function definition , I normally think about breaking it up a bit . In the general sense this gets down to one of the fundamental challenges of programming how to organise information and logic in a way that enhances rather than detracts . In this specific case there are a bunch of distinct responsibilities that make the decision about what to split up fairly easy you have code which knows stuff about requests and responses , and code which knows about lawn . I see you already have a planner class you could have this class require a Lawn instance when instantiated and let it figure out all this lawn care stuff instead of the view class planner . # . def grubdeadlineself return self . insectinfo ' grubdeadline ' # . With all this stuff in the planner class , your view becomes really simple def lawndetailrequest , pk lawn getobjector 404 . myplanner plannerlawn return renderrequest , ' plannerlawndetail . html ', ' planner ' myplannerAnd in the template , Grub deadline is planner . grubdeadlinedate % B % d What do you mean by metadata ? Do you mean the comments with filename and date created ? Aye , that ' s what I was thinking of . Personally I start a file with a docstring explaining what the module is for , or if I ' m feeling laconic which is most of the time nothing at all . If I want to see when a file was created or modified , and by which author , I can use e . g . git blame and get this information on a linebyline basis . Including an author name in source code runs into trouble when you have more than one author . Here are some questions to consider what happens when two people have edited the file ? Do you put both names there ? What if someone just fixed up a spelling mistake , do they still count as an author of the file ? After the file has been around for a while , does it have ten authors , ten names ? What about when the first person hasn ' t worked on the file for a month , a year , longer ? Should he or she go back and remove their name ? Why would they remember to ? If they don ' t , what is the value of their name being there ? Of course , if it ' s valuable to you , you should keep doing it ! Let me know how you go improving the closest station performance !