So /g/ - how do you plan out design for a non-trivial piece of software?
Do you go full UML or just think of the basic pieces and dig in? I have scrapped a few projects because of what a terrible spaghetti mess they became.
I'm a girl btw
At work we draw up a conceptual diagram that could be called similar to UML, on the whiteboard. Not like actually defining classes and members, just "we're going to write this piece of software, it will communicate with these other softwares with some XML that looks like x, it takes inputs from y, and it will store its data via mechanism z"
Then we just go write the C++ and see if it works.
>spaghetti mess
Avoiding this comes with experience and skill.
>I'm a girl btw
stfu and fuck off
>>55296331
This sounds like 90% of software development. It's either waterfall or agile model based with UML style diagrams outlining components and data/code flow.
>>55296047
Flowchart major logic. UI sketched in a notebook. Built core application, test, code review. Debug. Build error checking. Build UI. Code review.
Once item is solid, features are added and tested. It's slower than agile, but build master and gated check ins are the way to go imho.
>>55297478
Can you suggest a book or something on testing. I can't test my own software for shit and the office says they can't afford to hire an onsite tester.
>>55297385
WATERFALL HHHNNNNNGGGGG NOOOOOOOO
>>55297490
Ask a friend or family member to try it and take notes. You'll learn just how broken it is...
>>55296047
Didn't Karlie Kloss teach you this, coding girl?
For larger projects it helps to plan. The actually programming should be the shortest part of any project.
>>55297490
>I can't test my own software for shit and the office says they can't afford to hire an onsite tester.
>https://en.wikipedia.org/wiki/Software_testing
>>55297385
The place I'm working for has tried agile development numerous times. But the client keeps on demanding new tickets take priority over the planned development. We've just decided to abandon all delusions of control and work on the planned tickets after the SUPER URGENT PRIORITY tickets get taken care of. It's hell, but it's all we can do given the circumstances.
>>55297885
Agile isn't ideal for that model, but there are ways to make it work. Plan your sprints still and see how much work you get done each time. Use that information as an estimate for your next sprint.
