12.4 is out: CrossFit Games - Workout video demo with Graham Holmberg (by CrossFitHQ)
NASA
One Nice Bug Per Day

No title available

blake kathryn
🪼

Discoholic 🪩
AnasAbdin

❣ Chile in a Photography ❣
$LAYYYTER
taylor price

pixel skylines
Aqua Utopia|海の底で記憶を紡ぐ
noise dept.
Jules of Nature
Game of Thrones Daily

JBB: An Artblog!

No title available
dirt enthusiast

祝日 / Permanent Vacation

Origami Around
seen from Algeria
seen from United States

seen from China
seen from United States

seen from Malaysia

seen from Canada

seen from United Kingdom

seen from Italy
seen from United States
seen from United States
seen from United States

seen from China

seen from Poland

seen from United States

seen from United States

seen from Malaysia
seen from United States
seen from Germany

seen from Belgium

seen from Türkiye
@seags-blog
12.4 is out: CrossFit Games - Workout video demo with Graham Holmberg (by CrossFitHQ)
Getting into Git
A long time ago (a few months to be exact) we realised the hard way why it is so important to use version control. To those of my followers who don't know what version control is, it pretty much allows you to make changes, add features or fix bugs to your application but with ability to move between different versions and going back to your original code.
This would have been great when we made a nice big update, it broke, and we then had to scramble to get it to work again on a production site instead of rolling back to an older, working, version.
This is when my research into a version control system (VCS) began. It was an interesting learning curve and one that I got a lot of flack for simply because I was a well established web developer you didn't use a VCS. Yes guys, "what was I thinking?".
So we are running Git in our offices and have been for a little while now. Git is a VCS that has taken the development world by storm and has led to great services such as GitHub. Git allows us in the office to do the following:
Roll back on older versions if required.
Create almost a seperate application with something called branches when trying new features.
We push changes we have made and tested to the server (BACKUPS).
Then last something we are implementing is getting a dedicated line in to allow collaborators to push and pull code from anywhere.
So as much as I took the flaming I got about taking so long to get going I now ask myself the question, "WHAT WAS I THINK?".
The question is, what do people do about database changes? I see people talking about saving schema files and other people talking about version control. Any suggestions?
What a joke of a website, and what you call that ? Photography? Yeah sure
Where have I ever said that some are photography? Just because I share a photo doesn't make it a professional shot. Lastly, if you don't like it then you can simply not visit my site. Simple.
So excited to try this bad boy out! (Taken with instagram)
When the Skullcandys come out you know an extreme amount of work is going to be done. #boom (Taken with instagram)
New slops just in time for IPTs. #preparation #roadtoipt (Taken with instagram)
Make it happen and #nevergiveup (Taken with instagram)
Konka training grounds. We put them to good use. #roadtoipt (Taken with instagram)
Pulling into Konka yesterday morning. #RoadToIPT (Taken with instagram)
And then boom. My girl knows me :D (Taken with instagram)
Happiness. (Taken with instagram)
Dessert: Jam filled butter biscuits #valentinesday (Taken with instagram)
Dinner: chargrilled steak with beer mustard and watercress salad. #valentinesday (Taken with instagram)
Lunch for today. Not complaining. (Taken with instagram)
Old school Mini Clubman. Little gem of a car. (Taken with instagram)
Proof that the iPhone is the hottest thing out there! (Taken with instagram)
Trying not to give to much away here but boy am I glad to see this "randomness". (Taken with instagram)