tzaman

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

No big deal. :)

Honestly, the size doesn't matter.

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.

Must be cultural differences then - nobody around here (Central Europe) cares or asks about rings.

So what is the point of one?

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.

Why overcomplicate things? :)

Ok, I'll bite - enlighten us.

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.

Same here, doesn't instill much confidence for a hosting company to have their homepage down.

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.

Care to elaborate why? I'm somewhat of an apple-fanboy but Surface seems more and more appealing, and I'm leaning towards giving one a try.

Aj dident nou der vr sou meni Slavik pipol araunt dis plejs. Veri hepi tu si felou Slavs komentink on Hekr Njuz

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)

Thanks, I do in fact use AirBnB's config, just wondering whether there's anything I was missing.

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.

It appears Docker Hub is hosted on S3 as well, none of the official images can be pulled.

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.

Thank you!

Someone care to (briefly) elaborate what this is about for us not up to speed?

> 4: Raw SVG >= D3 for simple data visualisations

You can have a bit of both. D3 has a dependency "d3-scale" [0], which is a perfect choice if you'd like D3 to do the math and React to take care of the DOM.

0: https://medium.com/@mbostock/introducing-d3-scale-61980c5154...

I wasn't at first either, but benefits outweigh the risks (which are all security related).

It's something I'm willing to re-think if it turns out to be problematic on any level. But so far after half a year in production, we've seen no problems.

Actually, the problem is that Docker logs to stdout rather than to logfile(s)

> (We also went from paying $1k/mo to $0/mo, which is a very nice side effect)

That's not entirely true, because someone had to set Jenkins up and has to maintain it, but once things are rolling, it hardly needs any input.

Juenkins' Kubernetes plugin allows to mount secrets like with usual pods so we deploy test secrets just like we normally do production ones.

As for glusterfs, our Nginx reverse proxy also has a cron job that runs letsencrypt automatic renewal once a week so it needs to be able to write those new certificates. Because we need to be able to run several reverse proxies, all with write persmissions (we run one at a time, but on deployment, there are two running to avoid downtime) we chose gluster, as gce-pd doesn't support multiple writers.

Thanks for clarification - I'll definitely have a look :)

I'll definitely check it out - but the problem with many of these tools is a lack of "proper" Docker support, along with the ability to self host and debug. Thanks for the heads up!

Seeing how much people recommend other solutions, I've actually moved from Travis to Jenkins, and never looked back.

Yes, Jenkins has its issues (crappy UX, poor/awkward docs), but where it shines is the fact it's self-hosted, so I can SSH onto the instance to debug a failing build or replay it with a modified Jenkinsfile on the fly.

I'm quite proud of the current setup we have; We're hosting our app with Google's Container Engine (Kubernetes), so what we're doing is on every build Jenkins creates a slave agent within the same cluster (just different node pool) as the production, so the environment in which test containers are ran is identical to production, and what's more it actually talks to the same Kubernetes master, which means I can, for example, test our Nginx Reverse proxy with real backend endpoints and real certificates (that are mounted through glusterfs).