undefined | Better HN

0 pointssamwillis3y ago0 comments

> If you take time out every now and then to completely refactor your code base it can actually be surprisingly effective.

So much this!

Current project I'm on, I own the entire front end for a major modernisation (AKA rewrite) of a legacy application and we are working in 4 week "sprints". I'm giving myself two days every month just to refactor the code I wrote that month.

How you plan to structure a project never works out, you always find better ways as you go and as the objective and priorities change (they always do).

On another tangent, before pivoting into software development I used to be a mechanical/industrial engineer. The parallels between coding and CAD are enormous. With CAD you also need to be spending 10% of your time "refactoring" your model. It's almost exactly the same from a maintainability perspective and leaving the model with good hygiene for the next person to work on.

0 comments

jacquesm3y ago

> How you plan to structure a project never works out, you always find better ways as you go and as the objective and priorities change (they always do).

I always joke I write everything three times. The first time to get a feel for the space, the second time because I think I now understand it and then again when I finally really understand it. Most of the times these three look absolutely nothing like each other.

samwillisOP3y ago

I think that even extends over longer time periods to projects as a whole and an evolving team. Sticking to my current project which has a nearly 20 year legacy and looks nothing like what it was when it started:

V1: Perl CGI, HTML forms, very little js

V2: Perl CGI, JQuery, Ajax (done badly with js code generated by Perl code)

V3: Perl backend rest API (will be "public"). TypeScript+Vue front end.

Each time a transition has happened as the application features have outgrown the architecture, and more has bean learnt about how people use the product and therefore what it needs to do.

In this case it has now grown the the point that Node and build tools are required.

jacquesm3y ago

Neat, is this a public project. You make me curious what it is that you are hacking away at!

1 more reply

j / k navigate · click thread line to collapse

0 pointssamwillis3y ago0 comments

> If you take time out every now and then to completely refactor your code base it can actually be surprisingly effective.

So much this!

How you plan to structure a project never works out, you always find better ways as you go and as the objective and priorities change (they always do).

0 comments

jacquesm3y ago

> How you plan to structure a project never works out, you always find better ways as you go and as the objective and priorities change (they always do).

samwillisOP3y ago

V1: Perl CGI, HTML forms, very little js

V2: Perl CGI, JQuery, Ajax (done badly with js code generated by Perl code)

V3: Perl backend rest API (will be "public"). TypeScript+Vue front end.

Each time a transition has happened as the application features have outgrown the architecture, and more has bean learnt about how people use the product and therefore what it needs to do.

In this case it has now grown the the point that Node and build tools are required.

jacquesm3y ago

Neat, is this a public project. You make me curious what it is that you are hacking away at!

1 more reply

j / k navigate · click thread line to collapse