Hilariously, the physical cards can only be topped up at add fare machines (cash only) or ATMs (cash only).
If you go down the "add a pasmo/suica on your phone" then you get into licensing issues with the other cabal (credit card issuers): you need to use an Amex to charge it via Apple Pay (IIRC Visa is now supported, but when I tried it last week my card was declined, so... YMMV).
Assuming you’re a tourist, are you sure it’s not your bank flagging the transaction?
When visiting in April I too thought it was an issue with the card when trying to reload on apple wallet, but after two cards declined, found out the transaction was flagged haha
Same experience with reloading on the physical machines. It’s quite amusing
Same card worked via Apple wallet for other transactions, and the Visa thing is a known issue historically (https://discussions.apple.com/thread/255018680?sortBy=rank). A local friend confirmed the fix, but I can't seem to find any info from Apple or Visa about it.
It's working now (https://atadistance.net/2023/12/15/apple-pay-suica-visa-rech...) and has been working since ~2023. The last hurdle many face is that if you disable location services, sometimes the transaction is still blocked as they can now geofence it to just Japan with foreign bank cards.
Fluidstack | Forward Deployed Engineer, SWE, SRE, Infrastructure, Networking, Devrel | London/SF/NYC or remote | fluidstack.io Fluidstack builds and operates GPU supercomputers for top AI labs, governments, and enterprises. Our customers include Mistral, Poolside, Black Forest Labs, Meta, and more.
Engineers at Fluidstack work on a wide variety of activities, including:
- Deploying clusters of 1,000+ GPUs and operating them with and for customers.
- Validating correctness and performance of underlying compute, storage, and networking infrastructure, and working with providers to optimize these subsystems.
- Migrating petabytes of data from public cloud platforms to local storage, as quickly and cost effectively as possible.
- Debugging issues anywhere in the stack, from “this server’s fan is blocked by a plastic bag” to “optimizing S3 dataloaders from buckets in different regions”.
- Building internal tooling to decrease deployment time and increase cluster reliability, including automation where the customer benefits clearly outweigh the implementation overhead.
We don't require prior experience with GPUs or AI/ML; we require a willingness to learn quickly, work hard, and obsess about customer success.
> The sudden shift is fueled by fears of tariffs as Donald Trump threatens a trade war that could disrupt the gold market. Traders, worried that gold imports may soon face tariffs, are rushing to get their bullion into the U.S. before the policy takes effect.
Fluidstack | Forward Deployed Engineer, SWE, SRE, Infrastructure, Networking, Devrel | London/SF/NYC or remote | fluidstack.io
Fluidstack builds and operates GPU supercomputers for top AI labs, governments, and enterprises. Our customers include Mistral, Poolside, Black Forest Labs, Meta, and more.
Engineers at Fluidstack work on a wide variety of activities, including:
- Deploying clusters of 1,000+ GPUs and operating them with and for customers.
- Validating correctness and performance of underlying compute, storage, and networking infrastructure, and working with providers to optimize these subsystems.
- Migrating petabytes of data from public cloud platforms to local storage, as quickly and cost effectively as possible.
- Debugging issues anywhere in the stack, from “this server’s fan is blocked by a plastic bag” to “optimizing S3 dataloaders from buckets in different regions”.
- Building internal tooling to decrease deployment time and increase cluster reliability, including automation where the customer benefits clearly outweigh the implementation overhead.
We don't require prior experience with GPUs or AI/ML; we require a willingness to learn quickly, work hard, and obsess about customer success.
Fluidstack builds and operates GPU supercomputers for top AI labs, governments, and enterprises. Our customers include Mistral, Poolside, Black Forest Labs, Meta, and more.
Engineers at Fluidstack work on a wide variety of activities, including:
- Deploying clusters of 1,000+ GPUs and operating them with and for customers.
- Validating correctness and performance of underlying compute, storage, and networking infrastructure, and working with providers to optimize these subsystems.
- Migrating petabytes of data from public cloud platforms to local storage, as quickly and cost effectively as possible.
- Debugging issues anywhere in the stack, from “this server’s fan is blocked by a plastic bag” to “optimizing S3 dataloaders from buckets in different regions”.
- Building internal tooling to decrease deployment time and increase cluster reliability, including automation where the customer benefits clearly outweigh the implementation overhead.
We don't require prior experience with GPUs or AI/ML; we require a willingness to learn quickly, work hard, and obsess about customer success.
Having recently listened to TSMC as well as Costco, LVMH, and Hermes, there's something available to every member of the HN audience in every episode, no matter how "unrelated" you may think it is.
On the other side of the table, as a former sponsor of a season or two: it was the best marketing we (Crusoe) could have done. We had more high quality inbound from our audience than any other channel, by a long shot. They deeply understand their audience and target appropriately. Strongly recommend to anyone trying to reach a decision making audience (customer and investor).
How did you measure that? Podcast ads seem almost like old school TV in that a lot of listening is offline, with no call to action or method of measurement. Despite racing and resonating deeply with an audience.
1. I believe they require that you have an acquired specific landing page (e.g. crusoe.ai/acquired), which we saw directly as conversions through to our waitlist. The volume was lower than other channels, but the signal was much, much higher.
2. To @scarface_74's comment, "you talk to customer and you can ask them where they heard about you from" is mostly why I made the claim. In particular, when fundraising, basically everyone I talked to said, "I heard about you on Acquired, really interesting business model that I hadn't considered, let's talk more about it."
Sponsorship isn't cheap (I would go so far as to call it expensive), but relative to spending an equivalent amount on search or display ads/billboards on 101/etc., I think it was the right choice at the time.
My only analogy for this is what I call "cruise missile marketing" where you're investing a lot of time/money in building something that is very specifically targeted at high value buyers. It works really well for large, infrequent transactions (raising capital, selling GPU clusters, etc.) and less well for commodity SaaS or B2C products where volume >> everything.
Not sure why it's getting downvoted, definitely experienced Code Yellows, Code Reds and Code Purples at Google. Red is (obviously) worse than Yellow and IIRC was a total code freeze for a period of time. IIRC there was a Code Red around memory at some point because the supply chain was literally so backed up that google couldn't get enough DIMMs and reasonably sized services had to stop deploying because there wasn't enough compute capacity.
Purple is/was "developer experience is so bad we need to stop developing new functionality and make the current functionality usable."
- Code red: the situation is actively causing active business harm.
- Code yellow: the situation will cause irreparable business harm if not addressed in the next 3-6 months.
- Code purple: the situation will cause business harm if not addressed in the next year.
- Code green: things are not at risk of causing problems, but we still want to make sure we make progress.
At Google, all of these priority codes need senior VP signoff, which is to say that it is actually an existential threat to one of our main product areas (e.g. Search).
I only remember the RAM crunch (2020 or maybe 2021) being a code yellow, but it's possible it was downgraded after the first month or two.
Code reds don't always have to be met with a total code freeze, but they generally do preempt all work outside of incident response.
The point of a code yellow should not be to punish the team, and an appropriately-declared code yellow should be met with significant introspection from leadership about how we got into this mess and what we need to do to prevent us from getting into this mess in the future. It's a blunt tool that allows the organization to dictate that it's going to drop its existing commitments on the floor because they are simply less important than fixing the systemic problem.
You don't need a code yellow to try multiple things in parallel, or to ship a prototype without worrying about scale. A startup certainly doesn't need a code yellow to empower individuals to wear multiple hats. And if your team is spending 50-75% of its time on keep-the-lights-on work, then your systems are being held together by duct tape, and this is simply not sustainable.
> Can confirm: there are about two dozen bottom bracket tools in the drawer. In fairness, bottom brackets have been a pain in the ass for decades. Even on old ones, there are a couple different hook spanners and pin spanners you might need for the lock ring and adjustable cup and a couple other weird-ass wrenches that you need from time to time. Shit's usually tight AF too, and the various tools that were fine for manufacturing a bike get a little iffy when everything's good and seized after 20 years of neglect.
I agree the various (totally random) BB standards are a pain; every bike build I've done has meant that I CADed and then 3D printed the tool (100% infill PETG, takes ~2 hours on a Prusa MK3S).
Curious how long it is before we get 3D printing tech easy enough to where shops can have a printer, download any special tools for a bike assembly, and make them in a few hours.
Less fully featured, but more open (Gaggiuino became closed source post people profiting off the OSS).
I'll also pitch another fun OSS project I sponsored a few years back to build an OSS pressure sensor and 0.1g scale: https://github.com/rhit-coultabm/Consistent-Cups-Espresso-Ac...
Since then it looks like Decent has OSS'ed the DecentScale: https://github.com/decentespresso/openscale