Joe LeBlanc
@jlleblanc.com
Coder, manager, and software engineering leader.
Also an author, sometimes entrepreneur, urbanist, amateur cook
🏳️🌈
📍GR, MI
Also an author, sometimes entrepreneur, urbanist, amateur cook
🏳️🌈
📍GR, MI
Back to the real estate cost question: in the case of OpenAI specifically, let’s say they massively overbuild. They can split off part and rent it out to another company very profitably. All the infrastructure is ready to go in a suitable location.
October 31, 2025 at 1:40 AM
Back to the real estate cost question: in the case of OpenAI specifically, let’s say they massively overbuild. They can split off part and rent it out to another company very profitably. All the infrastructure is ready to go in a suitable location.
More thoughts here.
If you’re building a data center, you want it to be in a place where there’s at the very least daily FedEx service. Stuff breaks and you will need to replace it immediately so your quality of service doesn’t suffer.
If you’re building a data center, you want it to be in a place where there’s at the very least daily FedEx service. Stuff breaks and you will need to replace it immediately so your quality of service doesn’t suffer.
October 31, 2025 at 1:40 AM
More thoughts here.
If you’re building a data center, you want it to be in a place where there’s at the very least daily FedEx service. Stuff breaks and you will need to replace it immediately so your quality of service doesn’t suffer.
If you’re building a data center, you want it to be in a place where there’s at the very least daily FedEx service. Stuff breaks and you will need to replace it immediately so your quality of service doesn’t suffer.
C) fair point, but that can be an issue in rural areas as well.
D) they care about stable electricity and disaster prevention than hot weather. Going back a couple decades here: Rackspace was built in San Antonio because it’s supposedly the least seismically active city in the US
D) they care about stable electricity and disaster prevention than hot weather. Going back a couple decades here: Rackspace was built in San Antonio because it’s supposedly the least seismically active city in the US
October 31, 2025 at 1:02 AM
C) fair point, but that can be an issue in rural areas as well.
D) they care about stable electricity and disaster prevention than hot weather. Going back a couple decades here: Rackspace was built in San Antonio because it’s supposedly the least seismically active city in the US
D) they care about stable electricity and disaster prevention than hot weather. Going back a couple decades here: Rackspace was built in San Antonio because it’s supposedly the least seismically active city in the US
I’ll try.
A) they have to be able to recruit people to run them who are willing to live near the data center. Also, stable electricity, which much of rural America does not have.
B) doesn’t really matter: server farms tend to be unbelievably high-rent per square foot.
A) they have to be able to recruit people to run them who are willing to live near the data center. Also, stable electricity, which much of rural America does not have.
B) doesn’t really matter: server farms tend to be unbelievably high-rent per square foot.
October 31, 2025 at 1:02 AM
I’ll try.
A) they have to be able to recruit people to run them who are willing to live near the data center. Also, stable electricity, which much of rural America does not have.
B) doesn’t really matter: server farms tend to be unbelievably high-rent per square foot.
A) they have to be able to recruit people to run them who are willing to live near the data center. Also, stable electricity, which much of rural America does not have.
B) doesn’t really matter: server farms tend to be unbelievably high-rent per square foot.
Git is also not good software at times. Merging and rebasing can get complicated quickly, especially when there are conflicts. If you don’t have a good grasp on git internals and advanced concepts, you will get completely lost before long.
October 27, 2025 at 2:09 AM
Git is also not good software at times. Merging and rebasing can get complicated quickly, especially when there are conflicts. If you don’t have a good grasp on git internals and advanced concepts, you will get completely lost before long.
It’s good software in that I rarely think about what version of Git I’m running. The same commands I was writing 15+ years ago still work today. I can commit, pull push, and branch easily. If I mess up, it’s usually easy to recover with predictable commands.
October 27, 2025 at 2:09 AM
It’s good software in that I rarely think about what version of Git I’m running. The same commands I was writing 15+ years ago still work today. I can commit, pull push, and branch easily. If I mess up, it’s usually easy to recover with predictable commands.
I’m going back to newsletters
October 8, 2025 at 11:36 AM
I’m going back to newsletters
My husband and I did a watch-through after he moved in with me in Austin. I think we ALL need not just Coach Taylor, but Tami too
October 7, 2025 at 1:11 AM
My husband and I did a watch-through after he moved in with me in Austin. I think we ALL need not just Coach Taylor, but Tami too
After using Rails at work for 8 years and now using newer platforms/frameworks, I’m not going back.
Sure, there will be existing Rails projects around companies for years to come. But if you’re looking for a time investment for the next decade of your career, I wouldn’t recommend Rails.
Sure, there will be existing Rails projects around companies for years to come. But if you’re looking for a time investment for the next decade of your career, I wouldn’t recommend Rails.
September 27, 2025 at 8:14 PM
After using Rails at work for 8 years and now using newer platforms/frameworks, I’m not going back.
Sure, there will be existing Rails projects around companies for years to come. But if you’re looking for a time investment for the next decade of your career, I wouldn’t recommend Rails.
Sure, there will be existing Rails projects around companies for years to come. But if you’re looking for a time investment for the next decade of your career, I wouldn’t recommend Rails.
And Supabase isn’t the only contender here: you have Firebase, Convex, whatever DB you want + Prisma, etc…
All of them are either type-safe, or are easy to use with type-safe languages. And GenZ software engineers are starting with them instead of Rails.
All of them are either type-safe, or are easy to use with type-safe languages. And GenZ software engineers are starting with them instead of Rails.
September 27, 2025 at 8:14 PM
And Supabase isn’t the only contender here: you have Firebase, Convex, whatever DB you want + Prisma, etc…
All of them are either type-safe, or are easy to use with type-safe languages. And GenZ software engineers are starting with them instead of Rails.
All of them are either type-safe, or are easy to use with type-safe languages. And GenZ software engineers are starting with them instead of Rails.