mark

joined 1 year ago
[–] mark@programming.dev 3 points 1 year ago (1 children)

I use Todoist. But I'm currently trying to get to the bottom of what their privacy stance is. Their Privacy Policy is too vague for my liking. I've been recently talking with their staff and asking some questions about it, but they've been slow to respond.

[–] mark@programming.dev 1 points 1 year ago (1 children)

Oh I mean I can't seem to see any of the communities or posts made there on my Lemmy instance (the one I'm writing this comment from)

[–] mark@programming.dev 3 points 1 year ago

Something tells me that the people who use Instagram will use Threads, regardless of how it's linked. And they don't strike me as the types that would delete their account when they want to stop using a platform—they'll just stop using it. So point just seems moot, imo. But whatevs...

[–] mark@programming.dev 2 points 1 year ago (3 children)

Looked around and it's impressive they were able to replicate so much functionality! It doesnt seem to federate with other fedi platforms, though. At least it doesnt with Lemmy.

[–] mark@programming.dev 4 points 1 year ago (6 children)

Does anyone know what the author's point is here? Failing to see it

[–] mark@programming.dev 1 points 1 year ago

Yeah, we use Storybook with Chromatic for visual regression testing as well. Good tool! 👍

[–] mark@programming.dev 1 points 1 year ago* (last edited 1 year ago)

It may be difficult if the context behind those decisions are lost, but I imagine it can be doable for a smaller company, assuming the amount is reasonable. And ofc, there's always a chance the extra overhead may piss off a few engineers 😆

[–] mark@programming.dev 3 points 1 year ago

The meetings approach is interesting. I think we did those for RFCs but I remember they were very very long and unproductive. I think the company size matters when determining the right approach.

[–] mark@programming.dev 2 points 1 year ago (2 children)

we generally first discuss the topic and then write the accepted decision in an ADR. So, there isn’t much room for discussion/voting afterwards.

This makes sense. I guess it would cut down on the noise in the PR since, at the point of its creation, it's already been accepted. Our repos have so many other teams contributing to them that it's hard to rally everyone to build consensus on an ADR beforehand. I guess we could hold meetings, but having feedback in a PR allows us to go back and look at what discussions led to a decision later on.

How does your team build consensus before opening the PR? Is it through slack or some other chat tool? Or maybe a meeting?

[–] mark@programming.dev 1 points 1 year ago

As a US slave, I'm super excited for this! I've been using the previous version for about two years now, and it's been awesome. I'd even say it's on par, if not better, than Apple and Google flagship phones. But that's just my opinion.

[–] mark@programming.dev 3 points 1 year ago* (last edited 1 year ago) (4 children)

We just thumbs up the PR for an ADR if we're in favor of it. Does that differ from the ADR format?

[–] mark@programming.dev 1 points 1 year ago

I chose an instance with software engineers. Not only because I'm a software engineer myself but also because we have admins that can probably fix any issues with the instance quickly. But I can't confirm whether thats true or not. Just my thought.

view more: ‹ prev next ›