websites are made from computer files that contain code. code is just a bunch of instructions that are written in a language that the computer can understand.
for the websites that you visit on the internet, the code instructions are being read by a computer far away, and that computer thinks about the instructions and puts together (the website) and sends the finished website to your computer over the internet wires for you to look at.
there isn't just one copy of the website code, sometimes many different people work on the same website code at the same time. for this we create a special place to keep our code where everyone can share it, sort of like the junk drawer in the kitchen.
the people who write the code write it on their own computers, usually laptop computers that they can take anywhere with them. so that everyone can work on the code wherever they are, they each make a special copy of the (junk drawer) on their laptops. when they are done making changes to the code and want everyone else to see their changes, the push their changes back to the (junk drawer).
with more than one person making changes at the same time, you might think that my changes and your changes and her changes and his changes might not work well together. if we all push our changes together and then update the code on the website computer (without checking what happened when we put all those changes together), things might look all messed up and broken.
that’s why we make tests for our code - tests are another set of instructions saying what we want the code to do. if it was the junk drawer, my test might say ‘when i push the button on the flashlight, i expect the flashlight to produce a bright light’ if this test passes, we know this code is good (or at least does what we wanted it to do)
this is important because someone else’s new code might say ‘take the batteries out of the flashlight’ oops - their code did something that broke my code! good thing we wrote those tests. (we did write those tests, didn’t we?)
we need another special computer that is constantly watching for these changes and running these tests every time someone makes a change. that way, we know immediately if the code we wrote broke the code that someone else wrote.
if all the tests pass after someone makes a change, we should be good to push that new version of the website to the website computer so that you see the updates that we made.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
websites are made from computer files that contain code. code is just a bunch of instructions that are written in a language that the computer can understand.
for the websites that you visit on the internet, the code instructions are being read by a computer far away, and that computer thinks about the instructions and puts together (the website) and sends the finished website to your computer over the internet wires for you to look at.
there isn't just one copy of the website code, sometimes many different people work on the same website code at the same time. for this we create a special place to keep our code where everyone can share it, sort of like the junk drawer in the kitchen.
the people who write the code write it on their own computers, usually laptop computers that they can take anywhere with them. so that everyone can work on the code wherever they are, they each make a special copy of the (junk drawer) on their laptops. when they are done making changes to the code and want everyone else to see their changes, the push their changes back to the (junk drawer).
with more than one person making changes at the same time, you might think that my changes and your changes and her changes and his changes might not work well together. if we all push our changes together and then update the code on the website computer (without checking what happened when we put all those changes together), things might look all messed up and broken.
that’s why we make tests for our code - tests are another set of instructions saying what we want the code to do. if it was the junk drawer, my test might say ‘when i push the button on the flashlight, i expect the flashlight to produce a bright light’ if this test passes, we know this code is good (or at least does what we wanted it to do)
this is important because someone else’s new code might say ‘take the batteries out of the flashlight’ oops - their code did something that broke my code! good thing we wrote those tests. (we did write those tests, didn’t we?)
we need another special computer that is constantly watching for these changes and running these tests every time someone makes a change. that way, we know immediately if the code we wrote broke the code that someone else wrote.
if all the tests pass after someone makes a change, we should be good to push that new version of the website to the website computer so that you see the updates that we made.