home.social

Search

1000 results for “DrHyde”

  1. I've been playing with as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value , , etc. I agree that some ways of using for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

  2. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  3. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  4. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  5. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  6. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  7. Grargh! hates extensions. And can't be configured to specifically use instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

  8. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  9. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  10. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  11. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  12. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

  13. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  14. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  15. I got annoyed at having to know how many lines I want to `head` or `tail`, and having to write the same stuff over and over again using `cat -n` / `grep` (or even worse an awk script) to figure them out on the fly, so ... two new scripts, `ignore-after` and `ignore-up-to` which are basically content-based versions of `head` and `tail`.

    You're welcome.

    github.com/DrHyde/shellscripts

    #ShellScripting #shell #unix

  16. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the format which is standardised in ITU-T . The request is in Github issue 164!

    github.com/DrHyde/perl-modules

  17. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the #MSISDN format which is standardised in ITU-T #E164. The request is in Github issue 164!

    github.com/DrHyde/perl-modules

    #perl #telecoms #ITU #SpookyCoincidences

  18. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the #MSISDN format which is standardised in ITU-T #E164. The request is in Github issue 164!

    github.com/DrHyde/perl-modules

    #perl #telecoms #ITU #SpookyCoincidences

  19. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the #MSISDN format which is standardised in ITU-T #E164. The request is in Github issue 164!

    github.com/DrHyde/perl-modules

    #perl #telecoms #ITU #SpookyCoincidences

  20. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the #MSISDN format which is standardised in ITU-T #E164. The request is in Github issue 164!

    github.com/DrHyde/perl-modules

    #perl #telecoms #ITU #SpookyCoincidences

  21. I've been playing with . It seems nifty, but if I'm going to use it to get notifications from a job I want more reliability - I want cron to email me if there's an error sending the notification. And so I wrote a thing: github.com/DrHyde/shellscripts.

    After pushing I noticed some dead code, left over from an earlier version. And I noticed the "ask " thing on Github. So I asked it if all the code was reachable. See follow-up for the impressive results.

  22. Re earlier toot ... as soon as I'd finished dealing with 's PRs, I wanted to use the script to view other peoples' PRs against my code (there are only two that I've not dealt with because I'm a good boy, although one has been festering for 7 years because I'm a bad boy), and then to see all my PRs against other peoples' code that are still open. And so the script got just a teensy bit bigger.

    github.com/DrHyde/shellscripts

  23. RE: fosstodon.org/@DrHyde/11577485

    Arising from this ... overnight, shat approximately 15,000 pull requests at me, all of which I needed to look at. I could have written a small script to parse them all out of my mailbox, but a script that uses 's CLI tool and API is always gonna be more reliable. github.com/DrHyde/shellscripts

    Version 2 might save me having to look at them, by only showing me PRs which touch unexpected files or have test failures, and just auto-merge the rest. Need to look at the API in more depth.

  24. @DrHyde On behalf of us all, I apologise for our failure. You are right, that is very lax from us.

    I, of course, will be indulging in lots of during the coming weeks.

  25. Re earlier toot (fosstodon.org/@DrHyde/11517952) the release was further delayed by being bastards and breaking my CI by not letting me grab their data from within workflows, so I had to work around that. So that's more crawling horrors accreted onto the 20 years old that builds it all. Yay! But we have a release! The only changes are data updates and a tweak to cope with the 's new weirdness.

    @perl