text stringlengths 0 2.35k |
|---|
**Mat Ryer:** I like that too though, that people can start higher up in the stack, and can still be doing things without understanding everything. Because I've seen it, people held themselves back because they think "Well, I just don't know how all of this stuff, and I need to--" They don't know that they don't need t... |
And I'm afraid - put down your goblets of red wine. Yes, it was definitely wine, yeah... And put also away those sandwiches of miscellaneous... No, there weren't any sandwiches. No, let's just not do the sandwiches, but we'll do the wine but, and then keep the wine, because they think it's blood. |
Okay, and that's all the time we have on today's Ghost Time. Thanks for joining us, everybody. See you next time, and stay spoopy! |
• The host discusses a personal anecdote about being triggered by a former boss's behavior. |
• Sourcegraph is introduced as the sponsor of the episode and its product, CodeSearch, is discussed in relation to code intelligence platforms. |
• Joel Cortler, Product Manager of Code Insights for Sourcegraph, explains how Code Insights works and its potential uses. |
• Code Insights allows users to turn their code base into a database and interact with it through search functions such as regular expressions and structural searches. |
• The host and Joel discuss the versatility of Code Insights and its ability to uncover new use cases. |
• A link is provided in the show notes for viewers to learn more about how teams are using Code Insights. |
• Introduction to the spooky Go Time episode |
• Discussion of Chris Brando's career in horror and his ability to predict plot twists |
• Natalie Pistonowitch's confession of being scared of horror movies and preferring popcorn over film |
• D Kitchen's special appearance and discussion on the inconsistencies in horror films' physics and logic |
• Conversation about the variety of popcorn flavors available in different countries and regions, including a humorous anecdote about individual flavor programming and demand-based popping |
• Discussion of accidentally discovering a new flavor while experimenting with options |
• Explanation of the concept of "Blue Monday", an HTML sanitizer package in Go |
• Features and advantages of Blue Monday, including streaming parser, fixed memory, and opt-in approach |
• Responsibility and security concerns related to open-source projects |
• Horror story about a project interacting with Twitter API, resulting in a $1,000 bill due to misconfigured retries |
• Discussion of a $1,000 bill and its discovery |
• Importance of setting budgets and using budget alarms |
• Story of an AWS Lambda function causing a large unexpected bill due to an infinite loop writing to the same S3 bucket |
• Mention of another person's experience with a similar issue |
• Discussion of protecting against DDoS attacks |
• The DDoS team realized their system was the opposite of what they were trying to protect against. |
• A customer caused a massive spike in requests, exceeding 8 million per second, which broke the logging and visibility systems. |
• An intern wrote an infinite loop that caused the issue, but the company handled it professionally by having the customer own up to the mistake. |
• The DDoS team was involved in another incident where their own system's greedy regex caused a global failure of traffic processing due to excessive CPU consumption. |
• Incident recovery took around four hours |
• Teams used direct machine connections and Prometheus to troubleshoot |
• The incident affected everything, including DNS, TLS, HTTP, and was a "nightmare scenario" |
• Companies should prepare for unexpected events ("meteorites") that can cause significant disruptions |
• Break-glass procedures were well-documented but still took time to implement |
• Regular expressions are difficult to understand and write correctly |
• A previous talk on regular expressions mentioned their origins in math and finite automata |
• The importance of being prepared to break things when trying new approaches or coding |
• Learning from mistakes and the value of experience in becoming a better engineer |
• Writing good code and having good tests as essential for avoiding problems |
• Documenting every step taken, especially when working with unfamiliar systems |
• The need for playbooks, automation, and scripts to streamline tasks and reduce errors |
• Importance of documenting steps taken in a process |
• Value of having a blameless culture in the industry |
• Need for incident management tools and FireHydrant's unique approach |
• Importance of meeting companies where they are and providing immediate value with incident management solutions |
• Availability of free features for small teams up to 10 people on FireHydrant |
• Discussion of FireHydrant.com |
• Campfire ambiance and pretend scenario |
• Johnny's performance as a campfire storyteller |
• Slacker chat about imaginary marshmallows and GPU usage |
• Horror stories and humorous anecdotes from old computers and software |
• Energy costs and heating systems in Europe |
• Cost-effective alternatives to expensive electrical heaters (old computers) |
• Discussion of Electron apps and installation limits |
• The narrator had limited knowledge of C# at the time |
• They approached a problem by contacting Microsoft Professional Services, who advised against it as "reckless and foolish" |
• The narrator attempted to rename registry items on an Exchange server using a script and regexes, which appeared to work |
• They were concerned about the Active Directory name being a "magic value" and asked for a new one |
• The narrator discussed their experience with a scary question or problem that they don't know how to address |
• They reflected on how people often claim to know more than they actually do, especially when trying to get out of doing something |
• The conversation turns to a spooky Halloween party and the narrator begins telling a story about integrating systems and distributed system pitfalls. |
• System integration testing for a large-scale student project |
• Unexpected "thundering herd" situation due to concurrent login attempts from 4,000 students |
• Bottlenecks in the system that were not accounted for during development and testing |
• Impact on students waiting to log in, leading to delays and frustration |
• Personal reflection by an engineer on their role in causing the issue and feeling responsible for its consequences |
• Discussion on the sense of consequence and responsibility among engineers when working on complex systems with high stakes |
• Burnout from constantly thinking about consequences |
• The importance of being abstracted from the weight of consequences to avoid burnout |
• Predictability of bad consequences and lack of preparation for them in software engineering |
• Importance of setting up precautions and safety measures, like lifeguards do |
• Lack of consequences flowing down to engineers, leading to immoral decisions |
• Psychological experiments on people without their knowledge as an example of such decisions |
• A personal anecdote about joining a company using Kubernetes and Istio without understanding how they work |
• Unsecured Istio policy allowed open access to entire API for 9 months |
• APIs were broken after removing the unsecured policy and fixing other policies |
• Broken policies included YAML formatting issues and copied/pasted code without testing |
• Extremely secure environment can also cause problems due to IP firewalls and state tables overflows |
• Debugging extremely secure environments can be challenging, with connections being randomly dropped. |
• Discussion of security and potential for detection |
• Systems allowing or disallowing certain actions |
• Fire safety procedures and equipment use (foam, closing slack) |
• Database management and accidental updates to production systems |
• Restoring database after unintended update |
• Machine speed and efficiency in updating large datasets |
• Joking about running on Raspberry Pis vs. Intel Max processors |
• Discussion about the silence of a sound being distant |
• Unpopular Opinions segment on software security and inputs |
• Guest discussion on memory safety and sanitizing inputs |
• Comparison between Go's language features and potential vulnerabilities |
• Importance of validating user inputs in open-source projects |
• The importance of learning from past experiences and revisiting fundamental concepts |
• Using reflection to improve skills, but often avoiding it due to fear or embarrassment |
• Unpopular opinions on training and education, including the value of reviewing old material and learning from past experiences |
• Examples of books that provide a deep understanding of computing fundamentals, such as "But How Do It Know?" |
• The idea that even experienced professionals can benefit from reviewing basic concepts and learning new things |
• The speaker discusses the path to becoming a systems engineer and how some people may not realize they're doing it. |
• The importance of starting with fundamentals in computer science and exploring different styles and approaches to learning. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.