One of the major worries that I've had when launching our marketplace was poaching; What if clients (the demand side) decide to hire developers (the supply side) outside of our platform? Of course, we had rules against that in terms of service, but hey, circumventing those is not a big risk.
But, luckily for us, the value that we provided to both parties (and still do) outweighed the risk of losing their accounts for violating TOS, so we very rarely see that.
Regarding chicken and egg problem, we manually found and pre-screened 10 people to provide supply in advance, so when the first client came, they'd have someone to hire. Earned $13 the third day after launch. Happiest day ever :)
Today we have 19 employees and are profitable (we've hit profitability the third year, we're now 7 years "old"). https://codeable.io
1. I push a hotfix to GitHub.
2. Jenkins (which is on Google Cloud) builds it, and it already has all the Docker steps cached from previous builds, so it's fast.
3. Jenkins pushes the image to Google Cloud repo, which is almost instantaneous
4. Kubernetes (also on Google Cloud) pulls the image and makes a new deployment
I was once in the camp of small Docker images, but realized it's simply not worth the tradeoff, since there's only one upside to them, and that upside is fast transfer of images.
However, that argument becomes pointless when using a proper CI/CD stack. As a developer, you don't normally upload images yourself, but push changes to GitHub, then Jenkins/Travis/whatever takes over, builds the image, and pushes it into production/staging/whatever. Since CD tool of choice is usually also on the cloud, we don't have to worry about image size, nor to any of the CD vendors charge for data transfer.
I'd rather have bigger images (I base mine off Debian now, used to be Alpine) and not have to worry with lack of ported tools and libraries, than vice-versa.
Out of curiosity, what's all the fuss with engagement rings in the first place? When me and my wife got engaged, I gave her nothing (nor did she expect anything), just asked her to marry me and she agreed, we kissed and that was it.
We did, however, made wedding rings, which together were about $1300, but that's because they were made out of gold.
Slightly sarcastic, but on point: Doctors say a glass of red wine per day is good for your blood. But now, they also say it'll increase chances of getting cancer. So I guess I need to choose between these two. Too much of anything is a poison.
A victim here. My 2007 MacBook Pro started to swell on the bottom after a couple of years, didn't think much of it, it was a tiny bump at first, but then it almost doubled in thickness so I replaced it with a cheap Chinese knockoff (was broke at the time due to starting a startup), and the same thing happened in about a year. Lesson learned.
I use N26 as my personal bank, and I must say it's pretty much instantaneous - when I pay contactless, I can hear my phone notification before I get to put the card back in the wallet. I've tested the card across Europe while traveling and the speed at which I get push notifications is consistently fast.
Does this mean that anyone who's using Segment to collect data on their customer and sends it to a warehouse like Google Big Query is more likely to have a problem because the data is "shared" with two third parties? (pardon my ignorance, not good with this stuff)
I've been always meaning to try this out but always just keep reusing the ESLint config, which is probably a bit out of date now. So the question is, could someone explain to me (and everyone who has these same thoughts) why is StandardJS worth a try?
One thing that's still missing but would be quite valuable is a good egress approach/configuration. For example, we use an external PostgreSQL provider in which I can configure access IPs. Since K8s nodes (on GKE) get different IPs, I have to be very loose with CIDR selection, which I don't like.
I have an employee from the US (I'm otherwise from Europe) and while visiting through the conversation/personal stories he explained the most interesting part of relationship between US authorities and citizens: You're less likely to be "harassed" if you lie to them, because they can turn pretty much anything you say against you and dig so deep to finally find an excuse to bully you, or charge you with something.
That is quite a sad state for the society to be in, being always afraid of the authorities, rather than knowing their primary goal is to protect and serve.
But, luckily for us, the value that we provided to both parties (and still do) outweighed the risk of losing their accounts for violating TOS, so we very rarely see that.
Regarding chicken and egg problem, we manually found and pre-screened 10 people to provide supply in advance, so when the first client came, they'd have someone to hire. Earned $13 the third day after launch. Happiest day ever :)
Today we have 19 employees and are profitable (we've hit profitability the third year, we're now 7 years "old"). https://codeable.io