The main problem I run into with git is communicating with my teams about editing history and how they shouldn't.
Particularly on teams that like to keep main clean and avoid reverts and merge commits in favor of rebasing. Thankfully my current team likes to keep their PRs clean and main is whatever works.
That and merge conflicts, especially on a stale branch. I use cli for most things and Intellij's merge tool for merge conflicts because I can get a clear view of what's what.
Police already publish arrest records, mug shots, and they're covered by the media as well. Criminal charges are public records and covered by FOIA requests.
Colleague #437: "So whoever first set this up has left, so I'll just follow the documentation they left to figure out what they did... Oh. ...eh, I got a deadline."
A VPN isn't itself secure. It's only a secure tunnel. If the VPN's exit is insecure, then you're insecure. DNS-Over-HTTPS hasn't reached ubiquity yet but VPNs are very useful but are having a reckoning with serverside attacks and governments demanding "oversight" and backdoors (like the recent move by China on foreign owned but China-located companies VPN usage).
The CEO of SpaceX did commit a couple crimes in the same podcast.
Uber's autonomous car fatally collided with a woman, raising questions of negligence and liability in automation.
Uber acquired some of Alphabet/Waymo's trade secrets when they aqui-hired one of their former engineers who apparently kept a bunch of Waymo's IP he worked on. That engineer himself is now facing a federal indictment, and Uber and Waymo have settled.
E-scooters are facilitating a number of city-specific crimes (it's usually illegal to operate a vehicle, bike, or skate on a city sidewalk and the e-scooters do not provide helmets but neither do the riders). To say nothing of the legally dubious use of public property to deploy them.
Let's keep in mind that this is an end user application for pixel artwork. You and I might care that it's Rust. End Users will not. It could be written in Malbolge or BF for all an end user cares about.
Namespace collision is gonna be a pain for end users and newcomers, possibly depressing discovery, which is our point.
which is why you want more tracing and less logging.
log messages are always an art and I myself am a poor artist when it come to predicting what is both necessary and useful enough to log without overall increasing the log noise.
Tracing will show you the distributed behavior, but the best log, at most, can only show you the current state of information on a single service on a single node even when you aggregate. Tracing also works hand in hand because the correlation id should associate with the relevant log message when you do decide to drill down.
If you need it for work and are not an independent contractor then should pay for it.
BYODTEI
BYOD are a cost cutting measure by the office, but if you buy a second device then the cost isn't cut, it's transfered. To you. So congratulations on your pay decrease.
Particularly on teams that like to keep main clean and avoid reverts and merge commits in favor of rebasing. Thankfully my current team likes to keep their PRs clean and main is whatever works.
That and merge conflicts, especially on a stale branch. I use cli for most things and Intellij's merge tool for merge conflicts because I can get a clear view of what's what.