Wet jumping right in on Crockery

hcgtv · 2007-05-05 14:26:17

Looking at the commits by Wet into the Crockery branch makes one wonder how does he know what to change?

Please, I don’t want to start another “what the future holds” kind of thread, I’m just curious. How can a programmer gain SVN access a few days ago and start making changes without having some kind of ticket system in place where he or she can pick what to work on?

I’ve been a programmer for many years and every project I’ve worked on had two things:

a) A database scheme – tables and fields explained.
b) What needed to be done and who was working on what.

Just curious, not bashing anyone or anything.

zem · 2007-05-05 23:53:56

Looking at the commits by Wet into the Crockery branch makes one wonder how does he know what to change?

Please, I don’t want to start another “what the future holds” kind of thread, I’m just curious. How can a programmer gain SVN access a few days ago and start making changes without having some kind of ticket system in place where he or she can pick what to work on?

Crockery is the experimental branch. Pretty much anything goes: check in first, ask questions later. If it’s good, we’ll keep it. If it’s not, we’ll remove or replace it. That’s how decisions about new features get made: by selecting the best of the available code.

The reason we’ve selected people like Wet and Ruud for svn checkin access is that their patches show they already have a good understanding of what does and doesn’t belong in the Textpattern core.

Which tables and fields do you think need explaining? Most should be easy to understand for anyone who needs to delve into the schema.

Last edited by zem (2007-05-05 23:56:40)

hcgtv · 2007-05-06 00:40:53

zem wrote:

Which tables and fields do you think need explaining?

When I have a question, I’ll pop into your cubicle and ask :)

zem · 2007-05-06 01:03:57

With both the schema and code, if it’s written well, comments and documentation should not generally be required. If a developer or DBA can’t understand the purpose of a table or field from its name, that probably indicates a poorly chosen name, not a lack of documentation.

There are exceptions of course — some things are just naturaly complex or esoteric — but that’s the general philosophy regarding code and schema documentation in agile projects like Textpattern.

root · 2007-05-06 01:40:51

Interesting approach. Have there ever been problems with conflicting code or overwritten work?

zem · 2007-05-06 02:28:58

Rarely. svn’s conflict resolution makes it difficult to do accidentally. Testing takes care of the rest.

Textpattern CMS

Textpattern CMS support forum

#1 2007-05-05 14:26:17

Wet jumping right in on Crockery

#2 2007-05-05 23:53:56

Re: Wet jumping right in on Crockery

#3 2007-05-06 00:40:53

Re: Wet jumping right in on Crockery

#4 2007-05-06 01:03:57

Re: Wet jumping right in on Crockery

#5 2007-05-06 01:40:51

Re: Wet jumping right in on Crockery

#6 2007-05-06 02:28:58

Re: Wet jumping right in on Crockery

Board footer