Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AS
Posts
1
Comments
80
Joined
2 yr. ago
  • I took a compiler course focused on optimization and porting. So I worked with x86 and ARM. There's very little reason in modern computing to write assembly by hand, but it's still useful to be able to read and understand.

  • I was hacking scripts and web shit together in perl, python and php for many years before learning C, and just a couple months learning C/C++ made me understand so many more basic concepts than all previous years experiences combined.

  • Nah, our generation had to tinker with shit to get it working. Kids these days have it easy, which is good from a user perspective, but fails to train them how any of it actually works at a deeper level.

    No one has to install a device driver anymore.

  • It's a beginners book filled with a mix of bad and good advice, which takes considerable experience to separate the two. Those who can point out all the bad advice already don't need the book, and newer developers will pick up absolutely atrocious coding advice. There's simply better books that target beginners better, like The Pragmatic Programmer.

    So when you are on-boarding junior devs that have bought into the clean code/SOLID dogma, you're spending several months beating all their terrible coding habits out of them.

  • There is no dropping out, and there's no replacement. All political donations have been to the Biden campaign, it is illegal to transfer those funds to a new candidate. The only person who could run for president in his place is Kamala, since she is the other person on the ticket.

    It's extremely clear no one talking has any clue how any of this shit works.

  • the tests are now larger than the thing itself

    Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.

    The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.

  • I've programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.

    It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.

  • .NET @programming.dev
    asyncrosaurus @programming.dev

    Moq now ships with a closed-source obfuscated dependency that scrapes your Git email and phones it home

    Also some fun takeaways: it also makes external calls to azure to load configuration and stays silent after updating for 2 weeks before showing warnings.

    Moq is unusable. Needs to be forked or repoaced. Time to switch to NSubstitute.