https://github.com/briandilley/gilbert

We're currently listening to Grok'n'roll in the shop.

  Current Electric Vehicles is a high-end vehicle restoration and electrification company known for our award-winning builds. Our team of engineers, fabricators, and hotrod builders create custom electric powertrains, restore classics, and push the boundaries of EV technology.

  We are seeking an EV Technologist / Electro-Mechanical Engineer who will play a key role in designing and integrating electric drivetrains, battery systems, and custom vehicle components. This role requires deep expertise in battery system design, electric motors, inverters, and mechanical engineering principles. The ideal candidate will have a passion for electric vehicle innovation and enjoy working in a hands-on, fast-paced environment.

Vehicles: https://www.instagram.com/current.losangeles/

Labs: https://www.instagram.com/currentlabs.losangeles/

blanket statement, also bullshit. Of course money is a driver, but if that's your only driver as an entrepreneur then you're likely not going to be very successful. In fact, this is the primary difference between VCs and builders.

Interesting thought though, what if the product in question is a product geared toward a younger audience that younger devs are more "in tune" with? Assuming they have more impact as a result.

Same with your laptops... and this is only true if you make it that way. Using things like Docker containers eliminates some of the problem with this too.

> There’s always a queue

This has never been a problem for any of the teams I've been on (teams as large as ~80 people). Almost never do they "not want your code on there too". Eventually it's all got to run together anyway.

> Releases are too large

This has nothing to do with how many environments you have, and everything to do with your release practices. We try to do a release per week at a minimum, but have done multiple releases in a single day as well.

> Poor ownership of changes

Code ownership is a bad practice anyway. It allows people to throw their hands up and claim they're not responsible for a given part of the system. A down system is everyone's problem.

> People mistakenly let process replace accountability

Again - nothing to do with your environments here, just bad development practices.