The only way to get an extra monitor during my first stint at AWS was to loot one from the desk of a departing colleague (before IT got their hands on it). Fortunately there was no shortage of departing colleagues.
Frugality at its best. Sometimes certain decisions prioritize frugality so much over anything else, the time lost fighting is more expensive than the savings.
For example, the DevDesktop policy. My org had an Apollo/FMC fleet that only allowed 2-4 CPU and 4-8 GB RAM configurations. Anything else would require manual financial approval and justification from L6+ manager. This is between 2022-2024.
Take the following example, to save maybe 20-30$/month. You make engineers' life miserable while paying the same amount but in hourly rate...
When you run VSCode with bunch of Java plugins (where each uses Java), good luck reliably debugging anything. Me and basically anyone in my team would get into situation that the DevDesktop could not handle it anymore and would be stuck, requiring manual/hard restart or wait until load-avg dropping from 100+.
I did the simplest trick, kept the m5.large DevDesktop, but manually added another Apollo ASG, attached the HostClass to a random Production fleet that already has thousands of hosts (still under/in my VP org). Happily lived with m5zn.4xlarge until I left. I am pretty sure the machine is still there and running... (As my access was cut off right away...)
Comments
The only way to get an extra monitor during my first stint at AWS was to loot one from the desk of a departing colleague (before IT got their hands on it). Fortunately there was no shortage of departing colleagues.
Frugality at its best. Sometimes certain decisions prioritize frugality so much over anything else, the time lost fighting is more expensive than the savings. For example, the DevDesktop policy. My org had an Apollo/FMC fleet that only allowed 2-4 CPU and 4-8 GB RAM configurations. Anything else would require manual financial approval and justification from L6+ manager. This is between 2022-2024.
Take the following example, to save maybe 20-30$/month. You make engineers' life miserable while paying the same amount but in hourly rate...
When you run VSCode with bunch of Java plugins (where each uses Java), good luck reliably debugging anything. Me and basically anyone in my team would get into situation that the DevDesktop could not handle it anymore and would be stuck, requiring manual/hard restart or wait until load-avg dropping from 100+. I did the simplest trick, kept the m5.large DevDesktop, but manually added another Apollo ASG, attached the HostClass to a random Production fleet that already has thousands of hosts (still under/in my VP org). Happily lived with m5zn.4xlarge until I left. I am pretty sure the machine is still there and running... (As my access was cut off right away...)
Remember the “Frupidity” wiki page?