https://blog.jiya.net/enContents © 2023 <a href="mailto:me@jiya.net">Aaron Ji</a> Mon, 18 Dec 2023 05:37:13 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.jiya.net/posts/2023/12/code-tag.htmlAaron Ji<ul class="org-ul"> <li>TODO</li> </ul> <p> Use TODO to note missing features or functionality that should be added at a later date. </p> <ul class="org-ul"> <li><p> FIXME </p> <p> Use FIXME to note broken code that needs to be fixed. </p></li> <li>OPTIMIZE</li> </ul> <p> Use OPTIMIZE to note slow or inefficient code that may cause performance problems. </p> <ul class="org-ul"> <li>HACK</li> </ul> <p> Use HACK to note code smells where questionable coding practices were used and should be refactored away. </p> <ul class="org-ul"> <li>REVIEW</li> </ul> <p> Use REVIEW to note anything that should be looked at to confirm it is working as intended. </p> <p> One advantage of using these tags is that they are easy to search for and give an understanding of where the code can be improved. </p> <p> reference: <a href="https://gist.github.com/brun0xff/755438491898e8b12999f9492e537e53">https://gist.github.com/brun0xff/755438491898e8b12999f9492e537e53</a> </p>technologyhttps://blog.jiya.net/posts/2023/12/code-tag.htmlMon, 18 Dec 2023 05:30:00 GMT