• 0 Posts
  • 102 Comments
Joined 3 years ago
cake
Cake day: 23 June 2023

help-circle

  • I have a few decades programming experience, as a professional software engineer, an open source developer, and a DevOps engineer. There is no way in hell I would do a code review where 15k lines were added and a similar amount of lines removed without having a long discussion with the person who made those changes. I’d want to ask a lot of detailed questions about the changes, questions that an LLM isn’t likely to answer, and most definitely not questions I’d be inclined to try to type into an LLM to try to get an answer.

    Over the years I’ve dealt with all manner of bugs, from overflows & underflows, to bad assumptions about logic flow, and much much more. The whole purpose of pointed questioning of the author is to be comfortable with decisions made in the code and to minimize the chances of all sorts of potential bugs.









  • 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.











  • Spoofing is a whole hell of a lot easier said than done. Content delivery networks like Akamai, Cloudflare, etc. all know exactly how different versions of different browsers present themselves, and will catch the tiniest mistake.

    When a browser requests a web page it sends a series of headers, which identify both itself and the request it’s making. But virtually every browser sends a slightly different set of headers, and in different orders. So Akamai, for example can tell that you are using Chrome solely by what headers are in the request and the order they are in, even if you spoof your User-Agent string to look like Firefox.

    So to successfully spoof a connection you need to decide how you want to present yourself (do I really want them to think I’m using Opera when I’m using Firefox, or do I just want to randomize things to keep them guessing). In the first case you need to be very careful to ensure your browser sends requests that exactly matches how Opera sends them. One header, or even one character out of place can be enough for these companies to recognize you’re spoofing your connection.