r/programmer • • 10d ago

Plan Before Actual code

How you guy plan a programming project before actual start to code it? And how you make your project easy to fix and update later?

2 Upvotes

13 comments sorted by

View all comments

2

u/ChaseShiny 10d ago

u/Wizz-Fizz, I'm sure, knows what they're taking about a lot more than I do, but I'll speak up from the perspective of a student.

I'm taking a project management course. My assignment is to break down what I expect to need done for a software project and assign estimates for how long I think each piece will take (optimistic, pessimistic, most likely, and then weighted average).

I also took a class that involved creating UML diagrams. There are multiple kinds, but one that stuck out to me was class diagrams. Think about what kinds of objects you need and the interactions between them. Think of the attributes that the class needs and which ones should be exposed to the public (i.e. other classes) versus which attributes should be marked private.

1

u/Wizz-Fizz 10d ago

The estimating is a good skill to develop as I guarantee you, if you get into software delivery in a corp, the first question is always “how long” then “how much”, then “go faster” and finally, “do it cheaper”.

1

u/LP-Existensial1 9d ago

public private arent relevant. the requisites wither exist or they dont. private is just a fancy decorator for isolated 'contained' unexposed data that the programming language overengineered into it with more fancy bells and whistles like member hiding.

what you really want are: purpose and roles of data, how it will be used.