3 ms·

Right, I agree with all this. The unit tests will help you with bugs by ensuring your program is doing what it should be doing. You shouldn't be worrying abou

by gexla 16y ago

Right, I agree with all this. The unit tests will help you with bugs by ensuring your program is doing what it should be doing. You shouldn't be worrying about automating your testing before you have even started writing unit tests. Don't try to automate things you don't yet know how to do. Figure out how to run it manually first. Staging isn't so important at this point. Staging is generally most useful when you are showing a working version of what you are building to a client (or anyone who might need to see it) while you are still in development. In this case, your code is always changing and you are regularly breaking things. If someone needs to look at what you are doing then you need a stable snapshot setup for them. This is especially important when you have multiple developers because you don't know what the other guy is doing. The end game is that your code has gone live and the "client" is your actual customers. This is where being able to push your code to a staging server is critical. You need to be able to "user test" it before going live.

Zeu5 16y ago
>Staging is generally most useful when you are showing a working version of what you are building to a client (or anyone who might need to see it) while you are still in development. Yes I do have 4 people to demo to. >This is especially important when you have multiple developers because you don't know what the other guy is doing. Yes I have 2 developers working independently. I hired them to increase the speed of development. Plus myself, that is 3 people working on different parts. so my question is how do i get someone to help me? or point me to the right resources? I am getting the feeling that i am being perceived as someone enamored with a buzzword and ignoring basics. I am also getting the feeling that the term continuous deployment is perceived as a gigantic ball of multiple scripts and processes for deployment, only suited for projects of a certain size. I am going to state the following unspoken assumptions of mine. My bad that I unknowingly assumed that other readers believe in the same assumptions. Hope this will help the discussion. From a web application perspective, my assumptions are a) continuous deployment/integration means able to (as much as possible) automate the process of deployment of the code on a server preferably one where the configuration is identical to the production server. regardless how much the code is completed. b) continuous deployment/integration means able to (as much as possible) automate the process of testing the deployed code against unit tests or functional tests therefore allowing developers to add new features or re-factor existing code without fear of integration risks. Again, I would like to seek help to automate (as much as possible) the process of deployment. I already have Capistrano working but to a production environment. I am not looking to hire from HN readers, though I do not rule that out. at the very least point me to good places to look for such people. Like a stranger in another country, I need directions. Either take me where I want to go, or tell me where I can ask for better directions. I hope that analogy works to express what I am asking for. Thank you very much to all feedback so far.

by gexla 16y ago

Zeu5 16y ago

>Staging is generally most useful when you are showing a working version of what you are building to a client (or anyone who might need to see it) while you are still in development. Yes I do have 4 people to demo to. >This is especially important when you have multiple developers because you don't know what the other guy is doing. Yes I have 2 developers working independently. I hired them to increase the speed of development. Plus myself, that is 3 people working on different parts. so my question is how do i get someone to help me? or point me to the right resources? I am getting the feeling that i am being perceived as someone enamored with a buzzword and ignoring basics. I am also getting the feeling that the term continuous deployment is perceived as a gigantic ball of multiple scripts and processes for deployment, only suited for projects of a certain size. I am going to state the following unspoken assumptions of mine. My bad that I unknowingly assumed that other readers believe in the same assumptions. Hope this will help the discussion. From a web application perspective, my assumptions are a) continuous deployment/integration means able to (as much as possible) automate the process of deployment of the code on a server preferably one where the configuration is identical to the production server. regardless how much the code is completed. b) continuous deployment/integration means able to (as much as possible) automate the process of testing the deployed code against unit tests or functional tests therefore allowing developers to add new features or re-factor existing code without fear of integration risks. Again, I would like to seek help to automate (as much as possible) the process of deployment. I already have Capistrano working but to a production environment. I am not looking to hire from HN readers, though I do not rule that out. at the very least point me to good places to look for such people. Like a stranger in another country, I need directions. Either take me where I want to go, or tell me where I can ask for better directions. I hope that analogy works to express what I am asking for. Thank you very much to all feedback so far.