The main point of the article is that by "covering your ass" you are actually becoming a better developer, because the prose you write is plans and documentation and gives your thoughts structure.
Hence, your personal productivity (measured by what metric?) might suffer for this one task. However, in the long run you and your team gain productivity because of existing explicit documentation and plans.
A lot of plans and thinking goes into how to transition from the old to the new. Valuable for the "brief" period of transition but generally worth less once complete. This also doubles the time to deliver. Additionally, many times research and code analysis/review is needed to flesh out what needs to be done. Often times it's faster to make the changes when discovered rather than having to document what needs to be changed then getting the go ahead to change it. ("What did I change?" It's in the code commits and repo! Why do I need to translate it to English? Oh because my boss can't do my job...) This can drastically reduce delivery time. "What if there's a bug?!" What if there is a bug. We'll deal with it.
I wonder the same. This proposal sounds like it is leeching nutrients from the ground and storing it for a long time (on a scale of centuries in the proposal). How do these nutrients cycle back for growing the food that we need? Or, for that matter, for the next round of biomass to freeze?
On a tiny scale I store them via humification in the top soil. In agriculture they manage the humus content of their soil anyway, for example in greenhouses they might have 20% instead of 2% in the surrounding fields.
Someone armed with enough VC money could possibly do that on a really large scale and even monetize it via carbon offset certs and then just throw the C rich output of their giant bioreactor into the bottomless pit.
Caniuse is a database listing browser support for all kind of web development features, i.e. what version of what browser supports what features of HTML, CSS, Javascript.
It helps web developers to determine what language features to use in order to be compatible with the browsers most of their users use.
And it might sound unfair to compare the fairphone to a pixel device or a pixel device with grapheneos but the practical reality is that if this is going to be my one phone, than it will be the hub for all my private conversations, my bank forces me to use an app based authentication so basically my entire finances are on that device, e-mails, including those with doctors, etc.
It has to be secure and it has to up to date. And I am aware that my Pixel 3a currently isn't but I'm literally between buying the fairphone or the pixel 8. And I really don't want glued in batteries.
In November and December each there is at least one Critical System CVE, with google noting:
> Note: There are indications that the following may be under limited, targeted exploitation.
> CVE-2023-33063
> CVE-2023-33107
> CVE-2023-33106
So...Those aren't patched right now on the fairphone 4, are they? Now I'm not arguing most other companies are doing better, but that doesn't make it a good situation.
> And you would even prefer Lineage OS? Isn't that still more or less mandating userdebug builds and entirely open?
As far as lineage is concerned, i'll be waiting for an official release to even be there before evaluating the security but I am aware of the userdebug issue.
Though let me say that "abhorrent" is propably not the best adjective to describe it here. Unsatisfying would be fairer. As for the rest of the software... I just have to look at the forums dude...
Okay, that is fair: I am also not happy about us being late with security patches for several weeks. I am not directly involved in that anymore, but I believe, we currently have a policy to release updates quarterly.
Back when I was still working on security updates, this took up so much resources that we struggled to work on anything else (bug fixes, major upgrades, etc.). It is unfortunately a compromise that we currently have to make with our limited resources.
Still, we are planning to release these regular security updates for 10 years and we have a track record of sticking to such plans. In my opinion, that is much better than having monthly updates for a couple of years. (Btw: outside of flagships, many models don't get monthly updates anyway and not even for long.)
Maybe I misunderstand your point of spherical vs parabolic, but doesn't this paragraph explain it?
> The concept turns part of the inside surface of an inflated sphere into a parabolic antenna. A section comprising about a third of the balloon’s interior surface is aluminized, giving it reflective properties.
The balloon is approximately spherical but probably not exactly (actually, when looking closely, hardly any beachballs are spherical either). What is parabolic is the part of the balloon which is aluminized.
Yeah; I was wondering how they get the mirrored part of the balloon to take on a parabolic shape, rather than spherical; is that done by manipulating the balloon material somehow? Or are they settling for spherical as a good-enough approximation?
I work at Fairphone but am not at all involved with the headphones. Still, I know that this is an issue that we thought about and address.
Headphones should keep working even if the manufacturer goes bust and stops providing software support. And even if your battery dies and spare parts are unavailable. That is precisely the reason why we also sell a cable with a 3.5mm jack for these cans. That way, this product is long-lasting and sustainable even in the (hopefully hypothetical) case that we are not able to support them anymore.
That is the best out of both worlds: you get wireless connectivity and ANC now. And you will be able to use them for as long as you would with wired ones.
what's the issue here? if you buy large headphones from the same company you buy the your phone from, in a future where fairphone no longer exists (which playing the odds, is likely) at some point your also no-longer-supported phone (which functionally becomes slower every year because mobile application hardware requirements appear to double every year) might advance to support new fancy bluetooth things your headphones don't support?
I honestly (not hyperbolicly) don't see how a phone not having a 3.5mm jack is relevant to the headphones _having_ a 3.5mm jack
If the headphones are meant to be used with the phone, then the idea that the headphones are future-proofed because they have a 3.5mm jack is pretty meaningless if you can't connect them to the phone with that jack.
In 2023, most people who give two shits about running wired headphones are using a USB DAC, even if their phone has a 3.5mm socket as the onboard AD/DA chipset is usually mediocre and struggles to drive most high-end cans.
It’s simplicity I terms of construction and standard.
Here, the older standard (3.5mm jack) seems stronger (not an expert but an user opinion) and easier to source than usb c.
If you can't use thing A with thing B unless you also have thing C, to my mind that obviously reduces the expected lifetime of being able to use the combination, especially when thing C is a third party part.
The only person that I've ever seen do that had to replace his USB socket after a few months. It turns out that USB C is not designed for long term constant torque being applied, as is the case when it has a dongle attached constantly in a pocket bouncing around. Perhaps if someone sold a dongle that sits flush with the device, and is secured such that no force is transferred to the socket, that would help.
The dongle solution seems to only be good for sitting at a desk. Not for a device that is literally called "a mobile".
Are you sure this is the case? All the carrier app loading implementations that I am aware of (this is a small number) explicitly whitelist some carriers or even some apps by certain carriers. For instance, the implementation I worked on myself (as a reviewer) only granted a single carrier to load one of their apps when the SIM card was inserted.
With that implementation, it would not be possible for any random carrier in a foreign country to load random bloat onto my phone just by me crossing the border to that country.
Hence, your personal productivity (measured by what metric?) might suffer for this one task. However, in the long run you and your team gain productivity because of existing explicit documentation and plans.