Hello, I'm building https://chargeradius.com, a web app to help drivers find nearby EV chargers quickly and open directions instantly.
The idea came from wanting something simpler than a map-heavy charging experience when you already know roughly where you are and just want nearby options fast.
It’s built with a Tesla integration, though the core charger lookup and directions can also be used without it.
Sometimes people just want to talk, they want to be heard; occasionally bouncing ideas or thoughts on somebody can help come to a realization, or even a solution to a particular problem.
I would probably go for the new replacement screen.
Anecdote: I was able to find one of the last trustworthy MBP Retina (Mid 2015) for $1996. I had the late 2013 (no intention to change it) but the extra RAM is a nice upgrade and at the same time the old model could go to my mom. She loves it, and I'm super happy with mine.
TL;DR The article focuses on the ability to “Think and act like a CEO” as a developer.
In one of the recommendations it says: “As a developer, when you are developing features or working on any project, think about how this relates to the success metrics of the company and communicate this clearly.”
I wanted to hear from experienced developers, how much of this is true. I get the feeling that in some environments, thinking about how a metric relates to the success of the company may not be something some developers think or can actually focus on.
In South America, specifically Argentina almost all households have a Bidet. It baffles me that a country like the US doesn’t have them as a standard device (at least in homes), considering the amount of food in the average American diet.
The idea came from wanting something simpler than a map-heavy charging experience when you already know roughly where you are and just want nearby options fast.
It’s built with a Tesla integration, though the core charger lookup and directions can also be used without it.
Still early, but live and iterating.