91–100 of 224 posts
I want Oxide to do so well. The product is a breath of fresh air in the era of cloud providers. As an engineer, I'd kill to get to work with their hardware. Not to mention that working at Oxide sounds like a modern Sun Microsystems with the ideology that team has. Highly recommend their podcast "Oxide and Friends", and their original "On The Metal" show. I've attempted to apply to their company multiple times over th…
Earlier quoted context omitted.
I understand that all employees have equal salary pay (apart from sales people who can earn more and are valued higher). Do all have equal equity and voting rights, at least within common stock? And since transparency is a core value and principle, will you commit to sharing your cap table publicly?
I appreciate that our approach to compensation leaves some with overwhelming feelings of whataboutery, but no, we (of course?) do not have equal equity: as we have said (several times?) equity broadly compensates for risk -- and risk has gone down over time. (I used to tell people to "value the equity at zero"; I don't say that any longer because it plainly isn't.) In terms of the cap table: that's a bit of an odd re…
This design feels very obvious-in-hindsight . Consolidate power adapters and networking, replace cabling with pluggable slots. It's something similar to what IBM mainframes or Sun cabinets could've looked like. Somehow hardware giants like Dell, HP, SuperMicro, etc didn't make a product like this, even at their peak in 2000s or during cloud boom in 2010s. I wonder why? Beautiful machine, and fun to see Illumos heart…
Somehow everyone wrote to me about baldes. These are not the same, though. Blade servers were mounded into units of 4u, 8u, etc, they occupied a portion of the overall cabinet and still had to do "plumbing" for power and networking behind the chassis to the rest of the cabinet or to the rest of the datacenter. A full-cabinet blade rig would have multiple 8u blade units and some off the shelf units for networking, storage, etc. Yes, you could mix and match different components based on your needs, but that also meant that there were extra wires, cables, mounting rails, and more importantly - all these different components ran a mix of software that had to integrate using common denominator protocols and speeds.
Steve rightly mentioned the integration below, and I didn't put it in my message because I kinda assumed that we include software in this discussion too.
HP in 2005 had an army of programmers writing all sorts of firmware and software and another army of hardware engineers, too. They could have made an Oxide computer back then, and it would sell really well. But they didn't, and none of their competitors did despite this being an obvious product (in hindsight), an THIS is what I find interesting.
Earlier quoted context omitted.
I appreciate that our approach to compensation leaves some with overwhelming feelings of whataboutery, but no, we (of course?) do not have equal equity: as we have said (several times?) equity broadly compensates for risk -- and risk has gone down over time. (I used to tell people to "value the equity at zero"; I don't say that any longer because it plainly isn't.) In terms of the cap table: that's a bit of an odd re…
[flagged]
You’re not getting across a reasonable point here. Maybe take a step back and think about what you really want to say.
Clearly something is landing wrong, but exactly what is not being well communicated.
I want Oxide to do so well. The product is a breath of fresh air in the era of cloud providers. As an engineer, I'd kill to get to work with their hardware. Not to mention that working at Oxide sounds like a modern Sun Microsystems with the ideology that team has. Highly recommend their podcast "Oxide and Friends", and their original "On The Metal" show. I've attempted to apply to their company multiple times over th…
[flagged]
Earlier quoted context omitted.
Just a gentle reminder that a company may portray itself as cool to customers, but is not cool to their own current or future employees. Their interview process was shady. There was a post here about 1-2 years ago that was a link to their interview process and how open and transparent they were. The post itself was from an employee and a fellow commenter who was gaslighting folks was also an employee. Several folks c…
I'm seeing the phrases "tremendous amount of homework", "substantial amount", and "few hours". Does anyone have an actual estimated time we can discuss?
It's a fair bit of writing to ask for, but for a mostly remote and prose-driven company, you do a lot of long-form writing in the day to day work. The public RFDs and github issues/comments/commits give a good flavor for this.
As others have said, lots of my work is open source, and I have public writings and talks, so finding those were much easier for me than it might be for someone with only closed source works.
I want Oxide to do so well. The product is a breath of fresh air in the era of cloud providers. As an engineer, I'd kill to get to work with their hardware. Not to mention that working at Oxide sounds like a modern Sun Microsystems with the ideology that team has. Highly recommend their podcast "Oxide and Friends", and their original "On The Metal" show. I've attempted to apply to their company multiple times over th…
There are two companies that I want want to work for. Oxide is one of them. Many places I'm still willing to work for, but in a more neutral way. They're just mostly not hiring for my role/location as far as I can tell, so it is what it is.
This design feels very obvious-in-hindsight . Consolidate power adapters and networking, replace cabling with pluggable slots. It's something similar to what IBM mainframes or Sun cabinets could've looked like. Somehow hardware giants like Dell, HP, SuperMicro, etc didn't make a product like this, even at their peak in 2000s or during cloud boom in 2010s. I wonder why? Beautiful machine, and fun to see Illumos heart…
I wish I could edit my post. Somehow everyone wrote to me about baldes. These are not the same, though. Blade servers were mounded into units of 4u, 8u, etc, they occupied a portion of the overall cabinet and still had to do "plumbing" for power and networking behind the chassis to the rest of the cabinet or to the rest of the datacenter. A full-cabinet blade rig would have multiple 8u blade units and some off the sh…
That's what's so cool about Oxide's boxes to me-- the legacy garbage is gone and the strange undefined behavior part and parcel with overlapping edge cases will be minimized (and managed, as opposed to used as an excuse by a vendor). Dealing with incompatibilities and strange firmware interactions have made me come to see PC-based servers as a weird opposite of the "Swiss cheese" model. The various layers of interacting hardware, firmware, drivers, and OS act as a kind of "filter" for correct operation. When you swap or add one of these component you get one or more exciting new layers in the stack that, hopefully, have "holes" aligning with the existing.
Earlier quoted context omitted.
> Somehow hardware giants like Dell, HP, SuperMicro, etc didn't make a product like this, Dell and HP both have "blades" that plugged into a blade-chassis. The chassis had all the lights out mgmt as well as power/networking integrated so the blade was basically a metal box with compute/memory/storage and it just slid in to the dock. I am sure that supermico had something like this as well
Blades basically died out is the thing - AFAIK no one really wanted them and honestly the same is a risk for what Oxide is doing too. Blades have the basic issue of "how often do you want an unpopulated chassis?" - answer, never. So really they're solving for replacing a failed piece of hardware. But how often do you need to do that, what's it worth to you? If it makes sense then the statistical window where it does…
Loved the idea of blade servers, but they were targeted to people who needed very high compute in small footprints, and we both didn't have high compute requirements and were power/footprint constrained (we could get more power but cost/watt would go up because of cooling density).
The Twin^2 was nice because it amortized the cost of redundant power supplies over 4 machines, but didn't have the cost overhead of big backplanes or fancy layouts to get a lot of CPU+RAM in a small physical space.
Once populated a 4 node chassis was around $750/node including CPU and RAM and 2x SATA drives, it was within $100 of the price of a similar 1U server. We had around 10 cabinets in a data center when I left the company. It was, IMHO, a pretty good deal to get a dedicated box with 24x7 monitoring and sysadmin services including updates and backups at $150/mo.
I want Oxide to do so well. The product is a breath of fresh air in the era of cloud providers. As an engineer, I'd kill to get to work with their hardware. Not to mention that working at Oxide sounds like a modern Sun Microsystems with the ideology that team has. Highly recommend their podcast "Oxide and Friends", and their original "On The Metal" show. I've attempted to apply to their company multiple times over th…
I've gone through the same process, not so much that I don't think I would be worth considering, but serious code and documentation examples aren't something I can really give out given that they're proprietary. this last winter I started a whole guest-kernel based syscall intermediation and distribution framework in rust just for the application. with all kinds of design documents. I was about 30% finished by the ti…