If the time is off by that much after being powered off, this tells me two things:
An incorrect clock can absolutely cause network issues, so I would bet that’s what is causing you trouble
Why are you using networkd instead of networkmanager on a desktop?
What a weird question. Networkd works anywhere systemd works, why whould desktops be any different.
It’s the same as asking someone “why are you using systemd-boot instead of grub?” Because I like systemd boot better and it’s easier to configure. Same with networkd, configuration is stupid simple, I have installed it on my work machine even.
As for op: since you can manually ping ip addresses and the issue seems to be time-based, could it be that your machine is somehow not renegotiating a dhcp lease?
Don’t know why you are getting downvoted, it’s absolutely true. Raw specs these days mean relatively little. With smart frequency boosts that vary with thermals, CPU and GPU on the same package, different workloads stressing different components differently, RAM bandwidth playing different roles for CPU and GPU applications, and many other factors, just stating that the M4 has so and so many cores is practically useless.
The only real way to gauge performance differences is via benchmarks and measuring sustained workloads.
I plan on doing the same. Do you happen to know if it’s possible to pair multiple xbox controllers via bluetooth out of the box? If not out of the box, I’m also ok with it requiring tinkering, as long as it’s somehow possible
Im my defense, I did test it. It was working for me.
But then someone else touched it without understanding it or flipped the truth value returned by one of the functions used by my code without properly fixing the call sites.
Edit: or they had a merge conflict and they don’t know how to correctly resolve those.
That’s not enough, a better idea is to, somehow, poison the location data. Otherwise by disabling location tracking you still leak the information that you are going to a clinic.
I had an issue where the desktop would take a fair amount of time to load, and I have a very different issue that I don’t even know how to categorise. There’s a wayland app in which keyboard works but some keyboard related things stop working if I lock my screen.
The app is a game (Victoria 3). Normally, space pauses / unpauses the game, escape opens the pause menu, etc. If I lock my screen, those things (and more) stop working, but the keyboard as a whole works. E.g. if I go to save the game I can input text in the save name text field. Keyboard and keyboard shortcuts as a whole still work everywhere else.
The problem goes away if I log out and log back in, but otherwise persists across game session (i.e. closing and reopening the game doesn’t fix it).
Yeah that’s what we did last time. I implemented a basic framework on top of a very widespread system in our codebase, which would allow a number of requested minor features to be implemented similarly, with the minimal amount of required boilerplate, and leaving the bulk of the work to implementing the actual meat of the requests.
These requests were completely independent and so could be parallelized easily. The “framework” I implemented was also incredibly thin (basically just a helper function and an human instruction in the shape of “do this for this usecase”) over a system that is preexisting knowledge. My expectation was to have to bring someone up to speed on certain things and then let them loose on this collection of tasks, maybe having to answer some question a couple times a day.
Instead, since the assigned colleague is basically just a copilot frontend, I had to spend 80% or more of my days explaining exactly what needed to be done (I would always start with the whys od things since the whats are derived from them, but this particular colleague seems uninterested in that).
So I was basically spending my time programming a set of features by proxy, while I was ostensibly working on a different set of features.
So yeah, splitting work only works if you also have people capable of doing it in the first place. Of course I couldn’t not help this colleague either, that’s a bad mark on performance review you know. Even when the colleagues have no intention of learning or being productive in any way (I live in a country with strong employee regulations so almost nobody can be fired for anything concerning actual work performance, and this particular colleague doesn’t hide that they don’t care about actually doing a good job, except to managers so they still get pay raises for “improving”).
Yeah, you can tell I’m unhappy
who is actually stopping them from dealing with it?
Management. Someone in management sets idiotic deadlines, then someone tells you “do X”, you estimate and come up with “it will take T amount of time” and production simply tells you “that’s too long, do it faster”
they don’t care about the details or maintenance
They don’t, they care about time. If there are 6 weeks to implement a feature that requires reworking half the product, they don’t care to know half the product needs to be reworked. They only care to hear you say that you’ll get it done in 6 weeks. And if you say that’s impossible, they tell you to do it anyway
you have to include the cost of managing technical debt
I do, and when I get asked why my time estimations are so long compared to those of other colleagues I say I include known costs that are required to develop the feature, as well as a buffer for known unknowns and unknown unknowns which, historically, has been necessary 100% of the time and never included causing us development difficulties and us running over cost and over time causing delays and quality issues that caused internal unhappiness, sometimes mandatory overtime, and usually a crappy product that the customers are unhappy with. That’s me doing a good job right? Except I got told to ignore all of that and only include the minimum time to get all of the dozens of tiny pieces working. We went over time, over cost, and each tiny piece “works” when taken in isolation but doesn’t really mix with everything else because there was no integration time and so each feature kinda just exists there on its own.
Then we do retrospectives in which we highlight all the process mistakes that we ran into only to do them all again next time. And I get blamed come performance review time because I was stressed and I wasn’t at the top of my game in the last year due to being chronically overburdened, overworked, and underpaid.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
“They’re both for monsters”