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/)TH
Posts
2
Comments
124
Joined
2 yr. ago

  • In Omori ::: spoiler Title Mari's death and how it happened - I still feel pressure on my chest whenever I think about it. Since a missclick lead me accidentally to the alternative ending at first, it was even worse... :::

  • Thank you! That's exactly what I need, but I probably have a unique case where I as the developer am the cause for the feature creep myself. For work, luckily our product is an ERP software, so in most cases I'm naturally uninterested for more features :D

  • But I do choose this approach for these problems to not have reusable code on purpose xD I'm not try-harding to rewrite everything for every feature separately, so most of it would be separated and modular, as long as it's required by the initial purpose of the software. However I avoid writing generic and reusable code that only gets rewarded with functional scalability in mind.

    And unit testing is honestly not on my list for these kinds of projects. At best I'd write integration tests to challenge the route handlers. But simply using the software is sufficient to cover the predictably unpredictable usage in these cases.

  • Thanks for the recommendations. A missing understanding of what needs to be reusable could be a problem. E.g. in my example when I add a DAO-like interface just to implement it for the two entities I have, I invite my future self to add unnecessary features to make more use of that interface and other generic components.

  • This is the kind of extreme solution I want to discover with a fitting search term. But personally, I still want to be able to fix bugs and update dependencies. I don't want to lock down the project, but only the features.

  • It definitely is and I wouldn't take this approach mid-way for a project with multiple users and contributors. But it works for my little projects that desperately need me to be the user more than the developer. An example would be a REST API with a few endpoints where the database operations are handled directly in the route handlers uniquely for that specific task.

  • I don't really have a perception of people that like to listen to metal, because that's a huge amount of different people. This definitely did change. I'm not sure, if it was due to my younger age or the strength of genre stereotypes at the end of the 2000s, but at that time I didn't even realize how much of the music I listened to was metal. I associated metal more with the stereotyped metal heads than the actual music.

  • If we're talking about programming language guides in particular, following a guided introduction to a new language was helpful to me, when I was introduced to new concepts and perspectives. And Rust is the best example in my case. Personally I probably would've struggled more and longer in practice without learning about ownership, lifetimes and borrowing in theory first, because it's an essential part of almost anything, even strings, and yet it's not too difficult to understand in theory.

    But at the end of the day, you can start rawdogging it and use the Rust book or any other guide, when you're facing a roadblock. If you do so, please share your experience.

  • It is a problem worth solving. Terrorism is a problem that needs solving and killing all people on earth is a solution. The next question is whether or not it is an appropriate solution to the problem.