It's not about knowing when because, as you say, it's difficult to predict... Still preparing or defending your assets for the possibility would be wise.
2,370 karma · joined November 21, 2011
In 15 years jobsites will be run by machine operators remotely from (lower wage area?) control centers.
When everything is moved offshore to lower costs, what will we do all day?
With the 2019 refresh I thought they might do that as a compromise.
We could have all had whatever keys we want. Revolutionary. Instead, nope.
In regards to full time, we do both. Typically we start small and build up to ensure we are both happy with the initial work and can work well together. Once a client is ready to commit to one more more full time developers, we go month to month and the only issue would be scheduling the start time. If a developer was shared with another client/project part time, we would want him/her to finish up that commitment before pulling them off.
I don't think the base country will make too much difference. The biggest issues I had (that would not have occurred in the US) were with cultural barriers.
No matter the country, language can mostly be addressed with the right process and managers, but the attention and service that US customers expect is not something culturally that exists in many other places.
Getting that right, so that my team leads and PMs meet customer expectations was the hard part. I think that is where many offshore projects fail.
If your team is committed to delivering quality, and you, as the end client know how to communicate your needs and check the deliverables, things usually progress very well.
If your offshore team doesn't understand or care about this (many just don't get it, because customer service is NOT a thing in most countries outside of North America and Western Europe) then you will have frustration no matter where you go.
My clients are about 75% US based and I would be happy to talk with you directly if you have more questions or want to discuss a project. Reach out to me here: ethan [at] abovebits [dotcom]
2) Should be free when used in non-commercial applications. Multiple servers included.
3) Keep the common and already available typical configurations free: lamp, lemp, python, letsencrypt, email. Charge for things which no other panel free or otherwise typically supports. lightspeed, go, caddy, load balancing, sql replication, graphql, etc. Thats value.
I find water.css to be the prettiest of the classless bunch.
Have been using this for years and years and finally published to GitHub a couple of years ago.
I wonder what results in these dissimilar approaches? Are these cultural? are these youthful company versus decades-old bureaucracy?
However, when I need to do something like this I simply use this Chrome extension: https://chrome.google.com/webstore/detail/url-slideshow/pdbl...
"Also another funny thing, I don't know if I should say this or not... Not cause it's like lascivious or something, but because it's going to screw me on the next mystery movie that I write, but forget it, I'll say it. It's very interesting.
Apple... they let you use iPhones in movies but -- and this is very pivotal if you're ever watching a mystery movie - bad guys cannot have iPhones on camera.
So oh nooooooo, every single filmmaker that has a bad guy in their movie that's supposed to be a secret wants to murder me right now."