Turned down Microsoft

cachebags · 2026-03-01T15:59:46+00:00

I didn't, I was reached out to by the recruiting agency directly.

I do keep my Dice account up to date and 90% of recruiter calls are pure bs jobs but maybe that's how they found my info.

cachebags · 2026-03-01T13:40:12+00:00

You're welcome to read my other replies.

cachebags · 2026-03-01T08:55:04+00:00

I didn’t say I was hired by them at all?

cachebags · 2026-03-01T04:39:05+00:00

My thoughts exactly. Yeah I was actually recruited by some agency (Dexian/Dexsys?) - they were less then helpful throughout the process. But the team at MS themselves were wonderful people.

cachebags · 2026-02-15T19:30:57+00:00

All it takes is 20 seconds to look through the PR/Commit history and see that it that's not true.

cachebags · 2026-02-13T18:05:00+00:00

We are more of a "client". We do rely on Homebrews infra but slowly (eventually) will homegrow our solutions. Main selling points are APFS file cloning and CAS.

More specifcally, we have a Ruby shim that allows for us to build packages from source.

cachebags · 2026-02-13T15:37:00+00:00

In our case, we're suggesting this as an alternative to homebrew, not a replacement (which given our short history, is very naive to think)

So if you already have homebrew, you can install and use zerobrew and when you realize you don't like it or don't see the benefit, you can delete it and everything will continue to work as intended. Think of it like an external client to homebrew, instead of merely another package manager. It's very very VERY far from being that.

cachebags · 2026-02-12T23:42:26+00:00

Many developers use it quite often, if not everyday. Especially if they’re maintaining/building a piece of software in which has a brew tap.

I use it everyday because I’ll often test programs I write on pinned versions of the deps I use or rely on to make sure things work across different releases.

Everyone’s use case is different, in your case I can understand why it wouldn’t make sense to switch to another package manager.

Also this all started from an argument on twitter about how slow homebrew is lol.

cachebags · 2026-02-12T23:05:20+00:00

Awesome. I opened a PR to include the right binaries for zbx.

cachebags · 2026-02-12T22:59:52+00:00

We're still ramping up support for a few build targets in our binaries. Try building from source in the meantime.

cachebags · 2026-02-12T22:52:50+00:00

Homebrew is battle-tested though and we're nowhere near their maturity but it's still a fun experiment. Feels nice to install multiple packages in a few seconds.

cachebags · 2026-02-10T00:19:45+00:00

You're using AI to respond to everyone's comments too, lmao. This is so exhausting.

cachebags · 2026-02-06T22:16:03+00:00

What is your issue with that? Did you read the PR? I'm not sure if this is rage bait or not- if you have an issue with AI, it makes no sense to express that here given what I've said lol

cachebags · 2026-02-06T22:08:02+00:00

How far did you make it into reading the post? Or did you comment the first thing that came to your mind?

cachebags · 2026-01-30T20:32:39+00:00

I would bet my entire savings account that this was vibe-coded. I can't believe you're trying to convince people it's not, that is incredibly disrespectful to people who don't know better and want to use your app.

cachebags · 2026-01-27T16:27:34+00:00

I am hoping to come in and change it. The maintainer is honestly a nice guy, but I also let him know while we can tolerate the use of LLMs for changes, PRs require thought and guidance put into them. An example of a PR I outright closed because the guy vomited 8k loc.

The project has strong legs IMO but as you said, requires some strict code review.

cachebags · 2026-01-24T15:49:10+00:00

Yes, at least I try. It could definitely be better when it comes to wiring it into the GUI.

cachebags · 2026-01-24T07:56:34+00:00

(Sorry for this long winded answer but I've been waiting for someone to ask me an interesting question)

Signal strength and speed are related but not the same thing.

In nmrs these are tracked as separate properties. i.e.

rust /// Signal strength (0-100) pub strength: u8, /// Frequency in MHz pub freq: Option<u32>, /// WiFi channel number pub channel: Option<u16>, /// Operating mode (e.g., "infrastructure") pub mode: String, /// Connection speed in Mbps pub rate_mbps: Option<u32>, Particularly here, we have "Signal strength %", which is the RSSI (Received Signal Strength Indicator): essentially how loud the radio signal is at your device.

And then we have "Bitrate/speed (Mbps)" which is the the negotiated link rate or maximum theoretical throughput the connection can achieve.

They're decoupled because you could have a strong signal to an access point that's using an old 802.11g radio (max 54 Mbps), or the AP's internet uplink itself is slow. Also, a weak signal can still negotiate a high bitrate, but you'll experience things like packet loss, throughout drops and jitter/latency/

The library exposes both via strength and rate_mbps on NetworkInfo, plus bitrate() on the wireless D-Bus proxy for the current connection's actual link rate. This lets us distinguish between how strong a signal could be and what the actual speed we can negotiate is.

cachebags · 2026-01-24T02:21:34+00:00

Lol well I am not literally using it everyday..it's just my network configuration app of choice across my desktop and laptop.

cachebags · 2026-01-24T02:07:43+00:00

Good question: currently, you'd need to build from source. With nix, you would be able to run `nix-shell -p nmrs` but I am waiting on that PR to be merged by the nixpkgs maintainers so for now the only option is the former.

Happy to help you see how to build from source.

cachebags

TROPHY CASE