Mastodawn

Bertocq Nov 28, 2023

Alfonso Uceda Oct 22, 2023

https://github.com/aaronjensen/software-development

Really good articles about software programming from Aaron Jensen

GitHub - aaronjensen/software-development: Notes and articles on software development. All content is original. Most of the content reflects the way that our current software team operates.

Notes and articles on software development. All content is original. Most of the content reflects the way that our current software team operates. - GitHub - aaronjensen/software-development: Notes...

GitHub

Bertocq Apr 16, 2023

@porras I was looking for this kind of info, thanks for the research!

Bertocq Dec 23, 2022

@porras Hace tiempo que hice caso a este señor https://www.glennstovall.com/the-wolf-test/ y es bastante gracioso cuando me escriben un "Hi 🐮", suelo contestar con un 🤠 a secas.

The Wolf Test

Dealing with recruiter spam on LinkedIn, for good. I've recently implemented a change to my LinkedIn profile, one that helps me filter out automated recruiter spam. I call it "The Wolf Test" Here's how it works: 1. Replace your first name with an emoji of your choice. I went with

Glenn Stovall

Bertocq Dec 8, 2022

Bozhidar Batsov 💎Dec 8, 2022

RuboCop 1.40 is out! (https://github.com/rubocop/rubocop/releases/tag/v1.40.0) We've been cooking this release for quite a while and it has a ton of small improvements (and some bigger performance improvements in certain conditions). Enjoy!

Release RuboCop 1.40 · rubocop/rubocop

New features #11179: Add Style/ConstantBase cop. (@r7kamura) #11205: Add --[no-]auto-gen-enforced-style CLI option. (@ydah) #11224: Add Style/RequireOrder cop. (@r7kamura) #11219: Make Style/Selec...

GitHub

Show thread

Bertocq Dec 7, 2022

I know this kind of work might seem trivial, or low value, but it brings me lots of joy to automate these kinds of things so both author and reviewers can focus more time on test quality & coverage.

Show thread

Bertocq Dec 7, 2022

Maybe one day I'll find the mental energy to write an article about this, but for anyone interested the process to add it to an existing codebase was:

1- Install codespell locally fix all trivial/obvious typos (mostly code comments)
2- Temporary ignore words & files that represented some doubts, with codespell config.
3- Once codespell runs ✅ on the codebase... Add codespell to the CI checks (assuming you can't merge with a broken one)
4- One by one review ignored files/words

Bertocq Dec 7, 2022

Thank you very much @bbatsov for this article about automating Spell Checking https://metaredux.com/posts/2021/11/26/automate-spell-checking-in-your-projects-with-github-actions.html

It wasn't a direct copy&paste but rubocop's repo version is 👌 https://github.com/rubocop/rubocop/blob/master/.github/workflows/spell_checking.yml#L9-L27

Nice quick win on the code review automation front :)

Automate Spell-checking in Your Projects with GitHub Actions

A couple of years ago I wrote an article about dealing with typos in your source code. Today I’ll follow up with a simple recipe to automate this spell-checking process using GitHub Actions (GHA).1 Lately I’ve been adding the following GHA workflow to all of my OSS projects: name: Spell Checking on: [pull_request] jobs: codespell: name: Check spelling with codespell runs-on: ubuntu-latest strategy: matrix: python-version: [3.8] steps: - uses: actions/checkout@v2 - name: Set up Python $ uses: actions/setup-python@v2 with: python-version: $ - name: Install dependencies run: | python -m pip install --upgrade pip pip install codespell if [ -f requirements.txt ]; then pip install -r requirements.txt; fi - name: Check spelling with codespell run: codespell --ignore-words=codespell.txt || exit 1 misspell: name: Check spelling with misspell runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Install run: wget -O - -q https://git.io/misspell | sh -s -- -b . - name: Misspell run: ./misspell -error There’s nothing fancy here. We’re just installing a couple of popular spell-checkers for code and we run them on everything within the Git repository. If they discover any problems the build will fail. Just save the code above under .github/workflows/spell_checking.yml and you’re good to go. The workflow will get triggered for each subsequent pull request. A couple of things to note: This workflow uses both codespell and misspell. Using both might be an overkill for some of you. Personally, I like misspell more, as it’s super fast. It’s a good idea to run both tools locally first and address any existing typos. You may want to limit the checks only to files that were changed in the pull request. You may want to specify a locale for misspell if you want to enforce a specific flavor of English (e.g. misspell -locale US). This should probably be made a reusable workflow. I won’t be surprised if someone actually has created a public reusable workflow for spell-checking code already. That’s all I have for you today. Big thanks to my fellow OSS hacker Koichi Ito, who came up with the idea of making spell-checking a CI step. In hindsight it seems like a very obvious thing to do, but it was always an afterthought for me. I’d be curious to hear how others are dealing with typos in their codebases. The outlined approach can easily be adapted for any other CI. ↩

Meta Redux

Show thread

Bertocq Nov 20, 2022

Seen most of those join mastodon, gives me both happiness and also the energy to think that writing again is going to be worth my time :).

I try to be more active for you to also stay here. Hopefully I'll find again the courage that once @raulmurciano almost inspired me to write about Comments in Code and other well formed opinions I've got

Thanks all 🤗 and welcome!

Bertocq Nov 20, 2022

I joined mastodon in 2018, can't even remember which drama started that small migration.

It felt right to join an instance focused in my interests (Ruby) but I couldn't find back then one about cycling.

But most of the people that I wanted to read about remained at twitter so I was forced to stay there... but I did it 99% silently

Bertocq Nov 8, 2022

Simon Willison Nov 8, 2022

Wrote up an analogy that I've been finding really useful in helping me (and I think others) understand Mastodon:

Mastodon is just blogs

https://simonwillison.net/2022/Nov/8/mastodon-is-just-blogs/

(Extended version: Mastodon is just blogs and Google Reader, skinned to look like Twitter)

Mastodon is just blogs

And that’s great. It’s also the return of Google Reader! Mastodon is really confusing for newcomers. There are memes about it. If you’re an internet user of a certain age, …