When it comes to mobile apps, I generally recommend native (swift/kotlin) or Flutter, they all have good tooling and have good performance
In this case though, they are all curly braces languages and don't have much in common with python.
If you don't want to learn at least 1 new language, there are some python libraries/frameworks which can be used for mobile dev. Like Kivy or Beeware. I've never used any of these though so I can't tell you how good/bad they are.
This does strike me as odd, your commits should be cleaned up if they are a mess of "reverted X", "fix typo", "saved days work", etc. on the other hand, you don't usually have to explain your modifications if you didn't squash your commits.
It's already been said a couple times but if your more experienced team members are saying, "that's a really weird task" the issue is probably the task not you.
Having daily meetings with a senior because you're having a lot of trouble progressing isn't necessarily a bad thing. Everyone has jobs that are absolute ordeals and sometimes it's better to break them down even further and just go one step at a time.
Also, are you involved in your team sprint planning? Who says "this ticket is a 1 day job" that should be your teammates, or at least a subset of them? Why did they decide this was an easy task? What did they, or you, miss in the execution?
In my experience this does happen on occasion, it absolutely shouldn't be happening all the time though.
Generally when this starts to happen my team lead puts his foot down and says, no more changes until you sign off on what we have and we've released the MVP. After all, if the core functionality is done, then the MVP is done and we don't need to keep sitting on it.
The title is a bit misleading, the summary on the article makes it clear that YouTube kids functionality is being rolled into the main app rather than being its own thing.
I love when I make a small code change and then I make my PR, CI runs and some piece of code entirely unrelated fails and it's now my job to work out how these two unrelated things are related.
In that case, this is also a yes.
I'm a developer working for a SaaS company and you didn't NEED a degree to get hired but it sure was a "nice to have."
I've got a pixel 6, never had any issues with it. I would recommend all the usual suspects: turn it off and on, update, factory reset.
If you are up to date I remember people complaining that the latest update broke some stuff for them, that might be your issue?
I think I understand this;
cancel -> submit the POST request and cancel -> undo this thing. maybe they shoulda just used submit & cancel or cancel & exit instead.
I'm not sure if the rules are different with macros, I've never written one but this lint is generally caused because you set a var to a value and then overwrite that value before you use it. e.g.
let mut a = 1; a = 2; println!("{}", a);
This will throw the same warning because 1 is never used, this could've just been:
let a = 2; println!("{}", a);
So first I'd double check that I NEED last at all. Maybe try:
cargo clippy
See if it can tell you how to fix it.
If that doesn't work, it's sometimes necessary to skip certain lints. E.g. if you make a library, most of the code will be flagged as dead code because it isn't used and you can use an #[allow(dead_code)] to stop the linter warning. You might be able to use #[allow(this_linting_rule)].
Hope something here helps.