when running models locally, I presume the models are trained and the weights and stuff are exported to a "model." For example Meta's LLama model.
Do these models get updated, new versions released? I don't quite understand
when running models locally, I presume the models are trained and the weights and stuff are exported to a "model." For example Meta's LLama model.
Do these models get updated, new versions released? I don't quite understand
wow 10 months flew by since this was posted and since then the United States had a surprise privacy bill that is bipartisan that sort of addresses the issues you and I mentioned. https://www.washingtonpost.com/technology/2024/04/07/congress-privacy-deal-cantwell-rodgers/
This bill was proposed around the same time the TikTok ban was announced. I speculate that law makers had a difficult time framing the arguments against TikTok when "the data of citizens have no protections so there was no easy legal grounds to forbit the likes of TikTok to harvest it"
From what I've heard, this bill is pretty good. I need to educate myself more on it, however.
was it ever? I participate in interview rounds at my company (several tech screens a month) and I must say a candidate's email was not something that drew attention
you're able to unsubscribe from all those protomtions . . . that is in settings. Personally, a once-a-month newsletter of everything that is new is helpful bc I don't need to put in the effort tlinto keeping up
For backup and sync I use Syncthing. I can specify which folder on which devices I want to sync to which folder on the server.
I use a folder based gallery on my phone so when I move stuff around on my phone (or on my server) it gets replicated on all my devices.
I also have a policy to sync specified folders (and subfolder) with my family's devices. No more " hey can you send me all the pics from the XYZ trip"
We take a trip. Make a subolder for that trip in a shared folder dump all our pictures there, get home and open the folder on the computer and prune together.
simply put, programming is glorified automation. There are jobs where the process that needs automating makes money.
Debian has the advantage of not using snapd like Ubuntu does. You have to not only remove snaps but also instruct the package manager not you pull in snaps as dependencies and not to favor snap packages.
I have fond memories of Ubuntu being my first distro many years ago but pushing snaps onto users to compete with flatpak is a nuisance.
I don't think I am well positioned to answer that question given my experience. Ill give it my best.
I believe the advantage of more abstraction of gRPC was desireable because we can point it at a socket (Unix domain or internet sockets) and communicate across different domains. I think we are shooting for a "microserves" architecture but running it on one machine. FFI (IIRC) is more low level and more about language interoperability. gRPC would allow us to prototype stuff faster in other languages (like Python or go) and optimize to rust if it became a bottleneck.
Short answer is, we are able to deliver more value, quicker, to customers (I guess). But I don't know much about FFI. Perhaps you can offer some reasons and use cases for it?
At work, we started the c++ migration to rust doing the following:
The challenge here is identifying the subsystems. If the codebase didn't have distinct boundaries for subsystems, rewrite becomes much more difficult
hey, that's what the internet is for; information sharing :)
for the dummies (like me) that can't read the room, especially online, a sarcasm tag /s goes a long way 🙃
Out of college I did not work at a start-up but instead got a job at a "big, stable" corp. I got the following advice from the older engineers at big, stable corp. Some of those engineers are my personal friends 7 years later.
"Why work here where it's slow and stable? You're young, go take some risks, earn money, and most importantly get experience under your belt. Then come back with experience and coast. Your compensation grows slowly here so might as well come in with experience and start with a high salary. Also, everything is slow here, your peers at fast paced companies will out pace you."
That was some of the truest shit I've ever heard. I've since left big,stable corp and am working at a company who was a start-up but opted to grow instead of being bought out. I am working on a family so cannot afford the risks of a start-up.
Yes, I work many more hours but the pay is way better and in the last 1 year I've learned more than i've learned at big,stable corp. There is just much less process and red tape and we are more hands on and wear many hats. At times this is exhausting but I find comfort that if I were to lose my job, I have tangible experience to get hired again where as at Big,stable I was picking up skills how to do reviews on processes and techniques unique to the company.