deleted by creator
deleted by creator
So, I’d argue that “frontend” and “backend” are the default modes of software engineering these days, and that embedded is a more niche field.
That said, if you’re doing encryption code, you’re doing far more advanced math than backend monitoring and alerting.
You often need to be pretty good at math. But not because you’re “doing math” to write the code.
In real world software systems, you need to handle monitoring and alerting. To properly do this, you need to understand stats, rolling averages, percentiles, probability distributions, and significance testing. At least at a basic level. Enough to know how to recognize these problems and where to look when you run into them.
For being a better coder, you need to understand mathematical logic, proofs, algebra/symbolic logic, etc in order to reason your way through tricky edge cases.
To do AI/ML, you need to know a shitton of calculus and diff eqs, plus numerical algorithms concepts like numerical stability. This is kinda a niche (but rapidly growing) engineering field.
The same thing about AI also applies to any other domain where the thing being computed is fundamentally a math or logic solution. This is somewhat common in backend engineering.
I’m not “doing math” with pen and paper at work, but I do use all of these mathematical skills all. the. time.
I am an SRE on a ML serving platform.
So they tried to open a research center to steal Chinese talent (that has since been closed) and they released the Google Translate app on the Xiaomi store…
That’s not the same as supporting the CCP and the Uyghur genocide.
deleted by creator
What are you talking about?
Google doesn’t operate in China, much less do work for the CCP.
“Getting fired felt like a possibility but never a reality,”
They took over an executive’s office and a cafeteria. Not knowing that you’d be fired as a result is a severe lack of judgement.
Protests are important. But you have to understand that there will be consequences for your actions. Embrace that going in.
Saying that you didn’t think they’d actually fire you comes off as childish.
My money is on cousin Greg to take over.
Phone cameras tend to ramp up the saturation.
It gives the photo a more vibrant look, which many people prefer, at the expense of color accuracy.
But generally with artistic photography, you’re going more for a style than for accuracy, so I wouldn’t say it’s always a bad thing (though sometimes it is).
Great photo. Actually, is this a photo?
TIL. Thanks for the correction.
\1. Many retro games were made for CRT TVs at 480p. Updating the graphics stack modern TVs is valuable, even if nothing else is changed.
\2. All of my old consoles only have analog A/V outputs. And my TV only has one analog A/V input. The mess of adapter cables and swapping is annoying. I want the convenience of playing on a system that I already have plugged in.
\3. I don’t even still have some of the consoles that play my favorite classic games, and getting retro hardware is sometimes difficult. Especially things like N64 controllers with good joysticks.
Studios don’t need to do a full blown remake to solve these problems. But I’m also not going to say the Crash and Spyro remakes weren’t welcome. Nintendo’s Virtual Console emulators toe this line pretty well.
But studios should still put in effort to make these classic games more accessible to modern audiences, and if that means a remake, that’s fine with me.
(I’m mostly thinking about the GameCube/PS2 generation and earlier. I don’t see much value in remakes of the Wii/PS3 generation yet.)
What’s wrong with AC if it’s powered by renewable electricity?
Someone told me that Goldeneye actually supported dual stick controls if you plugged in two controllers. And Perfect Dark is the same engine.
I need to try that out on real hardware…
Huh. This got me curious.
Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.
So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>
.
So yeah \shrug.
https://spec.commonmark.org/0.31.2/#autolinks
Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.
I intentionally added a period because it was the end of a sentence.
If your Lemmy app messed it up, then that’s a bug in its markdown parser.
With a good style/best-practice guide, C++ can be quite productive of a language to work with.
Those kinds of guides typically define which standard/convention to use and which features not to use (cough exceptions cough).
I highly recommend Google’s C++ style guide: https://google.github.io/styleguide/cppguide.html.
It’s not like the Dem base will switch their votes to Trump.
At this point, now that the nominees are decided, the political game is to attract the swing vote, which is mostly “tough on crime,” anti-imigration, and anti-taxation (as it applies to them directly).
Even though none of these policies are actually good for those in the middle.
This is a good book on how Google treats production environments at their scale.
Cattle, not pets.
Ha, I see.
Yeah, sarcasm over text forums is sometimes difficult to pick up on.