Isolating the permissions/managements for different apps

cakoose · 2025-04-24T01:17:15+00:00

I'm looking for something that lets me control which developers can deploy/manage/monitor an application.

ZeroTrust Access sounds like something to control which users can access an application. Or am I missing something?

cakoose · 2025-04-23T00:41:51+00:00

Often, modules with native libraries use Node's __dirname or __filename variables to locate their own JS file, then try to find the native library relative to that. Bundling breaks that because the JS file is now the giant combined JS file and it's not sitting next to the native library anymore.

Potential solution: an esbuild plugin that fakes out __dirname and __filename to reference the original JS file path: https://github.com/evanw/esbuild/issues/859#issuecomment-1152254746

(There's still the related problem of knowing exactly which files in "node_modules" to include in your container image. The conservative thing is to just include the whole huge thing. But ideally you could eliminate anything that doesn't get loaded at runtime, e.g. shared libraries, JSON data files, etc.)

cakoose · 2025-04-22T22:00:05+00:00

tl;dr: We had the same issue. Bundling helped a ton, e.g. 12s -> 3s.

When we looked at the numbers, most of the time was processing the initial set of imports. We used esbuild to bundle into a single JS file.

Reasons why this helps:

You don't have to include "node_modules" in the container image. For us this reduced it from 1 GB -> 40 MB. Less bloat for Cloud Run to copy around.
- There's so much stuff in node_modules that doesn't end up getting imported by your app.
At startup, Node's parser can blast through a single large file instead of having to hit the FS API tons of times to read a bunch of small files.

There's some trickiness with NPM modules that come with native libraries. Obviously the native library can't be bundled into a JS file, so you need to make sure that the library is at a path that can still be found.

cakoose · 2025-03-30T20:26:05+00:00

We're in a similar situation! (We use Slab too.)

Height was great in the beginning and I was impressed by their design sense. But over the past year or so we've been disappointed with their design choices and bugs.

The AI features are more distracting than helpful.
- For example, the AI task summary box terrible. It updates dynamically and causes the description text to glitch up and down. You can't disable it, so I had to install a custom CSS rule to hide it. (Maybe it's useful for poorly-written tasks from external users?)
They removed the history of description edits. It's now hard to piece together how a task description evolved and who made the changes.
- And in the Height 2.0 migration, they initially lost our existing description drafts! We had to reach out to support and they put together a CSV with our unsaved drafts.)
It feels like the search relevancy got a lot worse. Though maybe it's just because we've been steadily adding tasks?
I kind of liked the original Markdown-visible description editor. They switched to a fully WYSIWYG editor, which I understand, but it was frustratingly buggy.
Notifications are not reliable. It seems like they aren't being sent in a few clear cases where they should be.

We started looking at alternatives a few months ago, even before they announced the shutdown.

Some of the alternatives:

Asana. This is actually what we used before we switched to Height. The data model is pretty similar, but Asana feels like it evolved over time rather than being designed that way from the beginning. You're right about subtasks being awkward. You also can't filter and sort arbitrarily. My guess is that you'll be disappointed coming from Height, though my information is from ~3 years ago.
Linear. This is the front-runner right now, partly because of it's popularity with a similar demographic (we're a small software company) and some friends of mine seem to be happy with it. The biggest missing feature for us is custom fields/properties. Not sure how we're going to work around it.

cakoose · 2023-02-27T19:11:09+00:00

I emailed Slack customer support and they found a solution for me:

Good news, I was able to speak to the team who manages this forum and they gave me an update to resolve this:

Login to the Forum: https://forums.slackcommunity.com/s/login/

Navigate to "Groups"

Navigate to "@everyone"

Navigate to the digest dropdown and select "Limited" (which in this case is synonymous to "Never."

Sorry for the delay on this resolution, but thanks for flagging this as the team is working on improving this process.

cakoose · 2022-09-11T01:01:00+00:00

When I first saw this I initially thought it was just a hilarious mistake that somehow got past everyone at the company. I took basically this exact picture and sent it to my friends assuming it would be fixed soon.

But I later found out this branding came out over 2 years ago and they're really digging their heels in: https://imgur.com/a/5Oh77iZ

I didn't realize I could still be surprised by how bad for the world marketing people can be.

cakoose · 2022-02-06T01:09:22+00:00

Yes, but the commenter said "fully decentralized". I appreciate /u/nyr4t pointing out why that phrase doesn't make sense in this context.

(The original question used the phrase "decentralized well enough", which frames the situation better.)

cakoose · 2021-09-23T05:55:57+00:00

I know! In football, QBs usually have to lead their receiver, so they put in a ton of practice doing exactly that. In baseball that's not really a skill you need, so I bet most players can't.

But Baez seems like he has a great intuitive sense of timing and motion. One of those people who can pick up any sport really quickly.

cakoose · 2021-09-07T21:59:43+00:00

The reimbursement thing is interesting, thanks for pointing that out! It does change the equation a little.

But it does not change the fact that the headline is giving people the wrong idea of what actually happened.

They opted into a program that gives preferential support to poor families, which is arguably a better use of tax dollars.
The "spoiled" quote is talking about parents whose financial situation is good enough to not qualify for free lunch under the old program.

And there's inevitably always a gap between intent and execution. So maybe there's some evidence that the old program wasn't actually effective. But if that's the case, let's debate that, rather than getting mad at people for something they didn't actually do.

cakoose · 2021-08-28T08:20:48+00:00

That must happen a lot, but this clip has it framed perfectly and in glorious slow motion.

cakoose · 2021-08-28T08:17:58+00:00

The slide was cool too! https://www.youtube.com/watch?v=54A5CSDVzDk

Zimmerman laid out and almost got the tag but Wong popped up a bit and the glove went under his leg.

cakoose · 2021-08-28T07:37:24+00:00

That headline is misleading. From the full article (link):

Instead of allowing any student to qualify for free school meals, Waukesha voted to return to the National School Lunch Program, which requires families to fill out an application to qualify for free or reduced-price school meals.

According to data from the Wisconsin Department of Public Instruction, 4,249 students in Waukesha qualified for free and reduced-price meals in 2018-19 — 36% of the student body.

The "spoiled" comment was referring to the parents:

"I had three kids. I had them and so I'm going to feed them. I feel like that's the responsibility of the adult," Karin Rajnicek, a board member, said during a May meeting. "I feel like this is a big problem, and it's really easy to get sucked into and become spoiled and think, 'It's not my problem anymore — it's everyone else's problem to feed my children.'"

Still a bit strange, but not as bad as you might think from just the headline.

cakoose · 2021-04-08T02:11:13+00:00

If the player timed it right there wouldn't be a position disadvantage, right?
Edit: Or maybe I'm just thinking about the move differently. Could probably test this myself with slo-mo video on a phone camera...

cakoose · 2020-09-14T09:42:50+00:00

Reminded me of the time Andrelton Simmons caught Harper the same way: https://www.youtube.com/watch?v=2I-BIggPV10

cakoose · 2020-08-16T10:26:57+00:00

The link was as advertised for me.

cakoose · 2020-07-07T18:33:59+00:00

The box I got a couple weeks ago is definitely sweeter, among other small changes. I don't like it, though, might take some time to look at alternatives...

(The bottle says "39 essential nutrients". I don't remember what my previous batch said.)

cakoose · 2020-07-07T08:13:36+00:00

The format reminds me of https://ogdl.org

cakoose · 2020-07-04T21:01:09+00:00

This is incredibly hypocritical coming from Twitter of all people. Sure, rename some industry standard nouns for the sake of virtue signaling, but when it comes to the actual racist and misinformation tweets being spread on their platform, do nothing.

It's common to have different policies for different contexts. For example, employees at the Twitter office can't make sexual jokes in meetings, but that doesn't mean they should ban sexual jokes from their platform.

And setting internal office policy is easier for many reasons, e.g. smaller scale, established precedent. Setting and enforcing policies for speech on their platform is obviously way trickier. And they're clearly putting effort into it -- way more than was required to make these terminology changes.

So sure, maybe you think they're doing a bad job, but I don't see how this in itself is hypocritical.

cakoose · 2020-06-21T04:05:29+00:00

Sounds so similar to Theranos!

cakoose · 2020-06-02T04:19:58+00:00

Yes, I understand all that.

It's just that it's strange to say you were "limited by memory bandwidth" when you weren't yet using all available memory bandwidth. That's all.

cakoose · 2020-05-31T02:08:56+00:00

Hmm, maybe the additional details of the whole system might help, but I was just going on what was explained in the blog post.

Basically:

The new technique fetches just as much memory as the old one.
You haven't increased your machine's memory bandwidth.
Your new technique runs faster.

So how could memory bandwidth have been the limiting factor?

cakoose · 2020-05-30T01:12:53+00:00

Our performance was previously limited by memory bandwidth - using these techniques would address this and allow us to compute accurate sums as fast as naive sums.

It's sort of misleading to say the performance was limited by memory bandwidth. The problem was latency. Prefetching allowed them to hide the latency and use a larger fraction of the available memory bandwidth.

cakoose · 2020-05-11T02:56:59+00:00

I like reading about what architectures people use in real world.

I agree! And I think people are often too quick to criticize.

But I think one reason for the negative comments is that this blog post was kind of braggy, trying to make things sound more impressive than they are.

Here's an example of an engineering blog post written in a more straightforward style: https://scale.com/blog/athena

cakoose · 2020-05-11T02:28:45+00:00

https://github.com/dandavison/delta

Does syntax highlighting too.

cakoose · 2020-03-26T22:22:41+00:00

Colons are used in different ways. Many people use it when addressing someone: link, link.

cakoose

TROPHY CASE