9 ms·
I have this problem with a codebase I work on now. Basically, the program flow is: 1. Download file 2. Load file to local DB 3. Load local DB to cloud 4. Load c
by hermitdev 6y ago
I have this problem with a codebase I work on now. Basically, the program flow is:
1. Download file
2. Load file to local DB
3. Load local DB to cloud
4. Load cloud to different local DB
5. Generate file for other system.
Really annoying, really over-engineered, and of course, undocumented. To boot, it also utilizes dependency injection because... There are no unit tests, no mocking, nothing. No reason to use DI other than to obfuscate. Very frustrating. It's 10Ks worth of C# that I could do in a few hundred in Python (and have it perform better).
- apta 6y ago> It's 10Ks worth of C# that I could do in a few hundred in Python (and have it perform better). You could also re-write the same code in C#, and have it perform even better than the hypothetical Python version, while being around the same length.