Where are you, ladies and gentlemen developers?

silentvoyager said:

one developer works on feature A, another developer works on feature B

exactly. 

and we can add to this that developers usually low level code generator bio robots with high level of attrition, so they have really not a clue about the code they are working on

and that is the normal practice basically everywhere. that's why there are a complete framework above developers from tech leads, business analysts, product owners, QA, etc, and a *** of a processes to prevent critical bugs arriving to production

so this should not be an excuse for this quality (or lack thereof) 

bw said:

I really can't understand what drives Garmin to do

let me summon the Occam's Razor here: the simplest answer is probably the correct and that is here the lack of competence (probably on a manager level).

because there is no pressure from the market (we buy these gadgets anyway), all the quality focused managers and lead devs are already left the company or they were just fired spending too much time on useless things such as a "working software"

pxl said:

Occam's Razor here: the simplest answer is probably the correct

Since we share a profession, let's be correct on this one: the explanation making the fewest assumptions is the one to be preferred ;)

And yes, I think they grew a culture where "people will buy it anyways" became the mantra and they are right about it. People are spending 1200 bucks on a watch and are defending that decision, although they are seeing that it's far from functional and stable. If somebody wants to set the impulse for a cultural shift that would be a hard one.

I see it with myself, I've been tempted buying a 1200€ watch, part as motivation, part as treat to myself... But lucky me, usually I'm with projects where my voice holding quality up high is heard - but mistakes there are usually also much more expensive than loosing some customers... Well Garmin at least got a bunch of first buyers for the Fenix 8, that fell into "Fenix 8 will be the AWU killer"-clickbaits during the last months.

silentvoyager said:

Furthermore, what often happens is that one developer works on feature A, another developer works on feature B, and both of these features are implemented in isolation from each other. But then it turns out these features don't work together. For example a lot of Fenix 8 bugs seem to be caused by changes in their UI and settings, and some settings being being lost in translation or moved to another place.

This is insightful and I can already see some concrete examples (just from forum posts).

- The ability to mute all beeps/tones was moved to volume settings - the new way to mute all beeps is to mute all sounds (along with disabling key tones as usual), and there's no longer a separate "alert tones" setting. Seems like a logical way to streamline settings (although I personally disagree with it - what if someone wants to hear audio prompts but not alert tones?) However, the "alert tones" setting was also removed from Enduro 3, which lacks a volume control (bc it lacks a fully-fledged speaker), which means there's no way to mute all tones in Enduro 3

- The only way to open the location menu (to save or navigate to the location) when the crosshairs is displayed on the map is to hold START (just like Forerunners). Unfortunately, the default shortcut for Hold START is Voice Command, and the shortcut takes priority (probably because Voice Command is an important system feature that's documented to open when you hold START.) This means there's no way to open the location menu without changing a default setting.

To me, the most annoying thing about this kind of bug is that similar things have happened more than once in the past: on FR955 (and probably other watches), holding DOWN or UP is supposed to pan the map more quickly, but at various points in time, hold DOWN opened the music controls (as per the default hotkey/shortcut) or hold UP opened the menu (as per unchangeable system behavior), even when you were on the map screen, in pan mode. Both of those issues have been fixed since. So at least twice in the past, there was an issue with a system or user shortcuts taking precedence over map functionality when they shouldn't. Each of those times, the problem was fixed, but here it is, happening again.

I work in software, so I absolutely know better, but you'd think that once a certain problem happens more than once (or even once), someone would make a note somewhere to avoid that problem in the future. But ofc, irl it's useless bc people would have to know where that note is in order to read it, and they would have to care in the first place. What usually happens is that some idealistic person might care and they might look out for these things, but ofc that isn't a solution in general, as people like that can't work on everything, and if and when they leave the organization, their knowledge (and passion) about that stuff goes with them.

Speaking of one hand not knowing what the other hand is doing, 3rd-party Connect IQ app developers see it all the time: the firmware team makes some decision without discussing it fully (or at all) with the Connect IQ team, leading to a bug in Connect IQ (apps start crashing, working funny or looking weird.) Nobody at Garmin notices until a 3rd-party dev reports the problem. Usually, after some discussion, the decision on the firmware side is reversed.

This happens over and over again, and there's no sign that anyone ever learns from these mistakes.

excellent!

then I might utilize my Epix instead of the actually broken Edge: SW version 24.19 gradient issue - Edge 1040 Series - Cycling - Garmin Forums that went nuts with the last FW update

I am hesitant, though, that I would consider this as an addition or upgrade...

Disabling gps recording when using iq glances wasn't that minor and took a year to fix.