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/)T
Posts
1
Comments
119
Joined
5 mo. ago

  • if you know how to write decent C, you'll have a much easier time of understanding PostgreSQL internals, for example, while if you've learned React, it's anyone's guess as to whether or not that'll actually improve your HTML skills, for example.

    I mean, there's also a much more mundane reason why C comes up more often: It doesn't use a runtime environment, so a library written in C can be called from virtually any programming language.

    For the longest time, if you wanted to write a cross-language library, C and C++ were pretty much your only choices.Rust is now entering that circle and I do think, it will start showing up in lots of places, too.

    But perhaps another reason why mastering C is more educational than mastering other languages, including Rust: C hardly abstracts from how the hardware works, so you're not just mastering C, you're also mastering hardware.

    Other programming languages ultimately get executed on that same hardware as well, even if lots of abstraction layers are in between, so that knowledge still keeps being relevant every so often.

  • I like how they have a thicker piece of wood for holding up the roof than for holding up the deck + roof.

  • Deleted

    Permanently Deleted

    Jump
  • And now it's nogamy.

  • Figured out why cross-compilation for Windows wasn't working. So, now there's release binary available for that, too.Completely untested, good luck.

    Cross-compiling for macOS is prohibited by Apple, so even more good luck to you guys. 🫠

  • Yeah, I thought the blog post was gonna be about horror stories, because even the greatest senior/architect/whatever will push absolute garbage into your codebase, if they don't have the time to familiarize themselves with how the code actually works.

    Even if it's some isolated component, if they implement it without explaining the what and why to others, then no one else can maintain or debug that. And you do not want to rely on your super important guy to have the time to fix things when production grinds to a halt.

  • One time I was in the next town over where they have a grocery store chain that I can't normally shop at. So, I figured I'll get the big shopping cart and grab everything that looks interesting.

    Went through the whole store and in the end, I stood at the checkout with a pack of cookies and some vitamin tablets. That almost felt worse than walking out without buying anything. It felt like I was insulting their product selection.

    Although, to be fair, it was absolutely terrible.

  • Personally, I've kind of given up all structure.

    I have a script that creates a Markdown file with basically just the date in the file name and then it opens it in my text editor. All Markdown files are in one big folder. Notes, todos etc. all go into the there.

    So long as a file is open in my text editor, it's actively relevant. Afterwards I'll use full-text search (like grep -iR), if I need something again.I will often specify a title in the Markdown, but mainly because it's a great place for keywords to make the file easier to find again. It's also my way of tagging the files.

    I mainly like this way of working, because I spend very little time on inputting information, which I do way more often than retrieving information (at least for the files which aren't actively open in my text editor).But I've also never used a structured approach for more than a few months without it turning into chaos, where full-text search is the only option anyways.

    Maybe this would be different, if my tasks were more structured. Your mileage may vary. ¯(ツ)_/¯

  • Oh man, I just woke up in the middle of the night, and in perhaps most definitely a stupid move, I immediately grabbed my phone and continued scrolling Lemmy.

    This post's title was the first thing I read, within like 10 seconds of waking up, and I didn't yet clock the actual sentence, but my brain still went "Wait, what?" when I read "Islamic Republic of Japan".

    So, apparently still more awake than Trump is in the middle of the day...

  • Oh, hmm, no idea. I certainly wouldn't put it past them to choose even more confusing naming, though...

  • You're doubly confused. You're thinking of GitHub Copilot, when this is about M365 Copilot. Last I heard, they have 78 different products called Something Copilot, so confusion is understandable.

    But then what you're actually thinking of is the "GPT" series of large language models, developed by OpenAI.GitHub Copilot is merely a GUI and a harness for large language models. It defaults to the GPT models, and is probably somewhat optimized for them, but it can use other models as well.

    This harness can influence the quality quite a bit, as it decides which source code files to feed into the model for context. I'm not aware of people saying that GitHub Copilot is particularly good at that, but it's available as an extension for IDEs, so it automatically knows which files you're editing, which can be useful.

    And yes, the GPT models have fallen quite a bit behind since the start of the year.

  • Yeah, that's why I got caught up on that sentence in the first place, to be honest, because I also thought to myself "What impact does Meta even have?".

    I guess, they do own some widely used messengers and social media platforms. But yeah, all the stuff Zuckerberg loves to talk about, is just hype bullshit, where they seem to have zero impact.

  • Meta’s north star is to be the best place for the most talented people in the world to make an impact.

    Not a positive impact, just an impact.

  • To be fair, lots of SaaS could'be been improved by instead just checking some Markdown files into Git, independent of LLMs.

  • Might also be a product of experience, that you have a need for strict scope definitions.

    When I was unexperienced, I would actively look for projects I could do and features to add to them. Because well, most project ideas were too large for me to tackle anyways and I needed the experience.

    Now that I have experience, I have multiple long-term projects that could use some love, if I find the time. And I have the experience to tackle virtually any project idea, if I find the time.

    Don't particularly want to add another long-term project into the rotation, so I do spend a lot more time thinking upfront "when will this be finished?".

  • One of the big, national grocery store chains here has managed to create a webpage, where:

    • you cannot open a product in a new tab, and
    • if you click on a product and hit the back-button, it resets the scroll position in the product list all the way to the start.

    In effect, the webpage is practically unusable for actually browsing through products. They're probably missing out on hundreds of thousands in sales, for something that could be fixed for like 50 quid.

  • Well, I just meant it was like bee hotels in that it's a product you can buy to help out critters. I did think it was food, as "buffet" suggests.

    Whether food is meaningfully helpful for ants, no idea. Did not overthink it too much in the few seconds until I realized it was poison. 🫠

  • Found some "ant buffet" in the shop a few months ago and thought "Oh wow, did people learn that those are dying as well and you can buy something like bee hotels for them now?".

    Yeah, it was poison.

  • Yeah, for folks with previous programming experience, I generally recommend the Rust CLI book, particularly the first chapter

    It makes you build a small, usable program and shows you concrete ways to handle some intermediate topics, like error handling, unit tests, bundling etc..