It’s very confusing to me too. I clicked an icon to see what it was, and it was opening times of a supermarket, which I had no idea about. But I couldn’t find a way to just get back to where I was before. My workflow now is to keep force killing the app frequently when I get stuck.
The biggest thing for me was just being brave enough to go for it and give it a try, and then learning how to undo your mistakes. Re-do things you’re not happy with with braid, reflow things with flux, etc. I’ve torn vias out of old valuable boards doing restoration, and I learned trace repair and fixed it.
It’s a neat core, but z386 is where the action is right now (https://github.com/nand2mario/z386_MiSTer). Interestingly this core doesn’t output a proper analogue signal. I always wondered why until I recently tried to implement a real EGA pixel clock on the PCXT EGA core. Basically, video cards with dual (or more) pixel clocks are not realistic on MiSTer. The PLLs are there, but once you get too many clock sources the routing becomes quickly impossible. MiSTer framework’s pipeline also forces pixel clocks tied directly to video output (for good reason) and switching that clock at runtime gets very tricky.
I suspect this will become increasingly common with companies that allow remote work. Atlassian is a large Australian tech employer that is full remote, and this is definitely the case there - performance reviews twice yearly and a very high attrition rate.
Anecdata: in Sydney, Australia, 5G on Telstra is incredibly fast (I get more than 1 gigabit at my apartment, but more typical / busier cells seem to be between 300-500Mb), and my experience using it mostly just for web browsing is it’s streets ahead of 4G.
What on earth do people do besides eating at home from a rotating set of straightforward recipes? Honestly curious. I’m the main cook in my home and we do eat out every other week, but who has time for that much experimentation?
I've recently started a job in a very complex business domain, but sadly they're using NoSQL for everything. I've known for a while about the technical tradeoffs of NoSQL, but until now I'd never experienced that the lack of expressiveness in the data store is a major obstacle to understanding what kind of data the code deals with and how it's related. The data's all there, but exploring it without a real schema is much more difficult.
Strangely enough, they did exactly as suggested when batteries started wearing out on iPhones (unable to reliably provide the voltage at full drain for peak performance) and you're the exact kind of person who jumped on them for planned obsolescence.