The average price isn't the price of a starter home, why do people fall for this clickbait.
That's like trying to use the average price if a car as your starting point for how much you need to make to buy your first car.
Which means about the halfway point between a 1k beater and a fucking 200k rolls royces is what you are pretending a starter car is.
"Oh man the average price if a car is like 80k no one can afford to buy a car"
People are so stupid about this. You can get homes for like 200k to 250k in most major cities, that aren't prime locations but 100% liveable and not a total dump, just need some work. That's not even bottom of the barrel, you can go way cheaper if you want a total dump.
Everytime you see click bait like this, step one is Ctrl+F for the word "average" and you'll find it everytime.
I haven't found a compelling reason to not just build a solid gaming pc, then buy a Chromecast and steam link to it.
Latency is quite low on a wired connection, I can stream 4k to my TV, and I can use an Xbox controller. You literally couldn't tell me the difference most of the time.
I'm rocking an 11th gen Intel i9, 4060 ti, and gigabit network wired between PC <-> chromecast.
Just make sure you get the latest chromecast that can handle 4k streaming though!
Not to wire ethernet into a chromecast, you need a USB c adapter, those dongles that take in USB C power, ethernet, etc. It has a single fully functional USB c port, so you can also connect wired USB and all the jazz to it if needed.
ITT: non devs that think multithreading is still difficult.
It's become so trivial in many frameworks/languages nowadays, its starting to actually shifting towards single threading being something you have to do intentionally.
Everything is async by default first class and you have to go out of your way to unparallelize it.
It's being awhile since I have seen anything mainstream that seriously cared about single thread performance enough to make it the most important benchmark.
I care about TDP way more. Your single thread performance doesn't mean shit if your cpu starts to thermal throttle.
Literally anyone can run the basic numbers on the bandwidth that would be involved, you have 2 options:
They stream the audio out to their own servers which process is there. The bandwidth involved would be INSTANTLY obvious, as streaming audio out is non-trivial and anyone can pop open their phone to monitor their network usage. You'd hit your data limit in 1-2 days right away
They have the app always on and listening for "wakewords", which then trigger the recording and only then does it stream audio out. WakewordS plural is doing a LOT of heavy lifting here. Just 1 single wakeword takes a tremendous amount of training and money, and if they wanted the countless amount of them that would be required for what people are claiming? We're talking a LOT of money. But thats not all, running that sort of program is extremely resource intensive and, once again, you can monitor your phones resource usage, you'd see the app at the top burning through your battery like no tomorrow. Android and iPhone both have notifications to inform you if a specific app is using a lot of battery power and will show you this sort of indicator. You'd once again instantly notice such an app running.
I think a big part of this misunderstanding comes from the fact that Alexa/Google devices seem so small and trivial for their wakewords.
What people dont know though is Alexa / Google Home have an entire dedicated board with its own dedicated processor JUST for detecting their ONE wake word, and not only that they explicitly chose a phrase that is easy to listen for
"Okay Google" and "Hey Alexa" have a non-trivial amount of engineering baked into making sure they are distinct and less likely to get mistaken for other words, and even despite that they have false positives constantly.
If thats the amount of resources involved for just one wake word/phrase, you have to understand that targeted marking would require hundreds times that, its not viable for your phone to do it 24/7 without also doubling as a hand warmer in your pocket all day long.
Man you'd think the US would've learned its lesson last time a small power hungry country kept trying to oppress and take over other neighboring regions, allowing its fascism to grow until it became more than just a localized threat..
Why does this mistake keep repeating? It's almost like the US likes going to war... oh. Hm.
The goal of the sprint meeting is very straightforward:
Everyone gets informed what everyone else got done yesterday, so they know where people are at
Everyone gets informed what everyone else is doing today, same reason as above.
Anyone who is currently blocked on a task can quickly ask for assistance, and with everyone in the meeting someone can jump on that or direct them to a person who can help
Anyone who doesnt have anything to do can ask if anyone else needs help with anything
Its an all hands meeting meant for everyone to get their morning baseline "what is everyone else doing" understanding.
It's also extremely critical for company culture, morning standups keep individuals anchored to "who is my team" and "what do they do", so they understand when asked who so-and-so is and what they do here.
Without the standup meeting, you typically get situations where everyone is operating in their own glass boxes and they start to disconnect from the team. They have no idea what other people are working on, they have no idea what other people even do for the team, etc.
You dont want a situation where your developers have no idea what your QA team is busy with, and no one knows what the UX team is currently tackling. Thats how you get a lot of divergence and disconnect.
The standup helps keep everyone not only aligned, but also knowledgeable of whats coming up next.
Your devs hear about what the UX team is finishing up so they know that in a couple days thats going to be next on their plate, and your QA knows what the devs are finishing up so they know whats next to focus on.
You can consider the morning standup to be your cross pollination meeting for infoshare.
Gogs and Gitea are very similiar, Gitea is a fork of Gogs with a bit more features as I understand it.
However when I tried to get Gitea working personally a year and a half ago, it had some rough issues with redirect looping onto itself infinitely, could never get it to work.
On the other hand Gogs didn't have this issue, and was much more painless to stand up, so it's what I use now.
Ideals largely vaporize when you have bills to pay and you are facing homelessness.
Your best bet is start talking to local job recruiters, ask them what tech stacks and certs are in high demand, and go learn that stack and get those certs and take whatever job will pay you.
Once your bills are getting paid you probably will have time/energy to work on personal projects.
The vast majority of work is closed source proprietary stuff.
In fact to be more specific, the vast majority is mind numbing "thing" management CRUD applications.
Inventory management, people management, accounting, etc etc.
"We wanna make an app for managing (things)" is gonna be your life for awhile.
It's also heavily a lot of "we had this (thing) management app made by someone 12 years ago. It's now barely functional, riddled with bugs, has huge security holes, and has tens of thousands of users every day on it. We want you to add new features to it and not fix any of the existing massive issues at all. We have no idea how it works, it has zero documentation, we don't even know where it is hosted atm, and you will count yourself lucky of you even get the git history"
You heavily want to focus your skills first and foremost on how to read other people's code. How to interpret wtf this zero documented function does and how it works.
This, my machine is in the basement inside my server rack lol.