text stringlengths 0 2.35k |
|---|
**Bartlomiej Święcki:** Yes, exactly. |
**Jon Calhoun:** But if Jerod wants to summarize this as "You should chase after people while you're coding", we can do that, too. \[laughter\] |
**Johnny Boursiquot:** We can do that too, we can do that too. Jon, did you bring one? |
**Jon Calhoun:** I did not. |
**Johnny Boursiquot:** You did not. |
**Jon Calhoun:** I can say I agree with Bart though. I like the idea of thinking about other ways... Johnny, you have a standing desk, don't you? |
**Johnny Boursiquot:** Yeah, I can raise it up and take it back down when I need to. |
**Jon Calhoun:** I used one of those for a while, and basically what I've found was that I didn't like changing my setup all the time... And because I have enough space in my house, what I ended up doing was just getting a desk that's always standing, and putting a walking treadmill under it. I've found that depending ... |
**Johnny Boursiquot:** Alright, alright, alright... That's good. I didn't bring an unpopular opinion, but I thought of one as we were having this powwow. One thing we didn't get to talk about, but that I am gonna do a show on... So that's the unpopular opinion - I'm doing a show on blockchain at some point in the futur... |
**Bartlomiej Święcki:** It's a dangerous opinion. |
**Jon Calhoun:** So your unpopular opinion is that you think you should do a blockchain show. |
**Johnny Boursiquot:** Yeah, exactly. I think I need to do an episode on blockchain. But yeah, that's gonna be unpopular. Yeah, it's brutal out there, man... \[laughs\] |
**Jon Calhoun:** I'm honestly curious if that's unpopular or just incredibly polarizing... Because there's definitely some people who agree with you doing a show on that. I can't imagine -- I don't know how many though... |
**Johnny Boursiquot:** Right. Well, I'm hoping folks won't shoot the messenger. I'm just the messenger. Look, I just don't want us to bury our heads in the sand and pretend this thing doesn't exist, because clearly, it pisses off a lot of people. So let's just talk about it, like we do most things. Let's just talk abou... |
• The speaker discusses the theoretical aspect of cryptography and mathematics. |
• The benefits of finding practical applications for cryptographic theories. |
• Introduction to IMUDB (Immutable Database) as a live database that uses machinery to prove and verify data integrity. |
• Overview of SignalWire, an API provider offering low-latency video communication solutions. |
• Discussion about immutable databases, specifically EmuDB, developed by the Code Notary team. |
• The concept of immutable databases and their benefits for maintaining data integrity. |
• Interview with Bart Sienczki and Hiranimo Irazapal, developers of EmuDB, to discuss their experience using Go in building this technology. |
• Immutable databases aim to preserve the history and state of data at a particular point in time |
• They help maintain a trail or log of changes over time for auditability and understanding how data changed |
• Immutability focuses on not altering existing records, but rather adding new ones with updated information |
• This approach is useful for tracking critical or historical data that should not be altered |
• Different use cases for databases: tracking changes over time vs. relying on current state |
• Immutability as protection against tampering with history |
• Banking application example: checking balance and transactions |
• Importance of verifiability in immutability databases |
• Clarification of term "immutability": appending-only data structures vs. verifiable history |
• Discussion of verifiable databases, where current state and history are independent |
• Tamper detection and integrity validation |
• Cryptographic verifiability of data |
• Immutable databases capture complete state with hash values at every moment |
• Client only needs to keep track of the current state, not the entire history |
• Deletion methods: logical deletion vs physical deletion |
• Physical deletion involves actually removing data while maintaining proof of its existence |
• Use cases for immutable databases: GDPR requirements, avoiding data tampering and ensuring consistency |
• Benefits of using FireHydrant for incident management and automation |
• Features of FireHydrant, including incident tooling, service catalogs, and incident analytics |
• Importance of immutable databases and their ability to provide a high degree of confidence in data integrity |
• Use cases for immutable databases, such as financial transactions and health records |
• Background on the development of Inmudev and its goal of making immutable databases easy to use |
• Previous experience with digital right management and applied cryptography at IBM |
• Database architecture with both SQL and key-value store capabilities |
• Dual modality for accessing data: traditional RDBMS and append-only log |
• Log-based storage as verifiable transparency logs |
• Indexing possibility for efficient querying |
• Temporal capabilities to query database as it was in the past |
• Addition of SQL capabilities on top of key-value database |
• Isolation between SQL and key-value store entries |
• Advantages of using SQL: easier application modeling and indexing |
• Possibility to verify data in SQL |
• Admitting and correcting mistakes is essential in working with immutable databases like MUDB |
• Immutable databases provide auditability of history, allowing corrections to be made without altering the past state |
• The concept of "freezing" values in the database can create a record of past events |
• Using immutable databases can improve security by preventing changes to released code or data |
• Developers may struggle with admitting mistakes and correcting them due to fear of being seen as incompetent |
• Immutable databases can require convincing other clients to update their local state, making rollback more difficult |
• Executive order on cybersecurity and software bill of materials (SBOM) |
• Origins of technologies like QLDB and EMUDB |
• Software bill of materials (SBOM) as a solution for verifying software dependencies and vulnerabilities |
• Use of immutable ledgers to store and verify SBOM information |
• Benefits of immutability in preventing tampering with SBOM data |
• Example use case: identifying vulnerable components in software infrastructure using SBOM |
• Code Notary uses immutability to store information |
• Log4J vulnerability highlighted importance of software bill of materials |
• Immutability requires operational procedures like data compaction |
• Go was chosen for its benefits in performance, concurrency, and simplicity |
• Google's use of Go adds credibility to its suitability for large-scale deployments |
• Code readability is also a key advantage of using Go |
• Discussion of contentment and personal preferences |
• Formatting and coding preferences (Go vs C++) |
• Unpopular opinions segment introduction |
• Bar's unpopular opinion on working environment and physical limitations |
• Bart's unpopular opinion on exercise and using muscles while working |
• Discussing projects while engaging in physical activities |
• Exploring non-traditional work environments that incorporate body movement |
• Standing desks and walking treadmills as alternatives to traditional seating |
• Limitations of implementing interactive workspaces due to office space constraints |
• Considering the development of a show on blockchain technology |
• Follow-ups and clarifications on previous discussions |
• Announcement for first-time listeners to subscribe at gotime.fm |
• Request for reviews and recommendations from long-term listeners |
• Acknowledgment of sponsors: Fastly, Breakmaster Cylinder |
• Preview of next week's episode with Ed Welch discussing logging |
[0.00 --> 3.68] The cryptography itself and mathematics can be very theoretical. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.