Stanford Research Computing | Stanford, CA (next to Palo Alto) | Full-time | Three positions | HYBRID,ONSITE
Stanford Research Computing (https://srcc.stanford.edu) is a collaboration between University IT and the Vice Provost and Dean of Research. We operate HPC environments for researchers, we do one-time consultations on projects (from software and pipelines, to data management, to physical building design and fit-out), and we provide contract support for individual Labs, Departments, and Schools.
We have four open positions, three hybrid and one (marked) onsite:
• Principal Storage Architect & Team Lead: Our current storage team lead is moving on to Industry, so we're splitting his work into two separate roles. This is the Technical Manager position: You'll be leading the storage team, setting the direction for our large storage environments: Oak (file storage, used by multiple cluster), Fir (fast scratch for Sherlock), and Elm (object storage on top of tape). Knowledge of Lustre, Infiniband, and PB-scale storage is important. More info: https://bit.ly/44PbQnr
• Storage Architect or Storage Sysadmin: This is the second role I referenced above. You'll be maintaining & expanding Oak, our 20+ Pebibyte Lustre storage environment used by our largest HPC clusters. Depending on your experience level, you might also have some responsibility for Elm, which provides object storage on top of tape. Knowledge of Lustre, Infiniband, and PB-scale
storage is important here, too. More info: https://bit.ly/4y8lj6R
• GPU Cluster Sysadmin: With Marlowe—our 1SU NVIDIA DGX H100 SuperPOD with DDN Intelliflash and DDN NFS storage—launched, we have decided to hire an additional sysadmin! You'll be working with the latest AI/ML/Deep Learning/LLM software & frameworks, getting them to work in an HPC environment. You'll be keeping the environment up-to-date, and working with NVIDIA/DDN when there's trouble. You should also expect to interact with users & PIs a lot. More info: https://bit.ly/4vf7aly
• HPC Hardware & Infra Sysadmin [ONSITE]: We are looking for a system administrator to help run the hardware & infrastructure portions of Sherlock, our largest HPC cluster. Sherlock is a mix of Intel & AMD x86_64 servers, with three Infiniband fabrics, plus an Ethernet backbone. You'll be responsible for maintaining, troubleshooting, and improving the hardware of Sherlock. That is, keeping things working, and figuring out how to make it better. More info: https://bit.ly/3SPRpnJ
If you don't already live in the Bay Area, we provide a relocation incentive. Depending on where you live, we provide free transit passes. Unfortunately, if you drive, you will have to pay for parking for the days you're on-site. There is some on-call around the holidays. We get a 403(b) match, good healthcare, and 30+ days off per year (holidays + vacation). All Benefits are all publicly documented at https://cardinalatwork.stanford.edu/benefits-rewards.
If you have questions, feel free to reply here or email me (the info is in my profile)!
There are other lines in the post that, to me, provide clarity.
First is this, the second paragraph:
> British-based employees at the Wikimedia Foundation (WMF) wrote a letter to management today (Wednesday 24thJune) requesting their right to be represented by the United Tech and Allied Workers (UTAW) section of the Communication Workers Union (CWU).
That makes it clear that this is regarding the "British-based employees at the Wikimedia Foundation". Yes, the headline does say "Wikipedia": I expect the CWU chose that because many more folks know what Wikipedia is, vs. the Wikimedia foundation.
Second is this:
> Over 1000 Wikimedia volunteers and community members have also signed petitions in support of the workers, who have networked globally under the banner of Wiki Workers United (WWU).
I view terms like "[wikipedia] editors" as terms of art: "Editor" in the Wikipedia context maps to the more-generic "volunteer" in the broader context, which is why the post is referring here to "volunteers and community members".
So, I don't see any inconsistency in the article, but I see how the current post title can make it confusing.
In my opinion, I think it would be appropriate for you to email the HN folks, to ask the title be changed to something like "Wikimedia Foundation Workers to Seek Union Recognition".
The content of https://news.ycombinator.com/item?id=48628303 should have been posted as the item's text. Or, that text could've been put in to an Issue, and the link pointed to that.
To be clear, Wise (previously "Transfer Wise", symbol `WISE` on the LSE) is not a bank. Wise is a Money Services Business in the US; in the UK, they are an Electronic Money (e-money) Institution. When they are holding your money, they use the services of one or more actual banks.
So, I'd be careful calling Wise a "UK bank", as that gives the wrong impression.
This makes me think of Jazz Semiconductor in Newport Beach. I think they’re Tower Semiconductor now, but I believe they’re still there, a small fab in SoCal that I assume is making obscure, important stuff.
Chris' videos are really good. And that was a great surprise at the end! (Yes, I'm being intentionally vague to get you to watch the video.)
I played SimCity in the past, along with Cities: Skylines. I enjoyed both, but it always felt weird, like I was handling things I wouldn't expect to handle.
Yes, 100G multimode transceivers are cheaper, but they don't use the same fiber.
100G on singlemode (100G-LR4 being the most common) uses the well-known two-strand ("duplex") fiber. Or you can get 100G bi-directional ("BiDi") over a single strand of singlemode (fiber-to-the-home often uses this).
100G on multimode is weird. As the name implies, one beam of light, sent down the core of a multimode fiber, results in multiple modes (search "Laser modes") being sent down the strand. As they overlap, it gets hard to get a clean signal out the other end.
To deal with this issue, 100G on multimode uses fiber cables containing multiple strands per direction of travel. MPO-8 and MPO-12 are common cables used for 100G multimode: It contains eight or twelve strands of fiber. Four strands are used to send, four to receive. And the prices for those cables are higher than standard duplex singlemode cable.
Are you talking about El Camino Real? There are two areas of construction happening: One at Page Mill and one in the San Antonio area. Most of the lane-blocks are happening only between rush hours, so it's easy to miss, but I'm guessing that it's someone at Waymo has put full-time blocks in those areas.
I checked in the Waymo app; it would be several blocks. Please reference the context "which I used to get to PT". I'm happy that, today, the extra blocks are doable. Some weeks ago, those extra blocks would not be doable.
Finally, besides the point of having to walk the distance, the main issue is the way in which the blockage is being conveyed to me: The Waymo app is not saying "We cannot get to you because of construction", the app is telling me that requests have been paused. Specifically, it's telling me "All of our cars are busy with riders right now" and "We're pausing requests in order to catch up — please check back again".
I said “20 minutes (or more)”. The 20-minute case is for a pickup at 5 AM. If I travel to the airport later in the morning, the time difference is worse.
And although 20 minutes doesn’t seem much, the variability of airline baggage check and TSA means 20 minutes doesn’t seem an lead to increased stress.
I wonder how the subscription would respond to a person's area being blocked off.
There construction happening a block down the road from me. As part of the work, the rightmost lane is often blocked during the day (in between rush hours), so that things like concrete pumping can take place. The lane block starts just before where I live.
Around the same time, I noticed that when I would try to take Waymo (which I used to get to PT), I'd be told that things are busy and rides are paused. Recently, I've noticed that if I'm at work (or the PT place) and I want to take a Waymo back home, I'm told "Can't get to that spot right now".
If I had Waymo Premier, I wonder how hard it would be to get a refund on my subscription.
The above talks about a complete block (or, a complete-enough block) to using the service, but what about a major impediment? For example, let's say I travel regularly, and use Waymo to get to/from San Jose airport. Waymo's been disabling highway routes, which for me equates to 20-minute (or more) travel-time increase from home to airport. Would that be enough to qualify for a refund on the subscription?
> The change to zero memory was my idea and my change. It was a reaction to a security report I got which caused use of an element past the end of an array. By zeroing the allocation I could ensure that misuse of that memory if a similar bug came up in the future could only cause a null ptr deref, which is better than the chance of a valid pointer.
> It got a claude co-authored tag on it as I got it to do some tidy ups of a series of commits, and that is just what it does when it makes any modification. It doesn't mean the change was written by claude. It was written by me.
I am surprised the trunk didn't open, and I’m very surprised that Waymo support could not turn the vehicle around. I’ve had a Waymo alert me when I left something in the back seat; I’m surprised it did not do the same for the trunk.
I think the person should report this to either the California DMV or CPUC, as well as the local airport authority.
For autonomous vehicles, I think people need to ‘normalize’ leaving one of the doors open until all people & cargo are out of the vehicle. The vehicle may complain, but it’s not going to drive off.