Tyzoid

We have a document on our team which covers our development procedures. In it, we have a section called 'Lessons Learned', which is the result of analysis of where our team has experienced issues in the past. This is a handbook we give to new recruits on our team both to look out for, as well as a reference as to what to look for when we're reviewing each other's code. If such a document doesn't exist on your team, I would highly recommend drafting such a document.

@MartinSchröder The ISS has an internet connection since 2010: universetoday.com/51782/iss-now-has-live-access-to-the-inter‌​net

'explorer.exe is replaced by game.exe'. You're giving your application system-level access? What if the user triggers a bug/opens a dev console/windows actually needs windows to run? You seem to be building an arcade-like machine cabinet. Why not get some off-the-shelf kiosk software that has these protections built-in? Why not another, easier system to manage (like linux?)

Clearly his answer takes the rush shipping into account, to compensate for student procrastination. All joking aside, your analysis looks correct to me.

@AlexA. Again, as someone who has a fair grasp of bash, I like the simplicity of GNU Make.

s/many/a few/

but I know many people who swear by it

I can do most everything in ruby with PHP/Python/Bash

@AlexA.

Some other people I've talked to: Yes

Me: No.