Ah yes, so bad that the bad character marries someone he groomed, someone he raped, and someone who is described to look like a child.

The show has been written to glorify Rudeus' negative behaviour. In the beginning he's already a repulsive person, but there was potential for a growth arc. And yet, he doesn't. Sure, the show addresses some topics like ED for him to deal with and learn from, but it feels quite limp-wristed - he grows and learns from things that negatively affect himself, not from things that negatively affect others. For example, when finally Rudeus is poised to understand the implications of his actions and the impact he has on other people, he's suddenly just groping the redheaded kid. Rudeus dealing with depression could have been poignant, yet again - panties.

Loli in and of itself is kinda grey area, and as such is tolerable in media. But the combination of Loli with other factors pushes it into the negative. Add on Rudeus being depicted as a good guy during all of this, and it's clear that it's a power fantasy isekai where the repulsive MC might struggle, but gets a happy ending nevertheless. Rudeus might be depicted as feeling bad/apologetic for being creepy, yet he doesn't change. What do you mean he gets to walk free by perving over a figurine with the guard. Or that Eris' father wanted to tie her up with Rudy's bed to gain political standing.

So in short, it was depicted bad in the same way that someone play fighting might go "staahp, noooo".

This looks interesting, though a mighty undertaking. Any reason why not take an existing project and fork it? Or even just an ERPNext module? Would help cover a bunch of potential issues rather than start from scratch. Alternatively, have you thought of what would the MVP be to test it out? That way won't fall into the do-everything-now trap (been there, done that, don't recommend). Also, it looks very US-centric, so not gonna ask about GDPR, data security, etc. Instead, re: FE - for prototyping, don't need design, just functional HTML + forms. Or, can try and poke at some premade or quick-assemble templates. Have you thought about functional (not design) requirements for the user experience, AKA how you imagine the users of this would use it? That is, full day in the office VS checking it once-monthly VS yearly for taxes, etc.

In any case, good luck with your project, I hope it turns out wonderful, and you get all the hype and support 😁

Thanks for elaborating. To me, it looks like you could definitely use an experienced dev-background person to help organise the project. For example, login is low priority imo - it's not needed until you're going into testing. And I mentioned the project being US-focused since I noticed stuff like eligible_1099 in the table design - not a thing outside the US.

Also, I'm working on a project for a non-profit, and as part of it I'm doing an audit trail functionality. Ended up thinking real hard over what's PII you actually need. Turns out, don't actually need to store phone numbers, for example. Makes life easier. And for data anonymisation - if someone makes a GDPR request, then the email gets replaced with a unique hash + @redacte.d, and the IP gets salted + hashed, so that the same IP is the same hash in all entries. This is to ensure continuity in the audit trail, plus if someone gets banned for DDoSing, then does a data redaction request, then tries to access again, they can still be blocked since their IP still matches the hash (same logic as to how passwords work). I'm mentioning it since that's the kind of details that are worth thinking about - however, it's deep down the rabbit hole of details.

Speaking of details, if you're thinking of mobile, then there's also the decision of app VS mobile-friendly site. If you want an app, then it's worth swapping to React right now, since React Native (the framework for creating mobile apps) has a larger community and is more mature. If you're OK not having a native mobile app, then go with whatever, have fun 😁

I asked about the MVP and day to day useage since that can inform you about what order to implement things. As mentioned above, having a login page is lower priority when starting a project. For example, if based on your knowledge and the feedback from existing cooperative(s) shows that the most heavily used functionality is ex. inventory tracking, then it's worth building a good inventory tracking system first, and grow from there. Is also why I mentioned forking an existing project - is a huge project, and if you're going at it solo, it's gonna be painful.

But, there's also alternative to forking - copy-paste. Just like artists use references, developers can also reference existing code. So, for example, I don't know if you've seen this sheet (from this post) for additional info how people think co-ops should work, but it's another piece of info to consider. Though it's Java, you can still take high level structure or direct code inspiration from Adempiere, they've been around long enough to make a bunch of mistakes. There's also a fork of Adempiere, Metasfresh, which is worth looking at re: how things work. Also Tryton, though that one's in Python. Mentioning Tryton since it also uses the party approach, and has an architecture that's worth considering: modularity. Essentially, having the core functionality that ties everything together, and a whole bunch of "modules" that each contain their own logic, SQL, etc.

Which brings me to my last point: it's great to work on a new project, but learn from my mistakes - think of what it would be like to maintain in 6, 12, 24, 60 months. If you tightly couple everything, all things depend on all other things, the system is going to be fragile, hard to maintain, and less likely to be used. With your background I'm sure you're already familiar with trying to update something someone else created in a way that doesn't make sense to you.

So yea, basically, I'm trying to caution you to KISS (keep it simple silly), and not overcommit, lest your project ends up the same way my uncountable exciting startings have ended - in some random dusty git repo, untouched for years, too big or hard or no longer relevant to finish 😅

Still better than some other countries where the more you rape, the higher the likelihood you become a *illionaire, or even a president

I don't get why people are still hyping Mushoku Tensei, not a fan of media that glorifies or supports pedophilia

If you do add visual glitches then remember to also honour prefers-reduced-motion or add a button to turn the wiggles off. For funsies, feel free to poke around this pre-alpha since there's subtle glitching background image, crt scan effect, glitchy text effect, etc.

removepaywall.com to the rescue

TBF with sufficient force and/or velocity you can stab someone with a carrot. Would probably have to pick a softer spot, but still

Pro tip: you know companies get branded shirts right? There are other companies that print/embroider them. And those companies do samples of blank shirts. Look for your local custom print shop 😉

Eh, an half-abandoned project more like 😅

Yea it's why I use the word cycle. In a meeting and the PM says "can we bring this in next sprint?" I reply "not sure about the next cycle, but after that one for sure.". So far I've been subtly nudging multiple people to shift away from using the word sprint

Want that implement in 2015, where you can have a private repo with public access?

And there's also EU CDN that provides fonts: https://fonts.bunny.net/ as an alternative to Google Fonts

Adding source ~/.alias to .zshrc. Is great going gc "WIP" 😁

Also, kanban-lite, and iTerm on OSX / Guake (or its alternative) on Linux. After Sublime and Atom, now have had to settle for VSCode. Recently been trialling micro-editor. Oh, and Firefox Developer + ungoogled-chromium + occasionally servo / links2.

And of course, the most important thing - thermal cup looking like a viking horn for that sweet sweet bean juice.

I use Kiwi Browser on Android, opens the Chrome Dev tools in a new tab, great fun