@Mng64218162@ex0t1clol@letstri You sound tone deaf. Let's assume what you're saying is right, what's wrong with that? Just why must someone do something without any intention of making money to begin with? Even to sustain "loving people" and "loving open source", a financial handle needs be maintained.
Sometimes I get depressed thinking that I won't be able to program in my 60s. But today I've watched first Sean Barrett stream back, and seeing him effortlessly benching code that's way above my pay grade made me very happy. I just need to lock in!
@MuthaNagavamsi There comes a point when you have so many closed networks that trying to distinguish ranges by something as abstract as frequency of use across unrelated systems across the whole world, becomes futile. And it just confuses folks starting out in an already confusing industry (2)
@MuthaNagavamsi Idk what parameters here is defining a private range to be more secure inherently. But my main point is the advice to change to an uncommon (which btw idk how one would know) range has no real roi. And juniors tend to take it at face value and waste effort and time. (1)
I disagree. Frontend you get dopamine hits and instant feedback. It's not the same for backend... and you rarely get recognition as a backend dev ^.^ not to mention with SPA,SSR && hybrid approaches you can nearly do it all on either the front or back, BUT would you rather build a parser, compiler, or a button? Me? I want to do it ALLLLLLLLLLL
Today, Linus Torvalds told a Google engineer that his code (updating RISC-V support in the Linux kernel) is “garbage” which “makes the world actively a worse place to live”.
Adding that the Google engineer’s code needs to “get bent”.
As you might have guessed, Torvalds has rejected that code submission.
@MuthaNagavamsi Worst mistake I see people make, is assuming the best because they made software "scalable" off of zero metrics. Unless it's a solved problem, then there's no point in discussing this to begin with.
@MuthaNagavamsi I try to stay away from anything fancy. Anything, including fancy words (they have an impact on directions believe it or not). It's a journey, good metrics, adjustments over time, start with the worst assumptions, throttle but don't crash (although this is a wishful thinking).