For Google Maps, They have an “official” limit of 500 where anything beyond that is not guaranteed. In practice, the current limit is 3,000.
I’m wondering if Apple Maps is doing something similar where they set a low official limit that they can walk back on / to in the future, as to avoid legal responsibility
Hello! I'm Lewis Godowski, a creatively-driven lead engineer with over a decade of experience across the Apple ecosystem. Passionate about the little details of good design and a strong advocate for the human-centered design process.
Most recently, I was brought onto a new strategic business unit build to turnaround, manage, and lead an underperforming team of ~10 iOS engineers at a top 3 global motorcycle manufacturer. I had two main responsibilities I needed to balance: doing some heavy lifting as an individual contributor, and more importantly people management (upwards with product stakeholders, laterally with other pods and work streams, and downwards with my team). I identified and reduced inefficiencies in our scrum sprint cycle rituals, and established a standard architecture, code style guide, and best practices document for the client's codebase, resulting in a 28% increase in velocity and allowing us to deliver on schedule for an in-person launch event with 150+ dealerships.
Unfortunately, my current role has been transforming more and more into a business/digital consultant, which means a lot of my time is spent working on slide decks and high-level architectures that never see the light of day. It's bumming me out and taking me away from what I really enjoy: writing code, learning new skills, and wearing multiple hats to solve problems.
Ideally, I'm looking for an iOS (or Vapor, a server-side Swift framework) role as either manager or IC that lets me really flex my Swift and iOS expertise.
Hello! I'm Lewis Godowski, a software engineer with ~10 years of experience across iOS and backend. I find joy in dogs, desserts, and the small details of good design. I am a strong advocate for end users and their experience with a product.
Most recently, I was brought onto a new strategic business unit build to turnaround, manage, and lead an underperforming team of ~10 iOS engineers at a top 10 global motorcycle manufacturer. I had two main responsibilities I needed to balance: people management (upwards with product stakeholders, laterally with other pods and work streams, and downwards with my team) and doing some heavy lifting as an individual contributor. I created structure and improved hygiene in the team, codebase, and sprint/scrum life cycle, which stabilized our velocity and allowed us to find our rhythm and deliver on schedule.
Unfortunately, my current role has been transforming more and more into a business/digital consultant, which means a lot of working on slide decks and high-level architectures that never see the light of day. It's bumming me out and taking me away from what I really enjoy: writing code, learning new skills, and wearing multiple hats to solve problems.
Ideally, I'm looking for an iOS (or Vapor, a server-side Swift framework) role that lets me really flex my Swift expertise.
Anecdata, but a few weeks ago I drove from LA to SF in my 2018 Model 3 (long range, single motor). It has a 75 kWh battery pack, my drive was 417 miles, and I drove 70 mph for probably 90-95% of the trip. I used a total of 95 kWh, which equates to ~329 miles on a full charge (100-0%). My efficiency was 226 Wh/mi.
There are absolutely other times when I'll get substantially less range, but it's understandably when I'm driving faster of more aggressive, or it's colder outside, or it's primarily uphill, or there's a strong headwind, etc.
There are a lot of different factors that can affect a car's range (regardless if it's an EV or ICE), and it seems like Tesla has decided to show the EPA range on the dashboard because there's no way they could magically know where you're driving if it's not entered in the navigation system. Once you start navigation however, it's able to factor in all these externalities and give a very accurate estimate. On the first leg of the above trip, I arrived to charge within 3% of Tesla's estimate.
Shouldn't the car know the current temperature (or at least the battery temperature), whether or not the AC is on, etc? Other EVs take those into account regardless of whether or not something is plugged into navigation.
Personally I just toggle to only show the percentage and ignore the battery range estimate. When on longer trips, the nav estimate is usually spot on, or at worst a couple of % off due to my not-predictable driving behavior.
My iPhone can send me alerts that I’m going to be late to work based on its tracking of my daily commute and you’re telling me that a machine that is constantly connected to a GPS network, sending data back to home base, and (almost?) capable of driving itself has “no way” of “magically knowing where you’re driving” unless you tell it?
If only they could use some of that data and processing power to back out someone’s standard commute, driving behavior, and local temperature.
On top of that, my car can remember the MPGs I got for the last tank (and every tank before that) and estimates my range off of that. Apparently that’s “magic” according to the comment you replied to. Tesla apologists always have some excuse.
That's exactly what the Tesla does. When I get into the car at 8AM, the car assumes I want to drive to my partner's workplace, and gives me directions to get there, taking into account current traffic and weather conditions, and a reliable estimate of what the battery will be when I get there.
> in every EV range comparison I’ve ever seen, teslas are the ones that can’t meet their claimed range by a fair margin. Other brands are almost always close to accurate or in some cases do noticeably better than claimed.
What's your source? Cause I don't think that's true... [1][2]
For me, it's hard to find anyone else that matches Tesla on price, range, and performance. It seems like with the other EVs you get to pick two of those.
