starky
There are a number of email providers I looked at when switching. Ended up going with mailbox as I was more confident about privacy of a company in Germany than Australia and they were a bit cheaper. Posteo seems like a good option if you don't have your own domain. I also looked at Tuta, but their lack of import killed them as an option, I'm not signing up for a higher subscription level to get that feature.
Not necessarily, there are also plenty of cases where a person's KPIs don't match their responsibilities or the actual needs of the team. This is frequently a management problem where resources haven't been properly assigned and the employee will always prioritize what they are evaluated on to minimize friction. Far too often managers collect responsibilities for their team (or are told to take on something), yet have zero plans other than "it will work itself out" and they don't bother to formalize how the requests will be dealt with.
There are certainly a lot of people out there that refuse to do their jobs, but it is common enough that there is something else wrong that a discussion with the manager about where the process is failing is the first step.
I feel called out here, I looked at this and thought "I've already built this". I've got a RPi with screen and speakers that displays a Home Assistant dashboard as a smart alarm clock and smart home controller.
I've never worked for a FAANG and don't intend on it, but are there realistic pathways to getting promoted into the more senior engineering roles within a few years and getting decent RSUs each year? At least from my experience from working for a Fortune 500 company, they path to getting RSUs and the title are not that quick.
I think startup or smaller growth companies are better for this (but I'm biased since that was my path), as you can get more responsibility and rise through the ranks quickly to that critical senior or staff level where you start getting the real RSUs even if it means moving to a different company.
I absolutely despise STL as a format and think it doesn't have any place it should be used.I have a hard time taking OpenSCAD seriously due to this.
In a case where something is safety critical the computer is super important as very subtle errors could cause catastrophic consequences. This is why you get into things like running software on 3+ computers concurrently depending on how fail-safe something has to be.
I've not used it in a very long time, but I also get the impression that Cinnamon is also familiar in this way and doesn't make major changes.
Recently I was trying to put a couple videos on my iPad before a trip. I would think I could just copy the files from a network share to the iPad and be done with it, but that didn't work as I couldn't get those files to be accessible in the apps no matter what I did. Instead I had to use VLC which has a server built in that was able to upload the files into the app. The entire process had me swearing at Apple constantly.
Testing products properly is HARD. Companies have entire groups of people who that is their entire job and if they do it wrong it can costs millions in returned product. At the same time, if the test is too harsh, the customer is paying extra for a product that is over-designed for conditions the product will never experience.
For example, with his bending test. You would define a standard loading method (e.g. 3 point or 4 point with specific spacing), and then apply a realistic load a phone may experience plus some safety factor with a specific loading/unloading profile (say a phone is sat on and experiences 100lbf you might test to 125lbf). Once released you inspect the phone for damage, deformation, and test functionality.
Maybe the folding phone form factor will inspire some better UI/UX for apps.
>What's the equivalent of "Google it yourself" these days? When you ask something of somebody, the expectation of the other side to drop everything and do work for you isn't always appropriate/balanced/appreciated.
One of the hardest things about taking on any sort of leadership role (even unofficially) is that you need to allow others to do things. It feels incredibly stupid when you have to ask someone to do something you are more than capable of doing better/faster than the other person, but if you did that all the time you wouldn't have time to do your other work. Sometimes that includes questions that seem lazy, but part of asking the question is for the other person to acknowledge that they have thought about it and/or to ensure you aren't stealing ownership from someone.
They did recently increase their storage from 10GB to 20GB (along with a price increase from 30 to 36EUR/year). They also have had catch-all addresses as long as I've used the service, you just setup an email alias for it.
I wouldn't say it is easier than expected though, logging in, changing your email, confirming the change, and then making sure the password manager was updated was a bit of work.
The tapping out thing can be so confusing, even as someone that uses transit a lot. I was traveling recently and encountered buses where you had to tap in only, ones you had to tap in and out on, and ones where you had to tell the driver where you were going before tapping in. None of which had clear signage on the bus itself.
Even with my home system, at the airport I noticed they had installed extra stickers covering up the wrong way gates, and I had to tell someone where to tap their tickets when their entire family was blocking my way to the platform when trying to get home.
I recently flew and the airport had gotten the new scanners since the last time I had gone somewhere. The signage was confusing as only some of the lines had signs that specifically said you didn't have to take out your electronics on "this lane only". Even with the new scanners they were pulling out half the bags for additional screening and only had one person doing the additional screening.
Coming back from overseas I saw how it was supposed to work, walked up and they directed me to a line and a specific bin loading station, had someone remind me to ensure my pockets were empty, walked through the scanner and my bag was already waiting for me, took all of 2 minutes.
When I make stews I'll often make a concoction of tomato paste, soy sauce, fish sauce and Worcestershire sauce to massively boost the meatiness of the stew without making it taste like any of those ingredients in particular.
I've recently had to deal with a problem where the parent company has dictated 100% production testing for a spec that we meet for the spec sheet but customers practically don't ever need. But since the parent company test their products this way they say we have to. I've been very vocally against this because it has delayed us shipping products that are otherwise ready, prevented starting new products, and added a lot of production cost when our RMA rate without the test is something on the order of 0.01% and most of those are due to installation errors, not true failures.
I dislike this statement. Hardware is as hard as the product dictates it needs to be. A 25 component PCBA and a clamshell of 2 injection molded parts is about as simple of a product as you can make. Heck, most people would just buy an off the shelf clamshell for that type of product.
That doesn't work for the vast majority of products, building a product with 20 COTS parts plus 60 custom tooled parts, and 4 complex PCBAs is what is hard. Getting everything to fit together, pass testing, arrive on time from dozens of suppliers, etc. it where the complexity comes in. Then consider that hardware is cash intensive, you need to pay ahead of time for all the tools, you need to pay to buy the individual parts and warehouse them somewhere while you build the products you hope are going to sell. If something goes wrong there, then your expensive parts are just sitting there waiting for replacement components before you can ship. Then even when you ship, that revenue goes into buying the next round of parts you are going to receive in 3 months. This is where many hardware projects fail as they run out of cash before the project breaks even.