473 karma · joined March 14, 2011
Lyft is hiring Infrastructure Engineers and Managers. If you love Kubernetes, Terraform, Cloud Infrastructure, Kernels and Networking, or if you love accelerating development of a large and diverse engineering organization, drop me a line at yramin@lyft.com or @theatrus on Twitter.
Lyft’s Infrastructure engineers are responsible for building the systems and tools that make our teams productive and the technology stack that powers the applications our customers use every day. We believe standing up a healthy service should be fast, standardized, and intuitive. We can run Lyft on our laptops on the first day. We can ship code to our customers continuously. We’re empowered to use tools and technologies that provide the Lyft community with the best possible experience.
I'm specifically looking for candidates who love monitoring, logging, aggregation, time series databases, or similar large scale systems for the Observability team at Lyft. We process billions of events per second all to show how Lyft is working in real time, helping engineers at Lyft debug and build world class services and applications.
The provisioning team is responsible for the systems which mange our core operating system, scale-outs, and container based development environment. You'll be responsible for managing Docker, images, and cloud provisioning environments using a mix of open source and in-house technology.
The core datastores team is looking for experts in traditional and cloud databases as well as caching systems.
Feel free to reach out to me at yramin@lyft.com or at @theatrus on Twitter if you have any questions!
Grumpy likely doesn't support the C extensions due to time, and complexity of having to actually emulate the GIL since Python does not have fine grained locking for structures. C extensions that work with Python data structures need to first hold the GIL.
The probably made some, but it takes money to turn any component inventory they may have into shippable products. They probably burned all of the money on mechanical tooling and part procurement already, and maybe hit a major issue in doing so (critical component is suddenly a very different price, etc). All of that inventory either is returned (if possible) or ends up liquidated on the secondary electronics component market for pennies on the dollar, to pay back the creditors. Custom parts, tools, etc have less of a resale market, but I'm sure a company in China will be happy to pick them up cheap to make smartwatches for the local market.
Safety is of course a huge component. 48V is about the limit before special isolation and insulation is required.
Pantone colors are such a system, with very exact control over what you get.
Munching on wood with an Epilog laser will produce copious volumes of smoke, and the air assist and 400CFM blower are not trivial pieces of equipment to embed in a unit to properly quell any fires and actually extract all the air needed.
You're looking at a very very large fiber / YAG laser to cut it. A low power YAG laser can engrave steel - commercially these start at about $30k
My team is Observability at Twitter; we work on monitoring and we’re looking for distributed systems engineers and full-stack engineers. We are one of the largest monitoring stacks in the industry, writing up to 15 million metrics per second for all production services at Twitter. We also have a front-end service that is used every day by most engineers at Twitter. We write our services in Scala, use a state-of-art Cassandra-like database called Manhattan, and if you join, you’ll get to work on challenging problems from day one.
Here are some of the things we’ve done in the past 12 months:
- Made our alerting execution service seamlessly fail over across datacenters
- Implemented a temporal set membership service for our database to keep track of metric groupings
- Added tiering policies for metrics based on their automatically-derived significance
- Added hybrid online/offline processing of data for different use cases
- Optimized the time-series query language to make reads more efficient
- Made an asynchronous query processor to support expensive queries with lower latency requirements
- Wrote a client-side agent that collects and reports metrics to the storage system
Our team is 12 people, including back-end, front-end, full-stack and reliability engineers. You can find out more by reading last year’s article here: https://blog.twitter.com/2013/observability-at-twitter. More formal list of requirements for the position is here: https://about.twitter.com/careers/positions?jvi=oO0WXfwr,Job.
Engineers from foreign countries, H-1B initiations and transfers are welcome. You can reach out to me directly at yann@twitter.com.
As for the cooling off period, I'm not sure. Perhaps you can get the contents back, but it may be cost prohibitive.
Bolting to the floor/wall is a must.
I don't think the HDMI hardware is new enough in the 2012 for HDMI, though in theory display port might work if the drivers get enabled for it.