Learning how to work in other people's code is part of being a developer, senior or not
Fare enough, but thats not the problem...as i've had my fare share of toiling with others code, fixing, documenting, etc...
It's just, I want everything to be as professional as possible and coding conventions are a step in the right direction...not that TL or AdoDB are not professionally written...I've peaked at the source and I like AKAPJ style and everything, it's just not my own...
This is where programming, for me anyways, becomes as much as art as it does a science...
Unless you can truthfully say your framework is/will-be different than the bulk of the others out there by a decent margin, I would seriously consider using someone elses existing and established framework
Well yes, they would be...as I would just be offering a DB abstraction layer, but an OR/M system and the template engine, uses drastically different techniques than anything out there today as far as I know and I've researched this intensely...but I'd need quite alot of other supporting classes, parsers, etc for this to work, which is why I'm troubled...as I don't exactly want to wait forever before I get started on this CMS
If you can't be bothered to learn their codestyle, build a "beautifier" to convert the code to your style. Although I will raise an "arrogance" flag at it, but won't do much worse than that
Considered that, but it's almost impossible...as I don't mean exclusively formatting, style, etc, although that's part of it...commenting, variable names, etc...all need the touch of a human...
I've read about TDD and I see it's usefulness...although I'm still not 100% convinced it's practical...to each to his own I suppose...
My problem is, that despite great deals of time spent planning, etc, I refactor code way to much to consider writing test cases for each object/function. I'm sure some might live past phase one, but every time I write a function I consider refactoring strategies, etc...
I'd be spending more time writing tests then writing code...which is where the discipline would come in, but the desire isn't there, yet anyways...
I write pretty compact functions and always look to further abstract a design, making debugging much easier and obsess quite a bit about a funciton returning expected results...thus making it harder for me to consider TDD as first round I usually get functions right as far as implementation is concerned. The TDD would come in handy for me when months later I modify some source code and have a green light go red, notifying me of a bug, instead of finding it the hard way, via user complaint, etc...
So for me, because of my obsession with writing a function right the first time...writing tests for functions, etc before I even write a single line of code would seem impractical, as I already spend greats deals of energy making sure their right...and the constant refactoring makes it difficult to keep synchronized...
I would MUCH prefer to use some kind of inline macro like ASSERT, so I could test in the implementation itself...I figure the runtime issues caused by tests is why PHP and other scripting languages use an external library/framework of sorts...
At least that's my understanding of the subject anyways...
Anyways the point is, writing PHP test cases goes against my very style of developing...where I plan alot, write a little, refactor, debug and repeat until I'm convinced the function handles every input properly according to plan.
I'm all for change, but the additional work load doesn't do the technique justice...whereas inline macros would be minimal to keep up to date...much like phpDocumentor comments...
What am I missing? Something else you can convince me on?