Amazing how easy it is to sell the US Gov new toys it doesn't need.
"...ensure the U.S. is at the bleeding edge of next-generation drone warfare."
Translation:
Pay threw the nose for expensive proprietary software that will eventually be made obsolete by it's open-source equivalent.
Google Pixel hardware is focused on providing a private relationship between the user (your data and behavioral patterns) and Google.
Depending on your threat model you can flash custom roms to enhance your privacy and security posture.
A lot of folks here seem to be of the "...just flash GrapheneOS and you're good..." crowd but it's not that simple and there are trade-offs that impact usability and user experience.
There are a lot of interesting projects out there to choose from. Best advice is to work-up your real world threat model and do your reasearch.
You may find Louis Rossman's experience with GrapheneOS relevant: https://www.youtube.com/watch?v=4To-F6W1NT0&t=1
Here's a few links to help get you started - there are many android projects. I am not affiliated nor am I explicitly endorsing any of these projects.
CalyxOS https://calyxos.org/
LineageOS https://lineageos.org/
HavocOS https://havoc-os.com/
ResurrectionRemix https://resurrectionremix.com/
DerpFest https://derpfest.org/
PixelExperience https://wiki.pixelexperience.org/
GrapheneOS https://grapheneos.org/
St, Xterm, Terminator - depends on hardware and os.
I'm most comfortable when my window manager and terminal emulator are well integrated and keyboard centric.
No. ReadMe files should be concise, explicit, and text only. UI/UX screenshots can be part of the repo, wiki, or associated website but they shouldn't be in the ReadMe.
If you don't understand the software you're installing from some rando stranger's git repo then you shouldn't install it. Period. Take the opportunity to learn more or use another tool.
Git repos are not app stores. The devs don't owe you anything.
The vast majority of software in publicly accessible git repos are personal projects, hobbies, and one-off experiments.
Your relationship with the software and the devs that create and maintain it is your responsibility. Try talking to the devs, ask them questions, attempt to understand why they constructed their project in whatever specific way they have. You might make some new friends, or learn something really interesting. And if you encounter rudeness, hostility, or incompetence you're free to move on, such is the nature of our ever-evolving open-source community.
We bring a lot of preconceived notions into the open-source / foss / software development space as we embark on our own journey of personal development. I try to always remember it's the journey of discovery and the relationships we curate along the way that is the real prize.
No, you don't know how to manage genZ (or any other cohort) because that's not a fucking thing.
Start here:
Fight to pay them more. Period. This should be at the top of your daily to-do list. Your team is the reason you have a job, and they're the reason your shareholders live such splendid lives. So, you want to keep your position(s) of benefit & security? Then never stop fighting for worker's pay & benefit INCREASES. It is really hard to care about management, production (or shareholders ๐) when you can't take care of yourself or your family.
Curate a safe, work-focused environment that supports the life-cycle of a product that actually solves current, real-world problems like - global warming, profiteering, equality, etc.
Stop managing and learn how to lead.
Leaders:
Know how to say, "I don't know."
Show / do by example
Share knowledge
Support and foster knowledge sharing.
Shut their goddamn mouths and trust their teams to succeed (that's why you hired them in the first place right?) and when the team/member falls short of PREVIOUSLY AGREED UPON goals you work together to address the extenuating circumstance(s).
Every company's greatest asset and product is the verve, innovation, and vision of its employees. Squash, or worse, fail to invest in any of these aspects of your workforce and the human beings you're trying to "manage" will "manage" themselves into better working conditions elsewhere.