timster - 12:07 am on Mar 1, 2011 (gmt 0)
And if you do something that is over ~25 lines, you could probably split it up into smaller functions; but I have to disagree with her on that last one! It depends on the context of what your doing.
I'd listen to her. A function should do one thing only. Shorter functions make much more maintainable and flexible code.
Should these be put in a functions file, or should these functions be put in a class.
If you understand object orientation, then creating classes for this sort of functionality will create cleaner, more maintainable, more reusable code. You have worked on small code projects, where you have probably been able to keep everything in mind at once. Once your functions file grows to 10,000 lines or more, you will see what I mean.
That said, if you do not have a grounding in object orientation, then I wouldn't try creating classes ad hoc. You are likely to make a real mess. That is, unless your senior developer can provide guidance to keep you out of trouble.