Leetcode is a great way to polish your skills. When I was your age, I read programming books and made projects I cared about, it's turned out very well.
I've helped a few others learn programming, practice and working on any project at all always help more than anything.
The real example of a health check trait really brings this issue to life, it's linked within op's article as well
Is this a reasonable summary?
Say you want a trait where a method returns a task that you would like to sometimes run within your own thread and sometimes move it to a separate thread to be executed, that means the Send constraint isn't necessary to add to your trait but it would be nice to add that constraint within another method's parameter definition so that it can accept structs that implement the trait and further constrain that implementation to be Send'able. That's now possible with this new rust language feature, though it was previously possible through a crate, now it's no longer needed.
That's really the foundational problem. If you could exist without bugging or being bugged by the neighbors dense housing would be so much more appealing
If they are failing to debunk a known fact, perhaps a conspiracy theorist?
If they are going against the grain, the devil's advocate?
Looks cool, when was the last time Zelda was a playable character in a mainline Zelda game?
No I mean how is trump involved with this post?
Perovskite isn't new in the solar world but considering it a coating seems to be, it's not used today primarily because it degrades much quicker than silicon based cells, as of 2022:
the maximum lifetime attained by perovskite solar cells is just a year while it is about 25 years for the Silicon solar cells
For the sake of external consistency, seeking a problem to fit the solution:
It seems like there's relatively little on the ship in the way of rotational mechanics, doors make a pneumatic sound, etc. Perhaps the equipment is highly EM sensitive? Like the electromagnetic waves from a motor could screw then up somehow kinda like electrostatic issues in a computer?
I still remember flipboard being forcefully installed as the action button app for an old phone. My rage continues to smolder a decade later.
An app that couldn't be uninstalled and took up precious resources. That's all they'll ever be to me.
Just collect your tears and pour them over the tree, plenty of salt coming out of you
Harris has me profoundly optimistic. She's the most qualified candidate I'll have had the chance to vote for in my lifetime.
Walz is fine, I was keen on Buttigieg but I'll happily vote for Walz and let Buttigieg keep his important current position.
My biggest hope is that Kamala will draw out some of the less extreme right leaning women, nobody needs to know that they're voting for the better candidate and God knows women need allies with the ongoing barrage.
This election cycle is not about fear for me, Harris is an easy candidate to vote for!
I explained a little about buffer overflows, but in essence programming is the act of making a fancy list of commands for your computer to run one after the other.
One concept in programming is an "array" or list of things, sometimes in languages like C the developer is responsible for keeping track of how many items are in a list. When that program accepts info from other programs (like a chat message, video call, website to render, etx) in the form of an array sometimes the sender can send more info than the developer expected to receive.
When that extra info is received it can actually modify the fancy list of commands in such a way that the data itself is run directly on the computer instead of what the developer originally intended.
Bad guy sends too much data, at the end of the data are secret instructions to install a new program that watches every key you type on your keyboard and send that info to the bad guy.
There is a ton of literature out there, but in a few words:
Rust is built from the ground up with the intention of being safe, and fast. There are a bunch of things you can do when programming that are technically fine but often cause errors. Rust builds on decades of understanding of best practices and forces the developer to follow them. It can be frustrating at first but being forced to use best practices is actually a huge boon to the whole community.
C is a language that lets the developer do whatever the heck they want as long as it's technically possible. "Dereferencing pointer 0?" No problem boss. C is fast but there are many many pitfalls and mildly incorrect code can cause significant problems, buffer overflows for example can open your system to bad actors sending information packets to the program and cause your computer to do whatever the bad actor wants. You can technically write code with that problem in both c and rust, but rust has guardrails that keep you out of trouble.
How much of your nose can you see? This is my POV
I wonder if there's anyone out there who can't see their nose at all?