Note that good companies clearly spell out the CA legal section which covers this. Bad ones try to hide it.
473 karma · joined March 14, 2011
Note that good companies clearly spell out the CA legal section which covers this. Bad ones try to hide it.
Personally, I've never encountered this issue and I rebase frequently.
Other structures such as CRDTs/lattices might be more appropriate for your use case.
Compile times are not a reason to move to a service oriented architecture.
While well beyond the scrappy startup phase, we are looking for a broad range of skills, from front end, mobile, operations, SRE, and backend positions.
See the job postings at https://twitter.com/jobs and feel free to e-mail me at yann@[company].com
As for bridging Twitter Future with (now) Scala Future, that should be coming soon, once the execution context stuff is squared away.
If you wanted to record and forward traces inside your own services, this is relatively straightforward (though not super trivial) to do. There are other implementations beyond the Finagle one in development by the community - I would suggest hopping on to the zipkin-users Google Group.
This isn't a unique problem, but using consistent libraries goes a long way (which works well internally at Twitter).
Note that the bus system is essentially classed, since only the old, non-airconditioned, slow buses are free (and you can pay for better transit options).
You're out $1-2k on the ticket, but paying a tiny fraction for great healthcare.
You just can't sue anyone later (but that is maybe a good thing).