- please put this broken crap of 15 services written in 6 different programming languages on a 50 node cluster so we can read and write data with 300 kbit/s.
2 years later:
- could you do something about this cluster, it costs us too much.
We are talking about 10+ years old companies. I quite often save significant amount of money for such companies which could have been saved from the beginning by not doing something completely silly.
There was a great white paper investigated how software gets bigger and bigger. They used the command line tool true as an example. I can't find it anymore but it was really an eye opener.
You are assuming that every city allows cars into dining areas. There are many examples in Europe where this is not the case. The whole electric vs combustion car argument is predicated on the fact that we need cars in inner cities at all.
Mmmmm, I don't think I assumed that. I'm pretty sure I described my current scenario, and the scenarios of others who live in similar places. I know how loathsome this scenario is because I have lived and traveled in those places in Europe you mention.
The sad reality is that cars are so thoroughly stuck into the urban areas in so many places and it will take longer than my lifespan to unring that bell here in America and fix mobility in urban centers. However, we can potentially unring some smaller bells a hell of a lot sooner with EVs. It's a really valuable transitional tech in that regard, in my eyes. I don't think ICE will ever truly go away, due to the huge power density of the fuel. But, if we just replace say, half of the passenger fleet within say, 10-100 miles of american cities with EVs as they age out by like 2035, life will be much better here from that point until I die. Of course if we can increase the portion of those cars that age out and are not replaced, especially in a 1 mile radius of the city center, that's a much larger win than swapping an ICE SUV for an EV SUV.
I'm glad I work for a company that uses Office 365 instead of the equivalent of Google or others. I really like Office products, for all their faults they allow me to work more productively than the alternatives. So I don't know why I have less in my head just because I can work well with Excel and Outlook.
It is not as much the enterprise security industry as it is better security for all. Problem with the current implementation with ssh keys is that there are non-trivial problems with it. For example how do you revoke a key? It is not possible in a central AAA service to revoke access for a user like it is possible for other kind of auth systems. Ssh and ssh keys were designed in an era where security was not really the primary concern. I think Facebook DevOps team had some detailed article how they manage ssh access to fb production with keys.
I have moved over to doas a while back and it is really amazing. Why? Because it JUST WORKS. I do not need to learn a configuration language to understand what is going on. It does very little and that is exactly what 80% of the users need. We should use more software like that. Simplicity is the best design pattern.
- please put this broken crap of 15 services written in 6 different programming languages on a 50 node cluster so we can read and write data with 300 kbit/s.
2 years later:
- could you do something about this cluster, it costs us too much.