Delphiki
Joined 14 years ago
Joined 14 years ago
Remote: Ideally yes, but depends on the opportunity
Willing to relocate: Yes, but depends on the opportunity
Technologies: Swift, UIKit, SwiftUI, Vapor, JavaScript, Node.js, MongoDB, Neo4j, PostgreSQL
Résumé/CV: https://drive.google.com/file/d/1NZdAwPtISwkDFWLHvFjmrkLj-ud...
Email: [email protected]
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.
Remote: Ideally yes, but depends on the opportunity
Willing to relocate: Yes, to Seattle, San Francisco, New York City, or Portland, depending on the opportunity
Technologies: Swift, UIKit, SwiftUI, Vapor, JavaScript, Node.js, MongoDB, Neo4j
Résumé/CV: https://drive.google.com/file/d/1T_QMQb8MNBE3qDSkM-JwqQwoN5J...
Email: [email protected]
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.
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.
What's your source? Cause I don't think that's true... [1][2]
I think you'd be surprised! There are some big names using it at scale[1].