allwein
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.
Not sure if it supports all the features you need, but it exists.
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.
From the online version at https://support.apple.com/guide/iphone/important-safety-info...:
>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.
From the tech specs page on the product itself though:
> AirPods Max can be used as Bluetooth headphones with Apple devices using earlier software and with non-Apple devices, but functionality is limited.
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.
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.
From "TestFlight beta testing overview" at https://help.apple.com/app-store-connect/#/devdc42b26b8
A review is only required for the first build of a version and subsequent builds may not need a full review.
1: Person must have physical access and control of your phone.
2: Person must have Phone pin-code or password, in order to unlock phone and access either SMS, banking app, or password app. Or somehow brute force password or decrypt phone contents.
3: Person must have either password for banking app or password to Password App to gain banking password.
If you're not using passwords (and different ones at that) for your phone, password manager, and banking apps, then that's the whole in your security, not from using SMS as a second factor.
There are issues with using SMS in 2FA, but it's not the issues that you've brought up.
> Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
and seeing the initial screenshot on the announcement, I thought that this was a joke post. How you can call this "focused on simplicity" while showing that horrific hodge podge of a screen shot is beyond me.
Not necessarily. The Product Owner should definitely be able to talk to devs, but not necessarily all stakeholders. What I suspect may have happened in this case, is that a dev talked to a stakeholder that was not the Product Owner, and instituted a change that was either not properly communicated to the team, or which was contrary to what other stakeholders or the Product Owner wanted.