It was indeed a recruiter, good job Fediverse! (Though I'm sure the fact that I wouldn't have posted this if it wasn't a recruiter played a role…)

Either way, responding to this message is bound to be a surefire way to land a job with interesting and diverse colleagues, don't you think?

mastodon.social/@vinnl/1057866

Show thread

@nolan "Trusting your collaborator to deal with feedback on their own using their best judgement" also means that it's OK for them to brush it aside.

That attitude, combined with suggested edits making it really easy for them to incorporate your feedback if they see the value, does away with most of the friction nitpicks and other minor disagreements can cause.

@nolan One thing I wish GitHub would change is to rename the "Approve" and "Request changes" options for a review. There's a lot of things (nitpicks, but also slightly more serious issues) that can very easily be resolved, and that don't need another re-review because you can trust your collaborator to deal with them on their own using their best judgment.

"Request changes" only really applies when you need to align on the approach before merging it in, which is very rare.

@nolan "Trusting your collaborator to deal with feedback on their own using their best judgement" also means that it's OK for them to brush it aside.

That attitude, combined with suggested edits making it really easy for them to incorporate your feedback if they see the value, does away with most of the friction nitpicks and other minor disagreements can cause.

@nolan One thing I wish GitHub would change is to rename the "Approve" and "Request changes" options for a review. There's a lot of things (nitpicks, but also slightly more serious issues) that can very easily be resolved, and that don't need another re-review because you can trust your collaborator to deal with them on their own using their best judgment.

"Request changes" only really applies when you need to align on the approach before merging it in, which is very rare.

Got a message from someone saying she "would not forgive [herself] for not making a move on me", and that she'd "love to make time to (virtually) have a cup of coffee together".

Pop quiz! Was this…

New blog post: "JavaScript performance beyond bundle size" nolanlawson.com/2021/02/23/jav

This is kind of a grab-bag post about all the different performance metrics I think about when writing or using JavaScript modules. I hope folks find it interesting!

This is also a great attitude:

> Be prepared for your feedback not to be acted upon

If you're the one who's going to have to maintain the work, of course your input matters. But sometimes we're wrong, sometimes it's just Not That Important. There's no need to "win" everything.

Show thread

This is a great point:

> It might feel to them as you're criticizing them personally, and it takes a lot of effort not to take the criticism personally. Honor that effort by making it easier not to take it personally.

Sure, it'd be great if people would try not to take things personally — especially if it wasn't intended as a personal attack! But we're all human and imperfect, and by taking the small effort of being mindful of that, feedback can be so much more effective.

Show thread

Are YOU with us? Sign now!

40 orgas across Europe. We call on the EU to ban biometric mass surveillance.

For a future in which we are treated like humans, not walking barcodes, in which we are respected and not humiliated, discriminated against or treated like crime suspects, in which our options are not limited by an algorithm based on our body and looks.

Now's the time to act!
The tech is out there, but the EU is drafting new laws on AI.

#ReclaimYourFace
reclaimyourface.eu/

@celia I recently used it to suggest servers to users while allowing them to pass in their own in penny.vincenttunru.com

Additionally, I used it to suggest commonly-used URLs for predicates that people could use.

@happybeing @janriemer (It's nitpicking, but "go-to-definition" and all that in VSCode is technically powered by TypeScript :) )

@noeldemartin Yeah exactly, and for all the stuff I *do* have under my domain, I'm afraid that I'll one day mess it all up in one fell swoop 😅

@noeldemartin Yep, but setting up my own domain is still more hassle and reliance on unreliable me than I'm willing to bear at this time. Additionally, it feels like somewhat of a waste of resources that I'd like to avoid if I can.

Unfortunately, though there are plenty of people I trust, I think there are none who are also running an instance and are relatively sure they'll still be running it in a couple of years.

Pinafore development 

I also saw it as a way to push the limits of what the web could do. However, I've become a bit chastened and disillusioned about this. For instance:

- Pinafore doesn't have nice animated transitions like native apps do. The web still sucks at this.
- Offline support is almost impossibly hard given Mastodon's API. The main benefit of IDB right now is low memory usage.
- PWAs haven't come far enough. Pinafore isn't listed in app stores, so it "doesn't exist" for most users.

Show thread

@silmathoron That would be an obvious criterion to look at (that I think holds for Fosstodon). I suppose sources of funding would be another. But mostly, I'm wondering if people know of other things that would be relevant to consider, and how those apply to Fosstodon.

@silmathoron Right, I'm sure there's no 100% perfect instance, but I'd still guess that the expected longevity does differ per instance. It seems like mastodon.social has the best prospects, and as far as I can see Fosstodon is not far behind. But I'm not sure, which is why I'm asking :)

@jwildeboer Haha yeah I'm definitely not going to do that: if I want some longer-term certainty, I'd best take myself out of the equation as much as possible :) But thanks for the suggestion.

Show older
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!