briandilley's comments

briandilley | 1 year ago | on: Ask HN: Who is hiring? (February 2025)

Current Electric Vehicles | EV Technologist / Electro-Mechanical Engineer | In-Peson (Northridge, CA) | Full-Time

  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.
Please contact jobs (at) current-la.com for a more detailed job description!

briandilley | 2 years ago | on: WTF Happened in 1971? (2019)

Unix epoch starts Jan 1st 1970 - could this have anything to do with it? As in, we started getting better at keeping records and more detailed data because of computers?

briandilley | 2 years ago | on: Beyond SQL: A relational database for modern applications

I have yet to come across a replacement for SQL that makes it easier, or more concise, while also remaining feature rich. Not knocking this, but SQL is a pretty solid and time-tested technology for querying structured data. Alas, if we don't experiment then I guess we wont get better.

briandilley | 3 years ago | on: Joint statement by the Department of the Treasury, Federal Reserve, and FDIC

> Just a way to talk about what you're doing without specifically mentioning that "we're doing this to get more money", which is the actual reason anyone ever does anything.

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.

briandilley | 4 years ago | on: We don’t use a staging environment

> Pre-live environments are never at parity with production

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.

page 1