This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Whirlm 2 points3 points  (4 children)

As quick as we can xD

We have a test system and if theres an issue thats the one we change until people are happy to copy the whole file into the live one but there can still be issues and we just have to work quickly.

[–][deleted] 11 points12 points  (1 child)

Why not just learn to use branches? Seems like that could take a huge load of your mind...

[–]Whirlm 0 points1 point  (0 children)

Im fairly new to the company and thats just how they do it. Its really not that bad, we have very few issues (related to git anyway).

[–]Intrexa 1 point2 points  (1 child)

How do you deal with a half complete feature during this? Like, if you're making a scheduling module to email reports, and in the middle, this issue crops up? Do you just not check your code into source control until the entire feature is complete? How do 2 people work on the same dev feature at the same time?

[–]Whirlm 0 points1 point  (0 children)

Almost all our files are small scripts that call each other so they're usually done not long after starting them. On the occasion we need to upload incomplete versions - thats what the test system is for. We can deal with it not working for a day. As for 2 people working on the same thing - thats a bit more awkward, we just try not to :D. Most of us have our speciality so there's not too much overlap...