I've been trying to boot a Ubuntu 24.04 USB (please no discussion of distro choice) but I keep getting a very unhelpful error during the initial startup. I've tried using a different USB drive, a different USB port, booting from UEFI. The only thing that has made a change was booting into safe graphics mode. It got to the install wizard but when I got to the end of the wizard it gave me other seemingly useless error messages.
I'm concerned there's an issue with my motherboard but I don't have strong evidence to support this idea. I recently took a trip where the computer was fine before I left. I turned it off while I was away and when I came back my main drive no longer worked. I couldn't boot from it or even see the drive in gparted. I've replaced the drive without issue though. If my motherboard is somehow going bad, it's being very subtle about it. I was ready to blame Nvidia but when I got it into safe graphics mode, it didn't get to the point of having Nvidia drivers.
Does anyone have any idea what might be going on or any way I can get additional information about the errors I'm getting? The lack of information is really frustrating.
It can vary a lot depending on the day and the company/job. Frequently there are meetings that are update/planning discussions, discussions with one or more other engineers on how to build a given feature, debugging existing code to figure out why it's not doing the thing we want (which is a different but overlapping skill set with coding).
Ultimately there isn't really a "typical" day because we wear a lot of different hats. My current job is more coding heavy because I'm at a small startup with only a couple of engineers. In a given week I'm probably doing 10% meetings, 50% coding/debugging/configuration, 20% code review (reviewing other people's code), and 20% thinking/designing/experimenting with ideas. Those numbers vary a lot though. At a previous job I ended up spending an entire week just doing project management to alleviate my boss' anxiety over a project (which was somewhat self defeating because it meant I wasn't getting work done on said project). That job in particular had a lot of politicking and communication which was due to micromanagement.
A lot of what people don't realize is that we aren't just building a feature. We're building a feature while thinking ahead to known or potential future features. How can we build feature A to enable making features B, C, and D easier/better/faster without also making feature E much more difficult or impossible? It's about building flexibility into the system while also balancing against time and cost restrictions. We as engineers have things that we see as necessary while the business wants more features and it's necessary to balance the two. At a healthy org that means that there's a negotiation of priorities between the two forces. If you only focus on the technical stuff, you won't ship features. If you only focus on the features, how fast you can deliver features will come to a grinding halt. Your system will also start breaking in unexpected ways which takes time away from building features.
It's kinda a rambly response to your question but I hope it helps.