OTA updates frequency.

They’ve slowed down significantly the last 6 months.
 
We’re two weeks away from the longest feature update interval.
 
Not directing this at anymore so don't get upset. :)

As someone who used to be a software engineer for 30+ years let me give you some insight on pushing out releases. There are reasons why some people get updates and some feel like its been months since they've had an update. The reasons are numerous. Some I can think of off the top of my former engineer head are:
- The more customers are onboarded, statistically your chances gets lowered if there is a static distribution. If Lucid only wants to do 100 updates/week in random batches well your chances gets lower with more customers. Also, with more customers the code may be impacted because there could be new regions to localize into the software.

- Versioning. If for example there are versions 1.7, 1.8 and 1.9 distributed and here comes version 2.0. Folks with version 1.9 "should" be less likely to be the first to get 2.0. Why? Because the 1.9 people had it for a short period of time. If those people get 2.0 and report a bug, it's hard to tell if the bug is from version 2.0 or a unreported bug from 1.9. Devs would love to know situations where "oh there was no such bug in 1.7 or 1.8 to 2.0 customers but we see it in 1.9 to 2.0 customers. That lets the Devs narrow the issue and not have to pull up multiple versions of the software to read. Imagine reading 5 versions of the same newspaper article and trying to figure out which one is most correct. Yes software development is THAT boring sometimes.

- The larger the code becomes (more and more features) the longer it will take to test. You may now have 100 components whereas last year there were 75 components.

- Whats the staff turn over like. Are their senior engineers gone and all the entry level (and god forbid outsourced) developers only doing what they are told to do by the remaining leads and have not demonstrated the ability to investigate on their own? This is a much bigger deal than you may think. My generation of developers will go and figure out things to fix and to improve. This generation (esp outsource), not so much. They feel they will get in trouble if they do more than they are told. I have worked with groups that cannot, on their own bring up the courage to correct a simple yet in your face typo until I put it in writing and schedule the change even though I tell them on a weekly basis, please just fix it and bypass any formal process, its been blessed by upper mgmt and I will take full responsibility.
 
Back
Top