"how do you make sure your full time employees don't mess up the codebase?" "we just sort of cross our fingers and pray" "that works just as well for interns!"
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We use git, but it doesn't suit many of our partners. Would you mind taking out some time to look into our operations?
-
You have a codebase that multiple people work on. Use version control. Your operations have nothing to do with that.
-
Our partners usually don't have a technical team - they outsource their tech work to our students. For example, a dentist who wants an iPad app for interactive demos for his patients. Now how do we ensure quality without going through code for each and every commit?
-
You don't. Overall code quality is the sum of code quality of every commit. Also, it begs the question if code quality is that important in this scenario. Is it? If yes, why?
-
It is important because the objective is to develop practical and productive skills in students. Doesn't need to be perfect, but needs to be good enough to get them hired once they finish the program.
-
They can be practical and productive without giving a shit about code quality, though. Will future employers judge the products built, the lessons learned by building or the code quality?
End of conversation
New conversation -
-
-
And do proper code review
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.