• 0 Posts
  • 193 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • IT professional for 20 years. C/C++ developer for 10 years prior to that.

    My first job out of college was mostly luck. I took a job doing tech support but after a couple of years was able to transition into development work.

    Virtually every job since that first one has been thanks to connections I made among coworkers. I got my current job because I knew two employees here. One of them was a co-founder of the company, and somebody I’ve known since the 1990’s and worked with at 3 other companies prior to this.










  • You would do well to go read up on the 1990 AT&T long distance network collapse. A single line of changed code, rolled out months earlier, ultimately triggered what you might call these days a DDoS attack that took down all 114 long distance telephone switches in their global network. Over 50 million long distance calls were blocked in the 9 hours it took them to identify the cause and roll out a fix.

    AT&T prided itself on the thoroughness of their testing & rollout strategy for any code changes. The bug that took them down was both timing-dependent and load-dependent, making it extremely difficult to test for, and required fairly specific real world conditions to trigger. That’s how it went unnoticed for months before it triggered.









  • The issue with cloud providers like AWS is that they charge for virtually everything, and that makes it easy to rack up charges if you forget about something you spun up as a test last week and forgot to terminate it. For larger companies it can be a significant issue. So there are other companies out there that you can use to scan your entire AWS account, summarize what you’re using, and highlight things you may not need any more. They’ll also recommend cost savings measures like paying for a year of server time up front instead of paying as you go. If you know you’ll need a server for a year then paying annually is a lot less expensive.

    On the plus side, you don’t need to deal with things like hardware failures. We have a large AWS environment where I work, and we’ll occasionally get an email informing us that an instance is “running on degraded hardware”. A simple reboot (power cycle) will move the instance to new hardware. And if you decide you need more RAM, more CPUs etc. then it’s also as simple as rebooting.