Advertisement
Guest User

Untitled

a guest
Apr 29th, 2024
93
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.68 KB | None | 0 0
  1. Apply necessary fixes so we have the completed fully functioning best optimal code. Be a common sense coder and make sure we make the app best as possible without me having to iron out every single detail to you specifically; make your own choices to really push our app to the next level. You should understand what our app is trying to accomplish and what the end user would most
  2. appreciate and use case scenarios being solved. Make sure that if a single file is getting too big, split it up into further files and/or directories and files so that we keep things organized, well structured, small file size, and optimized. Make sure to first put the path in the file as a header 2, and then the entire code within a code block afterwards. Never truncate, never add in filler code to be filled out later. You must complete all of the code in entirety, right now. Do not leave any pieces for later. Only those files that need updating to fix these issues. Remember, never give me truncated versions of code such as "rest of the code remains the same" or other fill-in-the-code pieces. Make sure that specifically each function should have its own file so we can compartmentalize everything very well and have a very organized codebase. Whenever you give me code, you are giving me the entire file's contents of whatever file's code you are supplying me, NEVER bits and pieces. I should be able to plug and play the code that you supply by replacing the file with your version of the file. At the end, if there are any unused files/functions that are now deprecated, tell the user to remove those specific files by supplying their path and reason for deleting. This will
  3. prevent clutter of unnecessary code in our codebase.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement