All the more reason to host your own instance! However, I understand if others prefer not to go this route and thus use an alternative version control solution.
358 karma · joined July 24, 2011
In other professional experiences, hosting our own instances of Gitlab was a great solution. Setup/updates were easy and we had the piece of mind knowing that we were in control of the maintaining uptime. I was very impressed by how simple it was to their implement CI service as well.
haha thanks for the laugh!
I started a company (shameless plug: fifthsignal.com) that makes software to fix a lot of the inefficiencies we saw. One of our biggest concerns was whether or not other carriers operated as poorly as what we had experienced. After talking with several carriers outside of the US, it would seem that most are actually worse off.
I believe someone in this thread made a comment towards the "legacy" telco space. Based on my experience, I would say it's a "dinosaur" industry that has seen very little delivered innovation in recent times.
*Most of my experience relates to operations/OSS solutions, with very little insight into telco BSS space.
We investigated a lot of other options (go & python specifically) when building new projects, but found that perl was the best solution. It's flexibility allowed us to develop a custom and durable solution that surpassed our expectations.
We ran into some environment/portability issues and resorted to using docker, carton, and gitlab CI to solve these problems. It is incredible how reliable and easy it became to modify and deploy code to a variety of systems (new or old).
I have two close friends (husband and wife) who spent the last 6 years teaching English in Thailand and Bali. In Thailand they taught at a private learning school and in Bali they taught at a school where the wealthier families sent their children.
Per the larger discussion: While there, they lived on one of their salaries and saved the other. I think they left with $15k and returned with roughly double that. I know during there time over there, they took off around a year and half total to travel and relax. They didn't live in glamorous places and eat at fancy restaurants. Instead they lived more like the locals to some extent, but this mentality/lifestyle allowed them to stay longer and ultimately come back home in a better place than when they left.
My wife and I visited them in Bali for four months last year (I am a remote software engineer). By association we adopted their lifestyle and had a fantastic/extremely affordable extended traveling experience.
For those learning, make sure you look into removing unused images and containers otherwise you might run into some issues a little farther down the road (eventually our builds started failing).
You can run docker rm and docker rmi to remove specific containers and images respectively, but we also found passing the --rm flag with docker run helped a lot as it removes a container after it exits.
Happy learning!
Stack: PHP, Mysql, JS, jQuery, Ajax, HTML, CSS
Contact: nick@12perks.com
I am looking to join a team that is passionate about what they're working on. I've worked for startups and contracted for international corporations for the past three years. I love engineering solutions with technology and am always expanding my stack knowledge. I enjoy engineering front-end and back-end aspects of applications. I have no problem working remotely, but would consider relocation if necessary.
It's a good old boys network that seems like they will resist change until their failure far before they'd ever consider transitioning to something that isn't, "just the way it is".
If you make it this way, please contact me, I'd love to help!
I'll send over a copy as well, I'd be curious to get your opinion!
It's $10, shoot me an email if you'd be interested in a copy or have any questions!
Good luck on your journey as well!