Re^5: Templating system choice

People are lazy. I am lazy. I gravitate toward what I know as opposed to what will make my future work and maintenance easier. MVC is an excellent rule of thumb; TT makes it trivial to break. Which makes writing new code quick for those handy with it at the expense of sometimes immense, even untenable, technical debt, AKA we need a total rewrite.

Discipline is hard. Correctness is hard. It pays benefits down the road. Depending. :P There are no actual rules in design, only rules of thumb.

Comment on Re^5: Templating system choice

Replies are listed 'Best First'.
Re^6: Templating system choice by GrandFather (Saint) on Dec 21, 2020 at 20:20 UTC
I'm lazy. I gravitate toward writing what I hope to be clear robust code now to tackle the task at hand without shutting doors as far as reasonable knowing I'll probably come back to it later. I have a friend/co-worker who knows that the first cut of a piece of code is rubbish and expects to completely rewrite it later. He also like to future proof code so adds coding overhead "just in case we need it later". We pay the penalty for that future proofing every tie we touch the code. I take longer to get the first cut out, but my code almost never needs a total rewrite and is generally easier to maintain and extend. His future proofing almost never gets used, but is always a maintenance burden. He is often correct in that the first cut of his code generally ends up being replaced or is a maintenance nightmare. Laziness wins, but it has to be the right sort. Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply]

Replies are listed 'Best First'.

Re^6: Templating system choice
by GrandFather (Saint) on Dec 21, 2020 at 20:20 UTC

I'm lazy. I gravitate toward writing what I hope to be clear robust code now to tackle the task at hand without shutting doors as far as reasonable knowing I'll probably come back to it later. I have a friend/co-worker who knows that the first cut of a piece of code is rubbish and expects to completely rewrite it later. He also like to future proof code so adds coding overhead "just in case we need it later". We pay the penalty for that future proofing every tie we touch the code.

I take longer to get the first cut out, but my code almost never needs a total rewrite and is generally easier to maintain and extend. His future proofing almost never gets used, but is always a maintenance burden. He is often correct in that the first cut of his code generally ends up being replaced or is a maintenance nightmare. Laziness wins, but it has to be the right sort.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

[reply]