Repost

Reposted Rob Allen (@rob@akrabat.com)
Post details
In my experience, multiple concepts invariably end up in a non-trivial PR. When a repository uses squash-and-merge then those concepts end up in the same single commit on main and any context is lost. https://indieweb.social/@lornajane/111425261462048360

by Jamie Tanna's profile image Jamie Tanna .

 Reply

Every time I work on a project like that I end up having to put myself through more ceremony to keep the atomic changes and commit messages, and I feel "if y'all would just let me rebase-and-merge or we learn together how to write better commits, it'd be easier"

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted lornajane (@lornajane@indieweb.social)
Post details
When you work on a project with squash-and-merge as a strategy, you end up splitting concepts across multiple pull requests to make coherent git history that could be untangled later if needed. Teams throw away the context because they have poor git commit practices, but they have poor git commit practices because they throw all that context away ...

by Jamie Tanna's profile image Jamie Tanna . #git.

 Repost

Reposted js (@js@social.lol)
Post details
@mhoye@mastodon.social there was a really good blog post that I can't find now, about how many (most?) feminine-coded hobbies/tasks like sewing, knitting, cooking, lots of housework, etc - are just straight up pure engineering tasks. you don't even have to squint to see it, but society likes to pretend that if it isn't made of concrete or steel, it doesn't count.

by Jamie Tanna's profile image Jamie Tanna .

 Reply

Have you asked the attendees what they'd like to do? (may sound rude but doesn't mean to be!) May lead to some interesting points and feedback, or a case of "we like it but I don't read up on Web stuff much" that's interesting to know too.

In the few CoPs I've helped organise over time:

  • Running a low-effort retro to see what's working and not working for folks can help - we did one which highlighted that a load of people wanted to dig into a specific subject, but no one had voiced that 😅
  • Rotating who's organising (preferably volunteering over voluntelling) can add a bit more variety - even if it's just the CoP leads/most senior folks to start with? Then can be rotated around with other folks too
  • Running a lean coffee was a good way to get to chat about things in a less pressured way than folks feeling they had to present something big for the session
  • Starting each session with a different engineer (who's been voluntold ahead of time) who does ~5-10 mins overview of their team, what they own and some of the stuff they've done gives a bit of an insight into what everyone does - depends on how much involvement folks get cross-team, but at a previous company this was super useful as it was a bit more silo'd

by Jamie Tanna's profile image Jamie Tanna .

 Reply

Tips for generally upping engagement, or for folks sharing things they've seen around the Web / have worked on recently that is interesting, or a mix of both? How many people are usually in the CoP meetings?

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked Sophie (@sophie@social.lol)
Post details
Does anyone have communities of practice at work with regular meetings? We have a (remote) monthly web dev catch up which I’d like to use for showcasing what’s going on in web around the company and also in the world of web more generally, but right now it feels a little too “Ms Koonin’s Compulsory Class Sharing Time”. Obvs people who don’t want to share/speak don’t have to, but any tips for things that have worked?

by Jamie Tanna's profile image Jamie Tanna .