Anything is possible, but I don't think judgement of visual aesthetics maps at all to quality of writing.
I'm a damn good technical writer and can break down complex ideas into clear and understandable prose, but I don't know the first thing about fonts or typesetting.
I think it's likely a sincere question. I, for one, would not wanting to be physically touching a radio that people may have been turning on/off depending on whether the device is located before or after their ability to wash their hands.
The key insight is to note that FIELDS table actually defines the name, ordering, and config for each of the fields of a given note type, and that the actual notes data is stored in the Notes table in the DATA column, most likely as JSON.
>Medical device interference iPhone contains magnets as well as components and radios that emit electromagnetic fields. These magnets and electromagnetic fields may interfere with medical devices, such as pacemakers and defibrillators.
>Though all iPhone 12 models contain more magnets than prior iPhone models, they’re not expected to pose a greater risk of magnetic interference to medical devices than prior iPhone models.
>Consult your physician and medical device manufacturer for information specific to your medical device and whether you need to maintain a safe distance of separation between your medical device and iPhone. There are many types of medical devices, and manufacturers often provide recommendations on the safe use of their devices around wireless or magnetic products to prevent possible interference. If you suspect iPhone is interfering with your medical device, stop using iPhone.
> Do you carry liability insurance for your company? Have a contract lawyer that you know and use? If not then you are probably not big enough for the major RFPs.
I just wanted to dispute this. I highly recommend carrying liability insurance regardless of size (I'm a single person shop). It's relatively cheap. A million dollar policy will run you just a few hundred bucks. It's a huge protection and also a marketing plus since it acts as a quality indicator.
I also recommend having a contract lawyer, even for single person shops. Again, a little money up front can be a huge time and aggravation saver down the road.
Or "hide" the stuff you don't like. I like to do that so that when I come back 10 times later that day I don't continually have that annoyance when seeing the story again.
2. Yes. Though like anything, you get out of them what you put in.
3. Set on a per-person basis. Some people need/want to meet every week. A lot of them are younger developers and are looking for constant guidance/feedback on how they're doing, ways to improve, or just to talk through issues.
While a person is in charge of their frequency, we do require at least once a month. Those people are usually more senior in their careers. In those cases, a lot of times the meetings are shorter and we just have a quick chat to make sure everything's okay with both them and their team.
TestFlight. The user limit is 10,000. If beta review is slowing down your dev/release cycle, you may be using it incorrectly. After initial beta review, it's usually unnecessary to have subsequent versions reviewed unless you've significantly changed the purpose/functionality of the app, and that's keyed off of the questions they ask you when you upload new betas.
I think this is a great idea, security-wise. I prefer my installations to have as few attack vectors as possible. So having as few things enabled/installed by default is awesome.