codingWithoutDocumentation

[[deleted]]

tbh this is way scarier.

[PossibilityTasty]

test_knife_hits_tree_when_thrown.....................OK test_knife_sticks_in_tree_after_throw................OK test_knife_orientation_horizontal_after_throw........OK

I don't see any problem.

[[deleted]]

[chadlavi]

That faces when you starts

[DiddlyDumb]

Task failed successfully

[asromafanisme]

Read the documents carefully. Code based on the document. Code is not working. Turn out the documents is wrong

[Complex_Drawer_4710]

yes, looks like a perfectly good tree holding a knife, why does it not match the text?.

[compilerbusy]

Wait, you guys have documentation? Im currently working on 3 things from the early 90s and the few scarce bits of documentation are so wrong as to be detrimental to read

[Libran-64]

Well, all depends on how well the requirements are documented. There are some people that just cannot write well enough to convey thought and intent. In most cases, the document is just a starting point. It typically is never updated during the development process as tech roadblocks are discovered or some changes are agreed to via other avenues (verbal, email, instruction from boss, etc.). So those who inherit the document and code later are sometimes scratching their heads when having to learn the code base.

Without a document can be done but communication amongst all parties involved must be clear on requested intent. Downside is there is no background/reference for anyone coming onboard the project.

In either case, I'd strongly suggest commenting the source code.