Best way to plan out coding and math ?

[givingtnt]

so im working on a project, and I need to lay out how the math works, and the coding..

 

whats the best way to do that on a computer to make it organised ?

[thekeemo]

make a naming system for yourself

and then go head in and modify as needed

[givingtnt]

5 minutes ago, thekeemo said:

make a naming system for yourself

and then go head in and modify as needed

yes, but how do I put on paper in clean way ?

[thekeemo]

1 hour ago, givingtnt said:

yes, but how do I put on paper in clean way ?

I dont do paper

I work first plan after

[givingtnt]

Just now, thekeemo said:

I dont do paper

I work first plan after

wha

 

but paper is alredy done kinda

 

I put my rough ideas on paper to not forget anything

but now I want to do clean presantable thing

is word the choice ?

 

[thekeemo]

1 hour ago, givingtnt said:

wha

 

but paper is alredy done kinda

 

I put my rough ideas on paper to not forget anything

but now I want to do clean presantable thing

is word the choice ?

oooh

Yes word is the word for this

[givingtnt]

Just now, thekeemo said:

oooh

Yes word is the word for this

ok

[2FA]

I normally lay it out in steps how the code will run. 

 

ex.

 

1. step 1
2. step 2
   1. part 1
   2. part 2
   3. part 3
3. step 3
   1. part 1
      1. subpart 1

[madknight3]

Some people draw diagrams that show all their classes and the relationships between them, like UML diagrams for example. There are tools out there for making these. You could combine that with some form of written documentation. People seem to like to use LaTeX for writing math so you could look into that as well.

[vorticalbox]

17 hours ago, DeadEyePsycho said:

I normally lay it out in steps how the code will run. 

 

ex.

 

1. step 1
2. step 2
   1. part 1
   2. part 2
   3. part 3
3. step 3
   1. part 1
      1. subpart 1

 

13 hours ago, madknight3 said:

Some people draw diagrams that show all their classes and the relationships between them, like UML diagrams for example. There are tools out there for making these. You could combine that with some form of written documentation. People seem to like to use LaTeX for writing math so you could look into that as well.

It depends on what I am creating, if it is a program say to calculate the blocks needed for a given structure in minecraft I will use what @DeadEyePsycho posted, If i creating a system that I know it is going to use classes then I will create a class diagram.

 

Use Case's are also very good for showing how the system will work. There are lots of ways to help design programs.

[mathijs727]

Math: use pen and paper.

Code: UML diagram or just code away. Code, unlike pen and paper, is perfectly editable. Use it to your advantage.

[givingtnt]

6 hours ago, vorticalbox said:

 

It depends on what I am creating, if it is a program say to calculate the blocks needed for a given structure in minecraft I will use what @DeadEyePsycho posted, If i creating a system that I know it is going to use classes then I will create a class diagram.

 

Use Case's are also very good for showing how the system will work. There are lots of ways to help design programs.

 

5 hours ago, mathijs727 said:

Math: use pen and paper.

Code: UML diagram or just code away. Code, unlike pen and paper, is perfectly editable. Use it to your advantage.

im creating a database plan that will do math with data and create graphs, as well as math to.create a db that will pair with a html form to create squads im a game.

 

complicated shit, and its coding, math and tables all mixed together.

[vorticalbox]

7 hours ago, givingtnt said:

 

im creating a database plan that will do math with data and create graphs, as well as math to.create a db that will pair with a html form to create squads im a game.

 

complicated shit, and its coding, math and tables all mixed together.

for database design I suggest you look up EER diagrams

[Nuluvius]

I personally begin by deconstructing the specification/requirement down into a set of fundamental concerns. If I am alone and the task is large I may adopt the Agile approach and prioritise these into a 'backlog'. From there I will tackle each discrete 'story' as a chunk of work. This may involve some planning which can consist of UML if it's a software component, some EERD if it's a database or model that I'm trying to create and/or some experimentation (spike) if it's going to be an algorithmic or technological implementation/integration component i.e. a communications protocol or some kind of data manipulation task.

 

I'd usually be doing much of my UML/EERD on paper or a whiteboard. Depending on the specific scenario I may choose to formalise this planning by creating documentation i.e. particularly if I am going to be delegating some/all of the implementation to my team. If I am in a team context then this planning phase will likely involve the whole team - paper/whiteboard is the best medium for such planning sessions.

 

I will stress that this planning is only to provide a very general or basic direction - a sense of the topology. In general Agile teaches us to spend as little time as possible embroiled or entrenched deeply in planning and architecture. This is especially true if one is following Test Driven Development (TDD) as one writes their tests upfront often against the business language which then facilitates the design and architecture to simply coalesce and evolve.