Why the fuck would you go for Backend in C++ and frontend in Java 🤣 just the wrong way around

Of course there’s a best solution… it’s whatever you end up with

Even with the external mind it’d be irrelevant. As long as we have no way of knowing the future or being able to predict it, having or not having free will is observed in exactly the same way.

I just kinda wonder why when you’re in a browser or node, you wouldn’t just do

const json = {...};
json.friends.filter(f => f.age >= 18);

why learn another language when you already literally got the language to process JavaScript Object Notation right there.

https://jqlang.org/

I’ve been using that for all my JSON extraction and processing needs. Let me automate a bunch of my builds for JS stuff for FoundryVTT https://gitlab.com/foundry-azzurite/pings/-/blob/master/build/build.sh

Setup an autocorrect phrase :D

I think what people mean when they say this is that they are looking for the same price point as the equivalent Windows device… I don’t know all these companies but every time I looked for a Linux PC/laptop it was 25-30% more expensive than the equivalent Windows thing.

Ideas are incredibly cheap. It’s absolutely unlikely that no one ever had your idea. It’s even likely that someone had your idea and it failed, and you don’t/can’t even know about it because no one bothered to record the failure.

Other people have mentioned all kinds of ambitious/proper ways to do this. I’ve got a different view: if you truly think this will work, do a basic version yourself.

Learn basic blender, design 3D printed parts yourself and let someone print them. Use some app builder and tutorials, or hire a programmer for a very rudimentary prototype work. Buy generic electronics. Just get it working once. Then show it to people, let them use it, ask if they would buy it, preferably let them sign a slip of paper not to talk about this product or compete with it (there are standard NDA/non-compete contract clauses online available) or talk to people you can trust.

If you do all this and get positive feedback, then you can start doing this properly and get more people on it, like the other commenters mentioned.

No. Just no. You’re talking about perfectionism basically. Who cares about continuing maintenance? If you get the product out there and working enough to last the 2 years warranty, you’re completely fine. One programmer is perfectly capable of learning the most basic things about the disciplines you mentioned, it doesn’t need to be good, it just needs to do its job mostly.

You have no clue about the scope of what this guy’s idea is since he gave no info. Maybe it’s so simple not even one programmer would have to work on it for very long.

Of course, what you say is perfectly possible to be “correct”, but you just have no way of knowing.

What’s wrong with cksfv?

You’re the one who brought up runit and insinuated it doesn’t have this problem ¯_(ツ)_/¯

I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.

systemd moment in the sense that someone not affiliated with systemd used systemd to write a stop job that doesn’t terminate quickly? Or that you willingly installed software that brought along a slow stop job with it?

This is like so far away from systemd’s fault, idk, it must just be a meme right?

Oh and as for reasoning why, another few points, all projects I’ve been in just kept being worked on and had constantly changing requirements. There was no real need to plan very much except maybe some rough estimations, that were allowed to be wrong.

There were like some very rough aspects of scrum in professional development, but only in the sense that we’d talk about what we’d like to do in the next sprint, we didn’t do multiple plannings or estimations or cared about our velocity or did retrospectives often, and even the sprints were adjusted to last longer or shorter based on what we’re going to do, there were a couple of roles people should have missing, and idk what. In the end, the resulting system was just something in the direction of agile/kanban, work just came in, and was handled based on some prioritizing by someone.

My personal projects could be really close to waterfall as well, I thought about a problem, made a rough plan on how to solve it, then just kept solving until I was done. Open source projects, no one organized anything, everyone just works on whatever they like.

Basically, you’re the expert in software development paradigms, I’m just a developer that works on problems with code until solved, either given to me by someone or myself. The only ones who care about the paradigm are the business guys who wanna plan some shit.

The paradigm in my work life I followed most of the time on most projects is “do whatever the project manager decides is important at the moment”. I’m not aware of it having a particular name. Technically, they might call it scrum or something else, but really it’s not even close to any of these labels. It really was always just “whatever sounds good to them at the time”. I guess you could call it “agile”, but not by choice necessarily. Please ask more questions on this or provide more options for me to choose if you want a better answer.

On my personal projects, I follow the “start programming and see what comes out at the end of it” paradigm, I’m also not aware of it having a particular label.

Edit: sorry other questions. Type of software is desktop application, web applications, browser extensions, game modifications. And for why these particular paradigms were chosen, they were chosen because a customer/user wants to be happy and doesn’t care about what paradigm is used, only the result. As such, the paradigm essentially follows some humans’ whims, which mostly doesn’t make sense and definitely is nothing “formal” at all.

Sure, I’m not unreasonable. I hate against exclusives, because I’m sure it’d be better without them, but Nintendo is not entirely terrible. It’s never completely black & white.

Yep. But aren’t we glad we have competition! Aren’t we glad we duplicate research/work all the time! We’d never think of improvements without this.

Exclusives are cancer. Computers should be able to compute everything. Nintendo’s/console strategy is an absolute travesty for human progress, like almost all capitalist strategy.

Lemmy is tech-minded, there are safe spaces for trans people. You can basically do the math.

You’ve already taken the first step. You want to.

This is not some thing you can just adopt whenever you want, like putting the plates on the right side of the dishwasher instead of the left. This will require some serious continuous practice.

Basically, to retrain your reaction to things, you must 1. understand why your current/natural reaction is undesirable 2. understand which reaction you think is desireable 3. Repeatedly expose yourself to the situation that triggers your reaction with the main goal to change your reaction.

1. and 2. requires you to continually remind yourself of these beliefs. You will forget when you slip back into your natural reaction.

3. is not easy. You can’t just manufacture adversity. It has to be real. It’s very easy to have a specific controlled reaction to something fake. So essentially, you just continue as normal, risk things, always keeping in mind that you can face adversity. You mentally prepare yourself for it so you can notice when it happens. “When I start this new job, people might be offended when I tell them I don’t want to talk to them. That is fine. I accept that they can be offended, because rejection is not a nice thing to experience, and that is what I do to them. However, I prefer this to having to suffer through their rambling. I know that this will likely cause them to help me less or actively oppose me, and I am fine with that outcome.”…

And then you just do it anyway. When your setback happens, you will first feel frustrated. But then eventually you will get a rational moment. See what is happening to you again. And then you can remember what you’ve been thinking so far. That it’s ok for this to happen. That being frustrated by it achieves nothing. And whatever else you figured out with 1. and 2. Each thing you remember should help you let go. Taking deep breaths and other relaxation techniques help with letting go.

And the result should be that you’re slightly less frustrated, for a slightly shorter time than you would’ve been without doing all this. It’s still essentially the same strength the first time, but it should be a little less.

And then you have another disappointment. That time, doing the same thing, it should sting even less and for even shorter. And so on and so on.

For me, I’m not sure how long and how many things it took. I know it was quite a few and over quite some years. Now, when I feel this frustration, it’s just a slight tinge for a few seconds at most, when I remember what I believe and that I’m fine with this, and then I can already completely let it go. Like others said, it’s a completely natural reaction, you might still feel like that. But eventually you’re so good at letting go that it takes mere seconds and then you’re completely fine.