This happened to my Samsung S23 after the update too. The thing would black screen spontaneously following the update. At first it would respond to an hard-reboot, then repeatedly complain about Google Play Services crashing, and eventually black-screen again. After hard-rebooting it a few times it no longer even responds to the hard-reset key combo.
I wanted an electric car. I did not want to be an early adopter of any brand. I value reliability over style and coolness, so ended up with a Nissan leaf. I'm very happy with it for my daily driving. It's a little boring, but very functional, reliable and a great value. The leaf and other ~$35k electric cars actually save me money over gas cars. Any electric that costs more than about $40k would be more expensive to own than a gas car.
The leaf will go to my teenager in a few years, and then I'll probably buy a mid size hybrid crossover. The electric car is good for daily driving near home, but not great for road trips in the rural mountain west.
How about this: stop penalizing kids who can’t sit still in school. Statistics show that the “sit still and listen” model doesn’t work for many boys, but the stats show that the model doesn’t work for many girls either.
The recommendations in this article are solid, but apply to all kids.
We are breaking our monorepo into 3 kind-of mono repos based on release cadence. A repo for each of two large applications plus a third repo for shared library code. We import the share library code onto the app repos using a git sub module. Has anyone else used git sub-repos to import common code?
We've used submodules pretty extensively in the past but we're working to get rid of as many of them as possible. A friend and former colleague liked to say they were the worst solution... with the exception of all the other solutions. Practically speaking they are probably more confusing to new developers who haven't had a lot of experience with them. We would often run into problems that stemmed from someone making a change in the submoduled repo and then forgetting to update the ref in the parent. Or people would navigate to the submodule to do the work there rather than checking it out separately, and then be confused over the detached HEAD status and check out a branch (not a problem, necessarily, but confusing to some extent). For some of our dependencies we've gotten rid of submodules in favor of hosting internal pypi packages.
Git submodules have a comically bad user interface imho but they work really well so I use them despite this. As with git in general the core functionality is solid. There is also something to be said for making as much of core functionality without resorting to another piece of infrastructure. People can use whatever front end they prefer on their machine but in a pinch the core git package is all you need.
You are right. Agile, languages, CI, devops are all tools not solutions to problems. Blindly applied, they will not get the results promised.
First focus on identifying the primary job to be done: build a valuable piece of software with as little effort as possible given your current team and existing technology.
Second, consider how valuable the existing software is and whether it really needs to be rewritten at all. Prefer a course that retains the most existing value. It is work you won't have to repeat.
Third, choose tools that maximize the value produced per hour of your team. CI, Devops, Microservices, Languages all promise productivity and reliability benefits but will incur complexity and time costs. Choosing the right mix is part of the art of software management.
