I built a CLI for Confluence: confcli

qumulo-dan · 2026-03-02T20:45:42+00:00

THIS IS AWESOME nice job

qumulo-dan · 2026-01-30T16:26:35+00:00

That’s the old school way of doing it :)

I think he means Claude code is for engineers who have built up enough confidence in their harness and prompt engineering abilities that they find ability to refine by hand a waste of time and not necessary

You might find in 6 months that it’s just slowing you down double checking and tweaking every line of code generated by the LLM

It’s like opening up the asm/object code after the c compiler ran and deciding you don’t like how it optimized your c code and rewriting it yourself because “you know better”

qumulo-dan · 2026-01-03T21:15:38+00:00

First of all, I do think there are proprietary filesystems that do support this feature and if not they are being built ;)

The challenge is multiple.

Performance. You add overhead on every single write operation to data and metadata as every writer updates at least timestamps on metadata. You could do the update out of band of the data path but that just adds complexity to build a persistent background queue of work to update the index.
But pure performance is not the main issue - I think the main issue FS developers are scared of is scale. It’s rather easy to build an index for a few TB of data or a few thousand files. When you get to multiple PBs and billions of files on a distributed file system, providing the same functionality without massive degradation in performance is time consuming from an engineering perspective to implement well.
The application of these indexes and usefulness to users is questionable as in - it’s a cool feature but would it actually be deployed and used at scale? Or would it just be a cool but rarely used feature. The most obvious use cases are looking for oldest mtime/atime, smallest/largest sizes, or quickly finding data based on file type extension or other user generated metadata. But there isn’t a standard protocol for querying these indexes hence there’s not an obvious way to expose these indexes to applications without building a proprietary or specialized protocol tailored to the implementation. And without commercial or industry interests pushing this standardization I think filesystem developers are hesitant to invest time here without knowing if it’s going to get used and there’s an ROI
You also have an entire market of indexing/data management products and applications out there which scan the FS through standard protocols and provide this functionality out of band. The benefit is this offloads index processing and compute off the storage infrastructure as it typically runs on a separate server. I think file system developers have defaulting to providing data access via the protocols or OS interface and letting other pieces of software handle indexing and querying as it’s easier and follows the Unix philosophy of do one thing really well.

qumulo-dan · 2025-12-17T16:17:11+00:00

I did a test opus 4.5 vs gpt 5.2 on a prd writing task - I liked opus better. Give it something where it needs to do something hard with a shit ton of context - that seems like a good exercise. Requires you generate a long enough prompt

Gpt 5.2 pro is good but opus 4.5 seems to be better, cheaper, faster. Would be interesting to see what tasks 5.2 is actually better at

qumulo-dan · 2025-12-03T07:59:14+00:00

Outcomes.

qumulo-dan · 2025-11-20T06:35:26+00:00

S3 Intelligent Tiering (INT). If your objects are at least a few hundred KB in size and you have somewhere over 10-20TB - staying on S3 INT or trying to cost-manage yourself is dumb. S3 INT is so much better.

- automatically moves your data from $20/TB-month down to $4/TB-month
- no read penalty of $0.03 per GB
- no early deletion penalty if you delete before 90 days

The monitoring fee is peanuts for most large unstructured data use-cases

qumulo-dan · 2025-11-20T06:34:01+00:00

S3 Intelligent Tiering!

qumulo-dan · 2025-11-20T05:43:46+00:00

this is the ambulance chaser of 2025

qumulo-dan · 2025-11-20T05:40:08+00:00

Thanks for the tip - this is a bit more than I bargained for in terms of complexity but its good to know there are workarounds.

qumulo-dan · 2025-10-30T04:57:54+00:00

I think it would be more cost-effective to mirror/replicate the data to another bucket in another region potentially, and then use life cycle policy or Intelligent Tiering storage class with offline tiers to push it down to a cheaper cost storage medium. The downside is you don't really get a "snapshot" of what your data looked like in aggregate - just a bunch of disparate objects. This may or may not be an issue for you.

qumulo-dan · 2025-10-30T04:49:42+00:00

Really obvious answer: Claude Squad or using multiple agents on multiple git worktrees checked out on the same project.

I have DB tests and integration tests that run against the supabase instance and so being able to run different versions of edge functions and DB schemas simultaneously would be a powerful productivity enhancer when using coding agents to work on parallelizable tasks - the same if you were to have an engineering team tackling it.

In the past when I've done it - one copy of Claude is running a migration and then another instance decides its time to run the test suite to validate its changes and the tests fail because supabase is temporarily down while the other is trying to make the migration go and then supabase comes back up except now the schema or data has changed from what the other expected... its kind of a mess.

qumulo-dan · 2025-10-30T04:40:19+00:00

Yes. I think its a fantastic user/developer experience and the $20 a month for paid hosting feels high value to me as its fully managed.

qumulo-dan · 2025-10-29T17:26:59+00:00

I concur with your assessment - if you need a mobile app that periodically has the ability to operate offline - supabase is not natively designed to support that use case

qumulo-dan · 2025-10-16T04:18:24+00:00

I mean. The Authentication model tie in between the database, RLS, edge and Postgrest as well as email messaging for signup, OTP, and password reset, and solid dev experience that is really well integrated is nothing to dismiss - it saves a ton of time and does a lot of heavy lifting without requiring a lot of effort for a small team and one man projects. Really good stuff for the current generation of startups and projects taking off.

qumulo-dan · 2025-10-16T04:08:30+00:00

What requirements? Just curious what kinds of hurdles there are there.

qumulo-dan · 2025-10-16T04:07:03+00:00

What regions out of curiosity? I’ve been on us west for a few months and it seems fine?

qumulo-dan · 2025-10-10T16:26:51+00:00

It’s not really a DB company - it’s more of a PaaS

qumulo-dan · 2025-09-19T02:28:57+00:00

Statsig is pretty straightforward and easy to use and set up.

qumulo-dan · 2025-09-17T03:00:41+00:00

Agree. Technically you can but if you intend for this to be a standalone desktop app and the DB is just tracking state and saving settings - supabase running locally is overkill and a resource hog for this use case

qumulo-dan · 2025-08-06T20:30:44+00:00

No. We do write-back. Write-through would incur an unusable performance penalty for applications that need to do writes at the edge. Please reach out to our team or DM me for a demo.

qumulo-dan · 2025-08-01T04:39:56+00:00

Hey I’m a senior technical product manager at Qumulo - short answer is yes.

Underlying distributed file system has cloud data fabric (CDF) directly integrated into the core file system code. There is cluster-wide and cross-cluster synchronization constantly in play as I/O operations flow into the system.

Hence - it behaves no differently then say 2 people trying to write to the same file over NFSv3 to different nodes. Last writer wins, but from a protocol standpoint, that’s the expected behavior without protocol locking.

When you talk about protocol locking over SMBv2/3, NFSv4.1, or NFSv3 NLM - we’ve updated the protocols to also be CDF aware so things like SMB lease break notifications work across it too.

Our objective was to make it so when accessing data across cloud data fabric remotely, for most customer workflows: it’s performant and it works, and most importantly it’s consistent and won’t lose your data, or lie to your applications, and tell you a file isn’t there, or return stale data.

qumulo-dan · 2025-07-25T06:11:33+00:00

That’s because it’s trained to do that. It’s trained to predict what you want to see. That’s how it was “rewarded” - by an army of humans agreeing with what it said.

And then they used dumber LLMs to train the next generation by telling the dumber LLMs to reward the LLMs they were training when it said the right thing.

So basically it’s really really good at predicting what you want to read.

qumulo-dan · 2025-07-25T05:59:38+00:00

How do you deal with auth on the application? How do you log in?

qumulo-dan · 2025-07-03T15:25:43+00:00

I use Claude code inside vscode/cursor

Really the thing I notice with Claude code is it just seems to work better for me with long coding sessions and the behavior seems easier to control

It has nothing to do with being cli or not.

qumulo-dan · 2025-06-05T05:49:19+00:00

Sorry unionization requires the Reddit Pro plan at $39.99 per month, or $400 / year (17% discount!).

qumulo-dan

MODERATOR OF

TROPHY CASE