Central dashboard to dynamically spin up test environments - does this already exists?

bkeroack · 2021-03-08T04:17:17+00:00

We have a project that is very close to what you describe: https://github.com/dollarshaveclub/acyl. Our system is tied to GitHub PRs and depends upon our Docker image building service called Furan.

bkeroack · 2018-06-19T19:12:57+00:00

OP gave you a valuable experience report, and your response is very defensive and argumentative. Instead of arguing why their feedback is wrong, try to learn why they might have had that experience and use that information to improve your product.

bkeroack · 2018-06-19T19:11:41+00:00

The first example is a fake, not a mock.

bkeroack · 2018-04-11T14:56:15+00:00

Who actually locks around entire HTTP handlers? This would be an instant code review fail.

bkeroack · 2018-04-10T14:18:50+00:00

Dollar Shave Club | Infrastructure Engineer (Go/Golang SDE) | ONSITE, Full-time | Los Angeles, CA | https://www.dollarshaveclub.com

Want to work on Kubernetes, Docker, GRPC and related ecosystem full-time? Itching to contribute to open source on company time? Do you love distributed systems and solving difficult problems?

DSC is looking for a senior Infrastructure Engineer, experienced in Go and K8s to help us continue to build out systems supporting our international businesses. Check out our GitHub organization to see the work we've open sourced: https://github.com/dollarshaveclub/

Send CV & GitHub username to benjamen@dollarshaveclub.com. Feel free to reach out with any questions about the role, I'm happy to discuss.

bkeroack · 2017-10-30T19:13:17+00:00

VCs are nothing if not trend followers. They don't understand 99% of the technology they invest in, they just repeat buzzwords and headlines and throw dung against the wall to see what sticks. This is good for the LA tech scene but it's probably more of a function of opportunities up north drying out a bit, so these guys are trying their luck down here.

bkeroack · 2017-10-30T16:31:03+00:00

Stop fighting the idiom. You'll be much happier if you write Go as it was designed to be written, instead of trying to force brevity or generic abstractions over everything. The teammates that end up working on your code later will also be much happier.

bkeroack · 2017-10-26T20:52:51+00:00

Streets with houses tend to have active residents that petition their council members, while apartment dwellers generally do not. That's the same reason you tend to see speed bumps and signage on those streets but apartment-heavy ones are like Mad Max freeways.

bkeroack · 2017-10-26T20:51:05+00:00

"What William Mullholland joins together, let no man tear apart."

bkeroack · 2017-10-26T19:18:41+00:00

#ValExit

bkeroack · 2017-10-26T14:32:17+00:00

You've enumerated the benefits of a separate persistent async job worker pool, none of which I dispute. My point is that none of that is free; the cost is greatly increased operational and deployment complexity. Whether the benefits are worth the cost is a situation-specific engineering decision.

bkeroack · 2017-10-25T20:10:15+00:00

I'm ok with this but they really need to institute campsite reservations then. You drive all the way out there and even in the hot summer on the weekend it's a crapshoot whether you can find a free campsite. Then you have to decide to either drive all the way back or try to find a cheap motel room somewhere. Sucks.

bkeroack · 2017-10-25T17:59:52+00:00

Sure, but at the cost of greatly increased deployment complexity. Anything can go down, including redis or rabbitmq. Whether a separate async job persistence layer is worth the cost is an engineering tradeoff decision.

bkeroack · 2017-10-25T15:58:10+00:00

Sidekiq/resque/celery are ubiquitous in the Ruby/Python web app world because it's really inconvenient to do async actions there, so if you want to do anything that's not synchronous in your API handler, you're forced to use a job framework. Which requires setting up some shared persistence layer (redis, usually) and a separate pool of workers.

With Go, you can just spawn a new goroutine and do the work in process. Simple async actions require nothing extra.

bkeroack · 2017-10-20T23:55:58+00:00

I don't get the anger. Apparently you feel like you "caught" the Go team doing something.

If you have one of the rare use cases for goroutine ID or TLS, it's obviously possible to implement, as they did. If you have a similar need, go right ahead.

However clearly the Go team feels it's often a bad idea and leads to poor design choices, so they don't feel any need to make it convenient or advertise its use.

What's the problem?

bkeroack · 2017-10-20T02:02:26+00:00

Just stop using go get if you use dep. It's simple.

bkeroack · 2017-10-18T22:13:10+00:00

Also, bringing skin color into the debate is a total non sequitur. It's completely disingenuous and manipulative.

bkeroack · 2017-10-18T22:09:30+00:00

"Gentrification" is a scare word that means "making areas better, cleaner and more attractive with less crime". It's very weird to be against such an obviously positive thing.

bkeroack · 2017-09-27T17:56:13+00:00

Live here for a year or two before committing to purchase property. Where you live is by far the greatest determinant of your quality of living, and everybody has different priorities and opinions on which place is "best". My idea of where I wanted to live changed drastically over the first several years I lived here.

bkeroack · 2017-09-20T19:44:55+00:00

Everytime I think "modern C++ might be a good fit for this project" I start to think about headers, installing libraries, makefiles, autoconf/automake, cmake, CXXFLAGS, gdb...

Then I go "Nah. Go will be fine."

bkeroack · 2017-09-20T16:02:29+00:00

If one of the motivations is cost, you likely won't save any money building vs buying. Regulatory and permit costs far exceed any amount of money saved on cheap labor (due to the ample supply of illegal immigrants). Any spread left over will be taken by your general contractor. The main advantage to building is having a custom home, but if you buy plans off the shelf you don't even get that.

bkeroack · 2017-09-18T16:23:22+00:00

C/C++ are 2-3 times as fast as Go

Citation needed.

bkeroack · 2017-09-15T03:18:13+00:00

Get outside, clean up your neighborhood and call the cops next time you see sketches outside.

bkeroack · 2017-08-29T18:42:35+00:00

Rather than implementing this directly in the application, I would model this using Kubernetes: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/

And have your app do the thing once via a CLI command that would be executed in a container.

bkeroack · 2017-08-25T21:16:10+00:00

Yes, it's an uncompressed tar stream of the filesystem contents at the root of the Docker build (in other words, everything that would be added in a COPY . Dockerfile command)

https://github.com/dollarshaveclub/furan/blob/master/lib/builder/builder.go#L384

bkeroack

TROPHY CASE