{"id":1648,"date":"2021-07-28T09:15:46","date_gmt":"2021-07-28T09:15:46","guid":{"rendered":"https:\/\/www.patricioland.com\/?p=1648"},"modified":"2021-08-24T14:55:58","modified_gmt":"2021-08-24T14:55:58","slug":"gdd730-week-5","status":"publish","type":"post","link":"https:\/\/www.patricioland.com\/?p=1648","title":{"rendered":"GDD730 Week 5"},"content":{"rendered":"

\"\"Taking advantage of this week’s rubric, normalisation of tasks, I think it is appropriate to talk about how Phil and I approached the coding management of the prototype.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

<\/p>\n

After having decided to make the whole development with Unity<\/strong>, I did not think it convenient to insist on the possibility of using visual programming as I did before using Playmaker during GDD710.<\/a> It is not the right moment to overload my partner\u2019s work and make him worried about investing extra time learning how to use Game Maker Studio 2<\/strong>. So I had to dust off my C Sharp<\/strong> notes, and in just a few days, I made up for the pleasure by programming in the traditional way.
\nI was aware of the fact that this procedure would be shared by two persons at least. Fortunately, Phil<\/strong> is very organized and clear, which helped me understand his code without major difficulties and I tried to do the same. Even more: w<\/span>ithout realizing it, both of us were carrying out our research by using the same tutorials and technical guides, which was a great relief. We both agreed on the use of Visual Studio<\/strong><\/a> as integrated development environment editor.<\/p>\n

Clean code and norming<\/span><\/h1>\n
\n
\n
\n

A major misunderstanding is to confuse clean code with something that can be called \u201cbeautiful code.\u201d Clean code has no beauty reasons. Professional programmers are not paid for writing beautiful or pretty code. They are hired by development companies as experts to create customer value. (Roth 2017)<\/strong><\/p><\/blockquote>\n