You are viewing a single comment's thread.

view the rest of the comments →

0
1

[–] cantaloupe6 0 points 1 point (+1|-0) ago  (edited ago)

For about 500k lines you can use a spreadsheet. Identify features and sub-tasks. Prioritize those. Identify what a minimal viable system would be, what should it do? Identify what technology you believe should be used - have at least three vendors. Try to adopt an existing well known architecture, can the system be split up as services? Create unit test so you know if changes break you system. Create a data-model so you have an idea of what's needed. After building a minimal viable implementation what updates to parts provides the most economic utility? Is there some part you can outsource? Is there tech you can adopt? They'll be making on going improvements.

Make some S.M.A.R.T. goals. Use a distributed source control system for exploratory work. Keep the sections of the system small enough to be held in one's head.

Create documentation that explains what the functionality should do and use a standardize format do you or anyone could come back later and have an explaination - include sequencing diagrams.

If you use REST services parts of the system can be mocked with scripting for a fast turn around.

The code should be very readable so that anyone could look an understand. For a small team comments explaining confusing points or todos can be helpful.

It may be necessary to look at the data rate - depending on the functionality.