Setting things up for a new App
Unanswered
Silver posted this in #help-forum
SilverOP
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
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
9 Replies
@Silver 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
normally you fix your code errors first before your app is 'done'. So fix them and you are good for the review
@B33fb0n3 normally you fix your code errors first *before* your app is 'done'. So fix them and you are good for the review
SilverOP
👍🏼 Get It. But how do you approach the review once you get to that?
@Silver 👍🏼 Get It. But how do you approach the review once you get to that?
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)
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)
@B33fb0n3 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)
SilverOP
And what if you´re not a professional programmer. Would you contract someone for a Code Auditory to fix issues?
@Silver And what if you´re not a professional programmer. Would you contract someone for a Code Auditory to fix issues?
if I wouldn't be a professional programmer, I wouldn't build a 'new app'
SilverOP
Yeah, I can imagine there´s a lot of them nowadays
@Silver Yeah, I can imagine there´s a lot of them nowadays
might be. Lets get back to your initial question. Can you tell me what question is currently unanswered?
SilverOP
I think I get It