Setting things up for a new App

[zinc viper]

Hey folks.
Let me ask you. Once you are getting your app done, but there might be some code errors wich request review. How do you proceed with that?
Regards

[upbeat pagoda]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[gusty wraith]

normally you fix your code errors first before your app is 'done'. So fix them and you are good for the review

[zinc viper]

👍🏼 Get It. But how do you approach the review once you get to that?

[gusty wraith]

the review itself is very much scoped to my specific code. I normally push it to git and check my own commits outside of my IDE. Like that I get a different view on it. When I check through the files and treat the code like if someone else wrote it and be like that very harsh. That works good and I find issues like that.

If someone else does the review for your code, then check his comments and either change code or defend your code + explain why you doing things (maybe also by adding a comment upfront when doing uncommon things)

[zinc viper]

And what if you´re not a professional programmer. Would you contract someone for a Code Auditory to fix issues?

[gusty wraith]

if I wouldn't be a professional programmer, I wouldn't build a 'new app'

[zinc viper]

Yeah, I can imagine there´s a lot of them nowadays

[gusty wraith]

might be. Lets get back to your initial question. Can you tell me what question is currently unanswered?

[zinc viper]

I think I get It