Podcast appearances and mentions of paul dix

In the push to integrate data into development, time series databases have gained significant importance. These databases capture time-stamped data from servers and sensors, enabling the collection and storage of valuable information. InfluxDB, a leading open-source time series database technology by InfluxData, has partnered with Amazon Web Services (AWS) to offer a managed open-source service for time series databases. Brad Bebee, General Manager of Amazon Neptune and Amazon Timestream highlighted the challenges faced by customers managing open-source Influx database instances, despite appreciating its API and performance. To address this, AWS initiated a private beta offering a managed service tailored to customer needs. Paul Dix, Co-founder and CTO of InfluxData joined Bebee, and highlighted Influx's prized utility in tracking measurements, metrics, and sensor data in real-time. AWS's Timestream complements this by providing managed time series database services, including TimesTen for Live Analytics and Timestream for Influx DB. Bebee emphasized the growing relevance of time series data and customers' preference for managed open-source databases, aligning with AWS's strategy of offering such services. This partnership aims to simplify database management and enhance performance for customers utilizing time series databases. Learn more from The New Stack about time series databases:What Are Time Series Databases, and Why Do You Need Them?Amazon Timestream: Managed InfluxDB for Time Series Data Install the InfluxDB Time-Series Database on Ubuntu Server 22.04Join our community of newsletter subscribers to stay on top of the news and at the top of your game. 

Summary Building a database engine requires a substantial amount of engineering effort and time investment. Over the decades of research and development into building these software systems there are a number of common components that are shared across implementations. When Paul Dix decided to re-write the InfluxDB engine he found the Apache Arrow ecosystem ready and waiting with useful building blocks to accelerate the process. In this episode he explains how he used the combination of Apache Arrow, Flight, Datafusion, and Parquet to lay the foundation of the newest version of his time-series database. Announcements Hello and welcome to the Data Engineering Podcast, the show about modern data management Dagster offers a new approach to building and running data platforms and data pipelines. It is an open-source, cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability, a declarative programming model, and best-in-class testability. Your team can get up and running in minutes thanks to Dagster Cloud, an enterprise-class hosted solution that offers serverless and hybrid deployments, enhanced security, and on-demand ephemeral test deployments. Go to dataengineeringpodcast.com/dagster (https://www.dataengineeringpodcast.com/dagster) today to get started. Your first 30 days are free! Data lakes are notoriously complex. For data engineers who battle to build and scale high quality data workflows on the data lake, Starburst powers petabyte-scale SQL analytics fast, at a fraction of the cost of traditional methods, so that you can meet all your data needs ranging from AI to data applications to complete analytics. Trusted by teams of all sizes, including Comcast and Doordash, Starburst is a data lake analytics platform that delivers the adaptability and flexibility a lakehouse ecosystem promises. And Starburst does all of this on an open architecture with first-class support for Apache Iceberg, Delta Lake and Hudi, so you always maintain ownership of your data. Want to see Starburst in action? Go to dataengineeringpodcast.com/starburst (https://www.dataengineeringpodcast.com/starburst) and get $500 in credits to try Starburst Galaxy today, the easiest and fastest way to get started using Trino. Join us at the top event for the global data community, Data Council Austin. From March 26-28th 2024, we'll play host to hundreds of attendees, 100 top speakers and dozens of startups that are advancing data science, engineering and AI. Data Council attendees are amazing founders, data scientists, lead engineers, CTOs, heads of data, investors and community organizers who are all working together to build the future of data and sharing their insights and learnings through deeply technical talks. As a listener to the Data Engineering Podcast you can get a special discount off regular priced and late bird tickets by using the promo code dataengpod20. Don't miss out on our only event this year! Visit dataengineeringpodcast.com/data-council (https://www.dataengineeringpodcast.com/data-council) and use code dataengpod20 to register today! Your host is Tobias Macey and today I'm interviewing Paul Dix about his investment in the Apache Arrow ecosystem and how it led him to create the latest PFAD in database design Interview Introduction How did you get involved in the area of data management? Can you start by describing the FDAP stack and how the components combine to provide a foundational architecture for database engines? This was the core of your recent re-write of the InfluxDB engine. What were the design goals and constraints that led you to this architecture? Each of the architectural components are well engineered for their particular scope. What is the engineering work that is involved in building a cohesive platform from those components? One of the major benefits of using open source components is the network effect of ecosystem integrations. That can also be a risk when the community vision for the project doesn't align with your own goals. How have you worked to mitigate that risk in your specific platform? Can you describe the operational/architectural aspects of building a full data engine on top of the FDAP stack? What are the elements of the overall product/user experience that you had to build to create a cohesive platform? What are some of the other tools/technologies that can benefit from some or all of the pieces of the FDAP stack? What are the pieces of the Arrow ecosystem that are still immature or need further investment from the community? What are the most interesting, innovative, or unexpected ways that you have seen parts or all of the FDAP stack used? What are the most interesting, unexpected, or challenging lessons that you have learned while working on/with the FDAP stack? When is the FDAP stack the wrong choice? What do you have planned for the future of the InfluxDB IOx engine and the FDAP stack? Contact Info LinkedIn (https://www.linkedin.com/in/pauldix/) pauldix (https://github.com/pauldix) on GitHub Parting Question From your perspective, what is the biggest gap in the tooling or technology for data management today? Closing Announcements Thank you for listening! Don't forget to check out our other shows. Podcast.__init__ (https://www.pythonpodcast.com) covers the Python language, its community, and the innovative ways it is being used. The Machine Learning Podcast (https://www.themachinelearningpodcast.com) helps you go from idea to production with machine learning. Visit the site (https://www.dataengineeringpodcast.com) to subscribe to the show, sign up for the mailing list, and read the show notes. If you've learned something or tried out a project from the show then tell us about it! Email hosts@dataengineeringpodcast.com (mailto:hosts@dataengineeringpodcast.com)) with your story. Links FDAP Stack Blog Post (https://www.influxdata.com/blog/flight-datafusion-arrow-parquet-fdap-architecture-influxdb/) Apache Arrow (https://arrow.apache.org/) DataFusion (https://arrow.apache.org/datafusion/) Arrow Flight (https://arrow.apache.org/docs/format/Flight.html) Apache Parquet (https://parquet.apache.org/) InfluxDB (https://www.influxdata.com/products/influxdb/) Influx Data (https://www.influxdata.com/) Podcast Episode (https://www.dataengineeringpodcast.com/influxdb-timeseries-data-platform-episode-199) Rust Language (https://www.rust-lang.org/) DuckDB (https://duckdb.org/) ClickHouse (https://clickhouse.com/) Voltron Data (https://voltrondata.com/) Podcast Episode (https://www.dataengineeringpodcast.com/voltron-data-apache-arrow-episode-346/) Velox (https://github.com/facebookincubator/velox) Iceberg (https://iceberg.apache.org/) Podcast Episode (https://www.dataengineeringpodcast.com/iceberg-with-ryan-blue-episode-52/) Trino (https://trino.io/) ODBC == Open DataBase Connectivity (https://en.wikipedia.org/wiki/Open_Database_Connectivity) GeoParquet (https://github.com/opengeospatial/geoparquet) ORC == Optimized Row Columnar (https://orc.apache.org/) Avro (https://avro.apache.org/) Protocol Buffers (https://protobuf.dev/) gRPC (https://grpc.io/) The intro and outro music is from The Hug (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/Love_death_and_a_drunken_monkey/04_-_The_Hug) by The Freak Fandango Orchestra (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/) / CC BY-SA (http://creativecommons.org/licenses/by-sa/3.0/)

For our very first episode, we welcome a special guest, Paul Dix, the CTO of InfluxData.He starts by giving us an overview of InfluxDB, an open source time series database used by developers to track server and application data. He takes us back to the early days of InfluxDB and explains how it came into existence, starting with the challenges they faced with their initial SaaS application and how they made the decision to repurpose their infrastructure and create this open source database. Paul also sheds light on the popularity of the programming language Go, which had a significant influence on their decision to use it for their project.He takes us through the journey of InfluxDB's development and the improvements that have been made over the years. He emphasizes the enhancements made in versions 0.11 and 1.0 to improve performance and query capabilities. Moreover, he shares their decision to explore using Rust for certain parts of the project and the positive impact it has had. Moving forward, the conversation delves into the challenges of managing high volumes of data in time series databases.Paul talks about the solutions they implemented, such as using BoltDB and developing the time-structured merge tree storage engine. We then dive into the decision to rewrite InfluxDB in Rust and the benefits it offers. He explains the improved performance, concurrency, and error handling that Rust brings to the table. Paul goes on to discuss the development process and how the engineering team has embraced Rust across their projects.As the conversation progresses, we touch on the performance improvements in InfluxDB 3 and the future plans for the database. Paul shares their vision of incorporating additional features and integrating with other tools and languages. He also mentions InfluxDB's involvement in open-source projects like Apache Aero Rust and Data Fusion, highlighting their ambition to extend beyond metric data. Paul concludes the conversation by discussing the standards and libraries in analytics, the role of Apache Iceberg, and the collaboration among data and analytics companies. He provides advice for getting started with Rust and InfluxDB, urging listeners to engage in hands-on projects and learn from books and online documentation.Thank you, Paul, for sharing your insights and expertise.

This is Rust in Production, a podcast about companies who use Rust to shape the future of infrastructure. We follow their journey in pursuit of more reliable and efficient software as they solve some of the most challenging technical problems in the world.I'm your host, Matthias Endler, and I'm a software engineer at corrode, a consultancy that helps companies make the most of Rust. I've been using Rust since 2015, have been a member of the Rust Cologne meetup since Rust 1.0 and ran a YouTube channel called "Hello Rust".There are plenty of great podcasts about Rust, but I felt that there was a missing piece. I wanted to hear more about how companies who use Rust in production. What are the challenges they face? How do they overcome them? What are the benefits of using Rust? How does the company find and hire Rust developers? And what advice would they give to other companies who want to use Rust.I sit down with decision-makers from companies that bet big on Rust and ask them in-depth questions about what they learned along the way. New episodes air every two weeks on Thursdays at 4pm UTC. If you don't want to miss out, please subscribe on Spotify, Apple Podcasts, or wherever you listen to podcasts. This helps other people find the show and supports our work.If you want to learn more about the show, please visit corrode.dev/podcast. Stay tuned for the first episode, where I talk to Paul Dix from InfluxData about how they use Rust in the latest version of InfluxDB.

Richard Seroter, Director of Outbound Product Management at Google, joins Corey on Screaming in the Cloud to discuss what's new at Google. Corey and Richard discuss how AI can move from a novelty to truly providing value, as well as the importance of people maintaining their skills and abilities rather than using AI as a black box solution. Richard also discusses how he views the DevRel function, and why he feels it's so critical to communicate expectations for product launches with customers. About RichardRichard Seroter is Director of Outbound Product Management at Google Cloud. He's also an instructor at Pluralsight, a frequent public speaker, and the author of multiple books on software design and development. Richard maintains a regularly updated blog (seroter.com) on topics of architecture and solution design and can be found on Twitter as @rseroter. Links Referenced: Google Cloud: https://cloud.google.com Personal website: https://seroter.com Twitter: https://twitter.com/rseroter LinkedIn: https://www.linkedin.com/in/seroter/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Human-scale teams use Tailscale to build trusted networks. Tailscale Funnel is a great way to share a local service with your team for collaboration, testing, and experimentation.  Funnel securely exposes your dev environment at a stable URL, complete with auto-provisioned TLS certificates. Use it from the command line or the new VS Code extensions. In a few keystrokes, you can securely expose a local port to the internet, right from the IDE.I did this in a talk I gave at Tailscale Up, their first inaugural developer conference. I used it to present my slides and only revealed that that's what I was doing at the end of it. It's awesome, it works! Check it out!Their free plan now includes 3 users & 100 devices. Try it at snark.cloud/tailscalescream Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. We have returning guest Richard Seroter here who has apparently been collecting words to add to his job title over the years that we've been talking to him. Richard, you are now the Director of Product Management and Developer Relations at Google Cloud. Do I have all those words in the correct order and I haven't forgotten any along the way?Richard: I think that's all right. I think my first job was at Anderson Consulting as an analyst, so my goal is to really just add more words to whatever these titles—Corey: It's an adjective collection, really. That's what a career turns into. It's really the length of a career and success is measured not by accomplishments but by word count on your resume.Richard: If your business card requires a comma, success.Corey: So, it's been about a year or so since we last chatted here. What have you been up to?Richard: Yeah, plenty of things here, still, at Google Cloud as we took on developer relations. And, but you know, Google Cloud proper, I think AI has—I don't know if you've noticed, AI has kind of taken off with some folks who's spending a lot the last year… juicing up services and getting things ready there. And you know, myself and the team kind of remaking DevRel for a 2023 sort of worldview. So, yeah we spent the last year just scaling and growing and in covering some new areas like AI, which has been fun.Corey: You became profitable, which is awesome. I imagined at some point, someone wound up, like, basically realizing that you need to, like, patch the hole in the pipe and suddenly the water bill is no longer $8 billion a quarter. And hey, that works super well. Like, wow, that explains our utility bill and a few other things as well. I imagine the actual cause is slightly more complex than that, but I am a simple creature.Richard: Yeah. I think we made more than YouTube last quarter, which was a good milestone when you think of—I don't think anybody who says Google Cloud is a fun side project of Google is talking seriously anymore.Corey: I misunderstood you at first. I thought you said that you're pretty sure you made more than I did last year. It's like, well, yes, if a multi-billion dollar company's hyperscale cloud doesn't make more than I personally do, then I have many questions. And if I make more than that, I have a bunch of different questions, all of which could be terrifying to someone.Richard: You're killing it. Yeah.Corey: I'm working on it. So, over the last year, another trend that's emerged has been a pivot away—thankfully—from all of the Web3 nonsense and instead embracing the sprinkle some AI on it. And I'm not—people are about to listen to this and think, wait a minute, is he subtweeting my company? No, I'm subtweeting everyone's company because it seems to be a universal phenomenon. What's your take on it?Richard: I mean, it's countercultural now to not start every conversation with let me tell you about our AI story. And hopefully, we're going to get past this cycle. I think the AI stuff is here to stay. This does not feel like a hype trend to me overall. Like, this is legit tech with real user interest. I think that's awesome.I don't think a year from now, we're going to be competing over who has the biggest model anymore. Nobody cares. I don't know if we're going to hopefully lead with AI the same way as much as, what is it doing for me? What is my experience? Is it better? Can I do this job better? Did you eliminate this complex piece of toil from my day two stuff? That's what we should be talking about. But right now it's new and it's interesting. So, we all have to rub some AI on it.Corey: I think that there is also a bit of a passing of the buck going on when it comes to AI where I've talked to companies that are super excited about how they have this new AI story that's going to be great. And, “Well, what does it do?” “It lets you query our interface to get an answer.” Okay, is this just cover for being bad UX?Richard: [laugh]. That can be true in some cases. In other cases, this will fix UXes that will always be hard. Like, do we need to keep changing… I don't know, I'm sure if you and I go to our favorite cloud providers and go through their documentation, it's hard to have docs for 200 services and millions of pages. Maybe AI will fix some of that and make it easier to discover stuff.So in some cases, UIs are just hard at scale. But yes, I think in some cases, this papers over other things not happening by just rubbing some AI on it. Hopefully, for most everybody else, it's actually interesting, new value. But yeah, that's a… every week it's a new press release from somebody saying they're about to launch some AI stuff. I don't know how any normal human is keeping up with it.Corey: I certainly don't know. I'm curious to see what happens but it's kind of wild, too, because there you're right. There is something real there where you ask it to draw you a picture of a pony or something and it does, or give me a bunch of random analysis of this. I asked one recently to go ahead and rank the US presidents by absorbency and with a straight face, it did it, which is kind of amazing. I feel like there's a lack of imagination in the way that people talk about these things and a certain lack of awareness that you can make this a lot of fun, and in some ways, make that a better showcase of the business value than trying to do the straight-laced thing of having it explain Microsoft Excel to you.Richard: I think that's fair. I don't know how much sometimes whimsy and enterprise mix. Sometimes that can be a tricky part of the value prop. But I'm with you this some of this is hopefully returns to some more creativity of things. I mean, I personally use things like Bard or what have you that, “Hey, I'm trying to think of this idea. Can you give me some suggestions?” Or—I just did a couple weeks ago—“I need sample data for my app.”I could spend the next ten minutes coming up with Seinfeld and Bob's Burgers characters, or just give me the list in two seconds in JSON. Like that's great. So, I'm hoping we get to use this for more fun stuff. I'll be fascinated to see if when I write the keynote for—I'm working on the keynote for Next, if I can really inject something completely off the wall. I guess you're challenging me and I respect that.Corey: Oh, I absolutely am. And one of the things that I believe firmly is that we lose sight of the fact that people are inherently multifaceted. Just because you are a C-level executive at an enterprise does not mean that you're not also a human being with a sense of creativity and a bit of whimsy as well. Everyone is going to compete to wind up boring you to death with PowerPoint. Find something that sparks the imagination and sparks joy.Because yes, you're going to find the boring business case on your own without too much in the way of prodding for that, but isn't it great to imagine what if? What if we could have fun with some of these things? At least to me, that's always been the goal is to get people's attention. Humor has been my path, but there are others.Richard: I'm with you. I think there's a lot to that. And the question will be… yeah, I mean, again, to me, you and I talked about this before we started recording, this is the first trend for me in a while that feels purely organic where our customers, now—and I'll tell our internal folks—our customers have much better ideas than we do. And it's because they're doing all kinds of wild things. They're trying new scenarios, they're building apps purely based on prompts, and they're trying to, you know, do this.And it's better than what we just come up with, which is awesome. That's how it should be, versus just some vendor-led hype initiative where it is just boring corporate stuff. So, I like the fact that this isn't just us talking; it's the whole industry talking. It's people talking to my non-technical family members, giving me ideas for what they're using this stuff for. I think that's awesome. So yeah, but I'm with you, I think companies can also look for more creative angles than just what's another way to left-align something in a cell.Corey: I mean, some of the expressions on this are wild to me. The Photoshop beta with its generative AI play has just been phenomenal. Because it's weird stuff, like, things that, yeah, I'm never going to be a great artist, let's be clear, but being able to say remove this person from the background, and it does it, as best I can tell, seamlessly is stuff where yeah, that would have taken me ages to find someone who knows what the hell they're doing on the internet somewhere and then pay them to do it. Or basically stumble my way through it for two hours and it somehow looks worse afterwards than before I started. It's the baseline stuff of, I'm never going to be able to have it—to my understanding—go ahead just build me a whole banner ad that does this and hit these tones and the rest, but it is going to help me refine something in that direction, until I can then, you know, hand it to a professional who can take it from my chicken scratching into something real.Richard: If it will. I think that's my only concern personally with some of this is I don't want this to erase expertise or us to think we can just get lazy. I think that I get nervous, like, can I just tell it to do stuff and I don't even check the output, or I don't do whatever. So, I think that's when you go back to, again, enterprise use cases. If this is generating code or instructions or documentation or what have you, I need to trust that output in some way.Or more importantly, I still need to retain the skills necessary to check it. So, I'm hoping people like you and me and all our —every—all the users out there of this stuff, don't just offload responsibility to the machine. Like, just always treat it like a kind of slightly drunk friend sitting next to you with good advice and always check it out.Corey: It's critical. I think that there's a lot of concern—and I'm not saying that people are wrong on this—but that people are now going to let it take over their jobs, it's going to wind up destroying industries. No, I think it's going to continue to automate things that previously required human intervention. But this has been true since the Industrial Revolution, where opportunities arise and old jobs that used to be critical are no longer centered in quite the same way. The one aspect that does concern me is not that kids are going to be used to cheat on essays like, okay, great, whatever. That seems to be floated mostly by academics who are concerned about the appropriate structure of academia.For me, the problem is, is there's a reason that we have people go through 12 years of English class in the United States and that is, it's not to dissect of the work of long-dead authors. It's to understand how to write and how to tell us a story and how to frame ideas cohesively. And, “The computer will do that for me,” I feel like that potentially might not serve people particularly well. But as a counterpoint, I was told when I was going to school my entire life that you're never going to have a calculator in your pocket all the time that you need one. No, but I can also speak now to the open air, ask it any math problem I can imagine, and get a correct answer spoken back to me. That also wasn't really in the bingo card that I had back then either, so I am a hesitant to try and predict the future.Richard: Yeah, that's fair. I think it's still important for a kid that I know how to make change or do certain things. I don't want to just offload to calculators or—I want to be able to understand, as you say, literature or things, not just ever print me out a book report. But that happens with us professionals, too, right? Like, I don't want to just atrophy all of my programming skills because all I'm doing is accepting suggestions from the machine, or that it's writing my emails for me. Like, that still weirds me out a little bit. I like to write an email or send a tweet or do a summary. To me, I enjoy those things still. I don't want to—that's not toil to me. So, I'm hoping that we just use this to make ourselves better and we don't just use it to make ourselves lazier.Corey: You mentioned a few minutes ago that you are currently working on writing your keynote for Next, so I'm going to pretend, through a vicious character attack here, that this is—you know, it's 11 o'clock at night, the day before the Next keynote and you found new and exciting ways to procrastinate, like recording a podcast episode with me. My question for you is, how is this Next going to be different than previous Nexts?Richard: Hmm. Yeah, I mean, for the first time in a while it's in person, which is wonderful. So, we'll have a bunch of folks at Moscone in San Francisco, which is tremendous. And I [unintelligible 00:11:56] it, too, I definitely have online events fatigue. So—because absolutely no one has ever just watched the screen entirely for a 15 or 30 or 60-minute keynote. We're all tabbing over to something else and multitasking. And at least when I'm in the room, I can at least pretend I'll be paying attention the whole time. The medium is different. So, first off, I'm just excited—Corey: Right. It feels a lot ruder to get up and walk out of the front row in the middle of someone's talk. Now, don't get me wrong, I'll still do it because I'm a jerk, but I'll feel bad about it as I do. I kid, I kid. But yeah, a tab away is always a thing. And we seem to have taken the same structure that works in those events and tried to force it into more or less a non-interactive Zoom call, and I feel like that is just very hard to distinguish.I will say that Google did a phenomenal job of online events, given the constraints it was operating under. Production value is great, the fact that you took advantage of being in different facilities was awesome. But yeah, it'll be good to be back in person again. I will be there with bells on in Moscone myself, mostly yelling at people, but you know, that's what I do.Richard: It's what you do. But we missed that hallway track. You missed this sort of bump into people. Do hands-on labs, purposely have nothing to do where you just walk around the show floor. Like we have been missing, I think, society-wise, a little bit of just that intentional boredom. And so, sometimes you need at conference events, too, where you're like, “I'm going to skip that next talk and just see what's going on around here.” That's awesome. You should do that more often.So, we're going to have a lot of spaces for just, like, go—like, 6000 square feet of even just going and looking at demos or doing hands-on stuff or talking with other people. Like that's just the fun, awesome part. And yeah, you're going to hear a lot about AI, but plenty about other stuff, too. Tons of announcements. But the key is that to me, community stuff, learn from each other stuff, that energy in person, you can't replicate that online.Corey: So, an area that you have expanded into has been DevRel, where you've always been involved with it, let's be clear, but it's becoming a bit more pronounced. And as an outsider, I look at Google Cloud's DevRel presence and I don't see as much of it as your staffing levels would indicate, to the naive approach. And let's be clear, that means from my perspective, all public-facing humorous, probably performative content in different ways, where you have zany music videos that, you know, maybe, I don't know, parody popular songs do celebrate some exec's birthday they didn't know was coming—[fake coughing]. Or creative nonsense on social media. And the the lack of seeing a lot of that could in part be explained by the fact that social media is wildly fracturing into a bunch of different islands which, on balance, is probably a good thing for the internet, but I also suspect it comes down to a common misunderstanding of what DevRel actually is.It turns out that, contrary to what many people wanted to believe in the before times, it is not getting paid as much as an engineer, spending three times that amount of money on travel expenses every year to travel to exotic places, get on stage, party with your friends, and then give a 45-minute talk that spends two minutes mentioning where you work and 45 minutes talking about, I don't know, how to pick the right standing desk. That has, in many cases, been the perception of DevRel and I don't think that's particularly defensible in our current macroeconomic climate. So, what are all those DevRel people doing?Richard: [laugh]. That's such a good loaded question.Corey: It's always good to be given a question where the answers are very clear there are right answers and wrong answers, and oh, wow. It's a fun minefield. Have fun. Go catch.Richard: Yeah. No, that's terrific. Yeah, and your first part, we do have a pretty well-distributed team globally, who does a lot of things. Our YouTube channel has, you know, we just crossed a million subscribers who are getting this stuff regularly. It's more than Amazon and Azure combined on YouTube. So, in terms of like that, audience—Corey: Counterpoint, you definitionally are YouTube. But that's neither here nor there, either. I don't believe you're juicing the stats, but it's also somehow… not as awesome if, say, I were to do it, which I'm working on it, but I have a face for radio and it shows.Richard: [laugh]. Yeah, but a lot of this has been… the quality and quantity. Like, you look at the quantity of video, it overwhelms everyone else because we spend a lot of time, we have a specific media team within my DevRel team that does the studio work, that does the production, that does all that stuff. And it's a concerted effort. That team's amazing. They do really awesome work.But, you know, a lot of DevRel as you say, [sigh] I don't know about you, I don't think I've ever truly believed in the sort of halo effect of if super smart person works at X company, even if they don't even talk about that company, that somehow presents good vibes and business benefits to that company. I don't think we've ever proven that's really true. Maybe you've seen counterpoints, where [crosstalk 00:16:34]—Corey: I can think of anecdata examples of it. Often though, on some level, for me at least, it's been okay someone I tremendously respect to the industry has gone to work at a company that I've never heard of. I will be paying attention to what that company does as a direct result. Conversely, when someone who is super well known, and has been working at a company for a while leaves and then either trashes the company on the way out or doesn't talk about it, it's a question of, what's going on? Did something horrible happen there? Should we no longer like that company? Are we not friends anymore? It's—and I don't know if that's necessarily constructive, either, but it also, on some level, feels like it can shorthand to oh, to be working DevRel, you have to be an influencer, which frankly, I find terrifying.Richard: Yeah. Yeah. I just—the modern DevRel, hopefully, is doing a little more of product-led growth style work. They're focusing specifically on how are we helping developers discover, engage, scale, become advocates themselves in the platform, increasing that flywheel through usage, but that has very discreet metrics, it has very specific ownership. Again, personally, I don't even think DevRel should do as much with sales teams because sales teams have hundreds and sometimes thousands of sales engineers and sales reps. It's amazing. They have exactly what they need.I don't think DevRel is a drop in the bucket to that team. I'd rather talk directly to developers, focus on people who are self-service signups, people who are developers in those big accounts. So, I think the modern DevRel team is doing more in that respect. But when I look at—I just look, Corey, this morning at what my team did last week—so the average DevRel team, I look at what advocacy does, teams writing code labs, they're building tutorials. Yes, they're doing some in person events. They wrote some blog posts, published some videos, shipped a couple open-source projects that they contribute to in, like gaming sector, we ship—we have a couple projects there.They're actually usually customer zero in the product. They use the product before it ships, provides bugs and feedback to the team, we run DORA workshops—because again, we're the DevOps Research and Assessment gang—we actually run the tutorial and Docs platform for Google Cloud. We have people who write code samples and reference apps. So, sometimes you see things publicly, but you don't see the 20,000 code samples in the docs, many written by our team. So, a lot of the times, DevRel is doing work to just enable on some of these different properties, whether that's blogs or docs, whether that's guest articles or event series, but all of this should be in service of having that credible relationship to help devs use the platform easier. And I love watching this team do that.But I think there's more to it now than years ago, where maybe it was just, let's do some amazing work and try to have some second, third-order effect. I think DevRel teams that can have very discrete metrics around leading indicators of long-term cloud consumption. And if you can't measure that successfully, you've probably got to rethink the team.[midroll 00:19:20]Corey: That's probably fair. I think that there's a tremendous series of… I want to call it thankless work. Like having done some of those ridiculous parody videos myself, people look at it and they chuckle and they wind up, that was clever and funny, and they move on to the next one. And they don't see the fact that, you know, behind the scenes for that three-minute video, there was a five-figure budget to pull all that together with a lot of people doing a bunch of disparate work. Done right, a lot of this stuff looks like it was easy or that there was no work at all.I mean, at some level, I'm as guilty of that as anyone. We're recording a podcast now that is going to be handed over to the folks at HumblePod. They are going to produce this into something that sounds coherent, they're going to fix audio issues, all kinds of other stuff across the board, a full transcript, and the rest. And all of that is invisible to me. It's like AI; it's the magic box I drop a file into and get podcast out the other side.And that does a disservice to those people who are actively working in that space to make things better. Because the good stuff that they do never gets attention, but then the company makes an interesting blunder in some way or another and suddenly, everyone's out there screaming and wondering why these people aren't responding on Twitter in 20 seconds when they're finding out about this stuff for the first time.Richard: Mm-hm. Yeah, that's fair. You know, different internal, external expectations of even DevRel. We've recently launched—I don't know if you caught it—something called Jump Start Solutions, which were executable reference architectures. You can come into the Google Cloud Console or hit one of our pages and go, “Hey, I want to do a multi-tier web app.” “Hey, I want to do a data processing pipeline.” Like, use cases.One click, we blow out the entire thing in the platform, use it, mess around with it, turn it off with one click. Most of those are built by DevRel. Like, my engineers have gone and built that. Tons of work behind the scenes. Really, like, production-grade quality type architectures, really, really great work. There's going to be—there's a dozen of these. We'll GA them at Next—but really, really cool work. That's DevRel. Now, that's behind-the-scenes work, but as engineering work.That can be some of the thankless work of setting up projects, deployment architectures, Terraform, all of them also dropped into GitHub, ton of work documenting those. But yeah, that looks like behind-the-scenes work. But that's what—I mean, most of DevRel is engineers. These are folks often just building the things that then devs can use to learn the platforms. Is it the flashy work? No. Is it the most important work? Probably.Corey: I do have a question I'd be remiss not to ask. Since the last time we spoke, relatively recently from this recording, Google—well, I'd say ‘Google announced,' but they kind of didn't—Squarespace announced that they'd be taking over Google domains. And there was a lot of silence, which I interpret, to be clear, as people at Google being caught by surprise, by large companies, communication is challenging. And that's fine, but I don't think it was anything necessarily nefarious.And then it came out further in time with an FAQ that Google published on their site, that Google Cloud domains was a part of this as well. And that took a lot of people aback, in the sense—not that it's hard to migrate a domain from one provider to another, but it brought up the old question of, if you're building something in cloud, how do you pick what to trust? And I want to be clear before you answer that, I know you work there. I know that there are constraints on what you can or cannot say.And for people who are wondering why I'm not hitting you harder on this, I want to be very explicit, I can ask you a whole bunch of questions that I already know the answer to, and that answer is that you can't comment. That's not constructive or creative. So, I don't want people to think that I'm not intentionally asking the hard questions, but I also know that I'm not going to get an answer and all I'll do is make you uncomfortable. But I think it's fair to ask, how do you evaluate what services or providers or other resources you're using when you're building in cloud that are going to be around, that you can trust building on top of?Richard: It's a fair question. Not everyone's on… let's update our software on a weekly basis and I can just swap things in left. You know, there's a reason that even Red Hat is so popular with Linux because as a government employee, I can use that Linux and know it's backwards compatible for 15 years. And they sell that. Like, that's the value, that this thing works forever.And Microsoft does the same with a lot of their server products. Like, you know, for better or for worse, [laugh] they will always kind of work with a component you wrote 15 years ago in SharePoint and somehow it runs today. I don't even know how that's possible. Love it. That's impressive.Now, there's a cost to that. There's a giant tax in the vendor space to make that work. But yeah, there's certain times where even with us, look, we are trying to get better and better at things like comms. And last year we announced—I checked them recently—you know, we have 185 Cloud products in our enterprise APIs. Meaning they have a very, very tight way we would deprecate with very, very long notice, they've got certain expectations on guarantees of how long you can use them, quality of service, all the SLAs.And so, for me, like, I would bank on, first off, for every cloud provider, whether they're anchor services. Build on those right? You know, S3 is not going anywhere from Amazon. Rock solid service. BigQuery Goodness gracious, it's the center of Google Cloud.And you look at a lot of services: what can you bet on that are the anchors? And then you can take bets on things that sit around it. There's times to be edgy and say, “Hey, I'll use Service Weaver,” which we open-sourced earlier this year. It's kind of a cool framework for building apps and we'll deconstruct it into microservices at deploy time. That's cool.Would I literally build my whole business on it? No, I don't think so. It's early stuff. Now, would I maybe use it also with some really boring VMs and boring API Gateway and boring storage? Totally. Those are going to be around forever.I think for me, personally, I try to think of how do I isolate things that have some variability to them. Now, to your point, sometimes you don't know there's variability. You would have just thought that service might be around forever. So, how are you supposed to know that that thing could go away at some point? And that's totally fair. I get that.Which is why we have to keep being better at comms, making sure more things are in our enterprise APIs, which is almost everything. So, you have some assurances, when I build this thing, I've got a multi-year runway if anything ever changes. Nothing's going to stay the same forever, but nothing should change tomorrow on a dime. We need more trust than that.Corey: Absolutely. And I agree. And the problem, too, is hidden dependencies. Let's say what is something very simple. I want to log in to [unintelligible 00:25:34] brand new AWS account and spin of a single EC2 instance. The end. Well, I can trust that EC2 is going to be there. Great. That's not one service you need to go through that critical path. It is a bare minimum six, possibly as many as twelve, depending upon what it is exactly you're doing.And it's the, you find out after the fact that oh, there was that hidden dependency in there that I wasn't fully aware of. That is a tricky and delicate balance to strike. And, again, no one is going to ever congratulate you—at all—on the decision to maintain a service that is internally painful and engineering-ly expensive to keep going, but as soon as you kill something, even it's for this thing doesn't have any customers, the narrative becomes, “They're screwing over their customers.” It's—they just said that it didn't have any. What's the concern here?It's a messaging problem; it is a reputation problem. Conversely, everyone knows that Amazon does not kill AWS services. Full stop. Yeah, that turns out everyone's wrong. By my count, they've killed ten, full-on AWS services and counting at the moment. But that is not the reputation that they have.Conversely, I think that the reputation that Google is going to kill everything that it touches is probably not accurate, though I don't know that I'd want to have them over to babysit either. So, I don't know. But it is something that it feels like you're swimming uphill on in many respects, just due to not even deprecation decisions, historically, so much as poor communication around them.Richard: Mm-hm. I mean, communication can always get better, you know. And that's, it's not our customers' problem to make sure that they can track every weird thing we feel like doing. It's not their challenge. If our business model changes or our strategy changes, that's not technically the customer's problem. So, it's always our job to make this as easy as possible. Anytime we don't, we have made a mistake.So, you know, even DevRel, hey, look, it puts teams in a tough spot. We want our customers to trust us. We have to earn that; you will never just give it to us. At the same time, as you say, “Hey, we're profitable. It's great. We're growing like weeds,” it's amazing to see how many people are using this platform. I mean, even services, you don't talk about having—I mean, doing really, really well. But I got to earn that. And you got to earn, more importantly, the scale. I don't want you to just kick the tires on Google Cloud; I want you to bet on it. But we're only going to earn that with really good support, really good price, stability, really good feeling like these services are rock solid. Have we totally earned that? We're getting there, but not as mature as we'd like to get yet, but I like where we're going.Corey: I agree. And reputations are tricky. I mean, recently InfluxDB deprecated two regions and wound up turning them off and deleting data. And they wound up getting massive blowback for this, which, to their credit, their co-founder and CTO, Paul Dix—who has been on the show before—wound up talking about and saying, “Yeah, that was us. We're taking ownership of this.”But the public announcement said that they had—that data in AWS was not recoverable and they're reaching out to see if the data in GCP was still available. At which point, I took the wrong impression from this. Like, whoa, whoa, whoa. Hang on. Hold the phone here. Does that mean that data that I delete from a Google Cloud account isn't really deleted?Because I have a whole bunch of regulators that would like a word if so. And Paul jumped onto that with, “No, no, no, no, no. I want to be clear, we have a backup system internally that we were using that has that set up. And we deleted the backups on the AWS side; we don't believe we did on the Google Cloud side. It's purely us, not a cloud provider problem.” It's like, “Okay, first, sorry for causing a fire drill.” Secondly, “Okay, that's great.” But the reason I jumped in that direction was just because it becomes so easy when a narrative gets out there to believe the worst about companies that you don't even realize you're doing it.Richard: No, I understand. It's reflexive. And I get it. And look, B2B is not B2C, you know? In B2B, it's not, “Build it and they will come.” I think we have the best cloud infrastructure, the best security posture, and the most sophisticated managed services. I believe that I use all the clouds. I think that's true. But it doesn't matter unless you also do the things around it, around support, security, you know, usability, trust, you have to go sell these things and bring them to people. You can't just sit back and say, “It's amazing. Everyone's going to use it.” You've got to earn that. And so, that's something that we're still on the journey of, but our foundation is terrific. We just got to do a better job on some of these intangibles around it.Corey: I agree with you, when you s—I think there's a spirited debate you could have on any of those things you said that you believe that Google Cloud is the best at, with the exception of security, where I think that is unquestionably. I think that is a lot less variable than the others. The others are more or less, “Who has the best cloud infrastructure?” Well, depends on who had what for breakfast today. But the simplicity and the approach you take to security is head and shoulders above the competition.And I want to make sure I give credit where due: it is because of that simplicity and default posturing that customers wind up better for it as a result. Otherwise, you wind up in this hell of, “You must have at least this much security training to responsibly secure your environment.” And that is never going to happen. People read far less than we wish they would. I want to make very clear that Google deserves the credit for that security posture.Richard: Yeah, and the other thing, look, I'll say that, from my observation, where we do something that feels a little special and different is we do think in platforms, we think in both how we build and how we operate and how the console is built by a platform team, you—singularly. How—[is 00:30:51] we're doing Duet AI that we've pre-announced at I/O and are shipping. That is a full platform experience covering a dozen services. That is really hard to do if you have a lot of isolation. So, we've done a really cool job thinking in platforms and giving that simplicity at that platform level. Hard to do, but again, we have to bring people to it. You're not going to discover it by accident.Corey: Richard, I will let you get back to your tear-filled late-night writing of tomorrow's Next keynote, but if people want to learn more—once the dust settles—where's the best place for them to find you?Richard: Yeah, hopefully, they continue to hang out at cloud.google.com and using all the free stuff, which is great. You can always find me at seroter.com. I read a bunch every day and then I've read a blog post every day about what I read, so if you ever want to tune in on that, just see what wacky things I'm checking out in tech, that is good. And I still hang out on different social networks, Twitter at @rseroter and LinkedIn and things like that. But yeah, join in and yell at me about anything I said.Corey: I did not realize you had a daily reading list of what you put up there. That is news to me and I will definitely track in, and then of course, yell at you from the cheap seats when I disagree with anything that you've chosen to include. Thank you so much for taking the time to speak with me and suffer the uncomfortable questions.Richard: Hey, I love it. If people aren't talking about us, then we don't matter, so I would much rather we'd be yelling about us than the opposite there.Corey: [laugh]. As always, it's been a pleasure. Richard Seroter, Director of Product Management and Developer Relations at Google Cloud. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment that you had an AI system write for you because you never learned how to structure a sentence.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Paul Dix is Cofounder & CTO of open source time series data company InfluxData. The company's open source datastore, InfluxDB, has 26K stars on GitHub. InfluxData has raised over $200M from investors including Norwest, Battery, and Sapphire Ventures. In this episode, we dig into building the category of time series data, how an open source company's monetization plan should tie to fundraising, some of the hardest decisions the team had to make during InfluxData's journey so far & more!

Welcome to my summer 2023 replay series! This summer, I'm re-releasing some of my favourite ever podcast episodes that I think are well worth a re-listen.In this episode, I had a fascinating chat with Elizabeth Swan (@Elizabeth_swan_uk on Instagram or https://elizabethswan.co.uk) about teaching MFL to people with ADHD and autism.Elizabeth Swan is a teacher, coach and consultant, who draws upon lived experience and professional expertise from over 20 years as a qualified teacher, SENDCo, and headteacher in secondary and special schools as well as postgraduate study of psychology. Lizzy's work is rooted in research-informed approaches to raising awareness and understanding of neurodiversity, with a particular focus on girls and women with ADHD.We covered a range of topics, from the advantages of keeping students with SEND in MFL lessons, to her top tips for making the classroom ADHD/autism-friendly. We also chatted about using rewards and sanctions with ADHD/autistic learners, and the importance of keeping parents/carers fully in the loop.As always, I'd love to know your thoughts on this episode, so do get in touch on my socials (@katelanguages on Instagram and Facebook) or through my website katelanguages.co.ukDuring the episode, Elizabeth mentioned Paul Dix, who is best know for his books including 'When the adults change, everything changes', research on the benefits of bilingualism for autistic people (https://www.frontiersin.org/articles/10.3389/fpsyg.2021.741182/full) and Tuff bags (of which there are many different varieties available online!).Music is from Pixabay by Coma-Media

In this episode we welcome special guest, Lyndsie Perkins, the Interim School Principal at Hartland Elementary School. Lyndsie has been reading audiobooks on her commute to school and her book is When the Adults Change Everything Changes: Seismic Shifts in School Behavior by Paul Dix (2017).  Liz shared a Hartland Library Book Discussion pick, and her new favorite, The Snow Child by Eowyn Ivey (2012). And Traci talked about the joys of expanding your reading comfort zone to include new genres. Traci's book is A Rip Through Time by Kelley Armstrong (2022), a time-traveling, historical fiction pageturner.

An unregulated adult cannot support an unregulated student. We know it's true, and it's up to us as principals to support our teachers and staff when student behavior is hard. Check out this week's pod all about supporting the adults in the school who are supporting our students through crisis.  Referenced:   When the Adults Change, Everything Changes by Paul Dix

We cover how to sustain long-term transformational projects with Paul Dix, CTO & Founder @ InfluxData! This high-energy conversation reveals the history behind InfluxDB and its multi-phase, long-term transformation over the past 10 years. Plus we discuss how to know when it's time to take your company to the next level, identifying the right people for your eng teams, integrating multiple teams into an org re-architecture, and building open-source products/communities!ABOUT PAUL DIXPaul (@PaulDix) is the creator of InfluxDB. He has helped build software for startups, large companies, and organizations like Microsoft, Google, McAfee, Thomson Reuters, and Air Force Space Command. He is the series editor for Addison Wesley's Data & Analytics book and video series. In 2010 Paul wrote the book Service Oriented Design with Ruby and Rails. In 2009 he started the NYC Machine Learning Meetup. Paul holds a degree in computer science from Columbia University."What I need is a small team of focused people who are on board, who can be focused on getting this done and we'll prove it out as we go.And I think the mistake I made with the 2.0 cloud product was we got way too many of people involved way too quickly, right? I think for the initial phases of project, it's actually advantageous to have a smaller team.- Paul Dix   Interested in joining an ELC Peer Group?ELCs Peer Groups provide a virtual, curated, and ongoing peer learning opportunity to help you navigate the unknown, uncover solutions and accelerate your learning with a small group of trusted peers.Apply to join a peer group HERE: sfelc.com/peerGroupsSHOW NOTES:The history behind InfluxDB & its multi-phase, long-term transformation (1:53)InfluxDB's first transformational phase featuring time series data (5:48)Phase 2.0 & shifting to a cloud-first delivery model (7:50)Challenges & opportunities faced in the current phase of InfluxDB (9:31)How Paul decided it was time to take the company to the next level (11:38)Making a bet on Rust (14:25)Why making an early announcement helped push Phase 3.0 forward (16:02)Strategies for identifying the right people for your eng team (19:06)How to optimize community insights when tailoring your vision (21:56)Tips for resolving disagreements between eng team members (24:45)Frameworks for executing long-term vision & achieving alignment (26:21)Processes for integrating other teams into an org's re-architecture (29:55)The impact of Conway's Law on team structure & open-source software (32:07)Considerations for managing large, open-source projects (36:40)Rapid fire questions (37:56)LINKS AND RESOURCES“The Happiness Hypothesis” by Jonathan Haidt - Each chapter is an attempt to savor one idea that has been discovered by several of the world's civilizations -­ to question it in light of what we now know from scientific research, and to extract from it the lessons that still apply to our modern lives.“The Fate of Rome” by Kyle Harper - How devastating viruses, pandemics, and other natural catastrophes swept through the far-flung Roman Empire and helped to bring down one of the mightiest civilizations of the ancient world

In this episode, I had a fascinating chat with Elizabeth Swan (@Elizabeth_swan_uk on Instagram or https://elizabethswan.co.uk) about teaching MFL to people with ADHD and autism. Elizabeth Swan is a teacher, coach and consultant, who draws upon lived experience and professional expertise from over 20 years as a qualified teacher, SENDCo, and headteacher in secondary and special schools as well as postgraduate study of psychology. Lizzy's work is rooted in research-informed approaches to raising awareness and understanding of neurodiversity, with a particular focus on girls and women with ADHD.We covered a range of topics, from the advantages of keeping students with SEND in MFL lessons, to her top tips for making the classroom ADHD/autism-friendly. We also chatted about using rewards and sanctions with ADHD/autistic learners, and the importance of keeping parents/carers fully in the loop. As always, I'd love to know your thoughts on this episode, so do get in touch on my socials (@katelanguages on Instagram, Facebook and Twitter) or through my website katelanguages.co.ukDuring the episode, Elizabeth mentioned Paul Dix, who is best know for his books including 'When the adults change, everything changes', research on the benefits of bilingualism for autistic people (https://www.frontiersin.org/articles/10.3389/fpsyg.2021.741182/full) and Tuff bags (of which there are many different varieties available online!).

How fast can data be collected and used in current business models? Evan Kaplan, CEO of Influxdata, claims that in the era of smart products, an autonomous system can utilize data collected every millisecond for instant responses. Listen in to learn more about how collecting instant data can provide better service for products and create loyalty with customers.Tune in to learn:What Influxdata does (01:12)  Monitoring data to build real-time responses (08:17)How quickly data is being recorded (13:40)Types of projects built with Influxdata (16:28)Influxdata's popularity with student engineers (20:17)Mentions:Check out our previous episode with Paul Dix also from Influx Data.“Memorial Day Murph” Crossfit RoutineIT Visionaries is powered by Salesforce Platform and Dreamforce 2022. Catch the news and insights coming out of Dreamforce this year for free on salesforce.com/plus. Content will start rolling on September 20th.Mission.org is a media studio producing content for world-class clients. Learn more at mission.org.

Listen to HashiCast: https://www.listennotes.com/podcasts/hashicast/episode-5-paul-dix-influxdb-PGC9o3DmNyc/ (12 mins in)Benefits of TS DBs: Compression for timestamps Write throughput because append-only writes Downsampling high precision for 7 days, then 10min summarizations for 3 months, then 1hr summaries Query patterns - Instead of SQL, Influx uses InfluxQL More on the TICK stack: https://docs.influxdata.com/

Paul Dix is the co-founder and CTO of Influx Data. Paul is an industry veteran and a man of many accomplishments. Having created the company in 2013, it has amassed thousands of customers and is now 200 employees strong. Given his experience as a CTO and understanding of programming, we asked what advice he had for non-technical people. Many people see learning to code as an impossible task, especially if you're not a technical person. But as Paul Dix points out, anyone can do it! It all depends how motivated you are by the frustration. In other words, just starting is half the battle. It can be overwhelming given how much information there is out there and how can all look and sound the same to begin with. Here are some clear goals you can aim for when first trying languages out! Homeroom is hosted by Cassius Felicella. Connect with Influx Data Website: https://www.influxdata.com/ GitHub: https://github.com/influxdata/influxdb Crunchbase: https://www.crunchbase.com/organization/canix Twitter: https://twitter.com/influxdb LinkedIn: https://www.linkedin.com/company/influxdb/ Slack: https://influxcommunity.slack.com/ We talk to founders and entrepreneurs! We're in the business of learning and want to look at everything startup related. Our hope is to show just how significant this segment of business is to the world, and the things it can accomplish. For all inquiries, please email homeroomtalks@gmail.com.

If the topic of databases is brought up to certain people, their eyes may gloss over. But if that happened, that would be because they just don't know the awesome power of databases. Data can be valuable but only if it is contextualized, and time is an extremely relevant aspect to consider when analyzing huge amounts of data. Paul Dix, the founder and CTO of InfluxData and the Creator of InfluxDB, explains how a time series database can help provide that temporal contextual information to promote efficiencies.Main TakeawaysTime Contextualizes Data: Data has value only when it is placed in context and then the information gleaned from it is applied into actionable items. Time is a key factor to provide a basis for understanding information. A time series database, iike InfluxDB, can provide this sort of context for server and IoT device monitoring. This info can then be applied to track performance and increase efficiency.Failure Becomes Opportunity: Sometimes it's hard to see how a win can come from a loss, and most people try their very best to avoid losing. But the reality is that learning is happening when something is being created, and the knowledge that's gained in the creative process has nothing to do with the outcome of a given project. To ultimately be successful, the lesson is to take what's been learned and then keep pivoting until the product and the market are aligned and the timing is right.Evolving Engineering: Technology is always advancing rapidly. Therefore, even a successful product will require adaptations to meet new challenges. Accepting the reality of the high rate of change and, therefore, the need to constantly adjust accordingly will position a company in the best position to succeed.IT Visionaries is brought to you by the Salesforce Platform - the #1 cloud platform for digital transformation of every experience. Build connected experiences, empower every employee, and deliver continuous innovation - with the customer at the center of everything you do. Learn more at salesforce.com/platform

Today Adam is joined by Evan Kaplan, CEO of InfluxData. Evan's journey to become the CEO was not by way of founder, in this company. Evan has founded several companies in the past, and he's been in a CEO position for more than 22 years. But InfluxData was founded by Paul Dix, and Paul knew years ago that his role (best role?) was to lead the technical and product direction of the company, which lead him to Evan. Today we share that story as well as a glimpse into operating the business that built the defacto platform for building time series applications with deep roots in open source.

Today Adam is joined by Evan Kaplan, CEO of InfluxData. Evan's journey to become the CEO was not by way of founder, in this company. Evan has founded several companies in the past, and he's been in a CEO position for more than 22 years. But InfluxData was founded by Paul Dix, and Paul knew years ago that his role (best role?) was to lead the technical and product direction of the company, which lead him to Evan. Today we share that story as well as a glimpse into operating the business that built the defacto platform for building time series applications with deep roots in open source.

While the overall concept of timeseries data is uniform, its usage and applications are far from it. One of the most demanding applications of timeseries data is for application and server monitoring due to the problem of high cardinality. In his quest to build a generalized platform for managing timeseries Paul Dix keeps getting pulled back into the monitoring arena. In this episode he shares the history of the InfluxDB project, the business that he has helped to build around it, and the architectural aspects of the engine that allow for its flexibility in managing various forms of timeseries data. This is a fascinating exploration of the technical and organizational evolution of the Influx Data platform, with some promising glimpses of where they are headed in the near future.

One of the most intractable problems in modern education is how to close the widening gap in attainment between the haves and the have-nots. Unfortunately, successive governments both in the UK and abroad have gone about solving it the wrong way. Independent Thinking founder Ian Gilbert's increasing frustration with educational policies that favour no excuses and compliance , and that ignore the broader issues of poverty and inequality, is shared by many others across the sphere of education and this widespread disaffection has led to the assembly of a diverse cast of teachers, school leaders, academics and poets who unite in this book to challenge the status quo. Their thought-provoking commentary, ideas and impassioned anecdotal insights are presented in the form of essays, think pieces and poems that draw together a wealth of research on the issue and probe and discredit the current view on what is best for children from poorer socio-economic backgrounds. Exploring themes such as inclusion, aspiration, pedagogy and opportunity, the contributions collectively lift the veil of feigned equality of opportunity for all to reveal the bigger picture of poverty and to articulate the hidden truth that there is always another way. This book is not about giving you all the answers, however. The contributors are not telling teachers or school leaders how to run their schools, their classroom or their relationships the field is too massive, too complex, too open to debate and to discussion to propose off-the-shelf solutions. Furthermore, the research referred to in this book is not presented in order to tell educators what to think, but rather to inform their own thinking and to challenge some of the dominant narratives about educating the feckless poor. This book is about helping educators to ask the right questions, and its starting question is quite simple: how can we approach the education of young people from disadvantaged backgrounds in a way that actually makes a difference for all concerned? Written for policy makers and activists as well as school leaders and educators, 'The Working Class' is both a timely survey of the impact of current policies and an invaluable source of practical advice on what can be done to better support disadvantaged children in the school system. Edited by Ian Gilbert with contributions from Nina Jackson, Tim Taylor, Dr Steven Watson, Rhythmical Mike, Dr Ceri Brown, Dr Brian Male, Julia Hancock, Paul Dix, Chris Kilkenny, Daryn Egan-Simon, Paul Bateson, Sarah Pavey, Dr Matthew McFall, Jamie Thrasivoulou, Hywel Roberts, Dr Kevin Ming, Leah Stewart, (Real) David Cameron, Sir Al Aynsley-Green, Shona Crichton, Floyd Woodrow, Jonathan Lear, Dr Debra Kidd, Will Ryan, Andrew Morrish, Phil Beadle, Jaz Ampaw-Farr, Darren Chetty, Sameena Choudry, Tait Coles, Professor Terry Wrigley, Brian Walton, Dave Whitaker, Gill Kelly, Roy Leighton, Jane Hewitt, Jarlath O Brien, Crista Hazell, Louise Riley, Mark Creasy, Martin Illingworth, Ian Loynd, David Rogers, Professor Mick Waters and Professor Paul Clarke. Here is the Spotify link I mentioned. Some crackers on there. This is the ITPress link to the book if it helps. This resource might be useful too from the ITL site.

Catch up on our Sunday morning sermon, this week delivered by Paul Dix. Reading: Ephesians 6: 10-24

In our Summer Series, we're sharing some highlights from our 2020 podcasts, including this one on Behaviour Management. This podcast is for every practitioner, and the principals who lead our schools. This week we discuss behaviour management with one on the UK's leading experts. CSA's Dave Stevens of WA, interviews Paul Dix the once difficult child, relentless teacher and now award-winning behaviour trainer. Paul has been working with the most difficult behaviours in the most challenging urban schools and colleges for the last 25 years. He founded Pivotal Education and The TBAP Trust transforming behaviour, teaching and learning in schools and colleges in the UK and internationally. His voice has echoed through many classrooms. But, if you think this podcast is for a school other than yours, you've missed the point. A leading thinker in behaviour management and behaviour change, his inspirational perspectives and fascinating narratives reveal a ferocious passion for education. Join them both as they explore tips and strategies to encourage teacher-student relationships in the classroom. From the “at risk” to the “attention rousing” – Paul explores how minor adjustments in our craft produce monumental shifts in our cultures.

This week on The Changelog we’re talking about the recent falling out between Elastic and AWS around the relicensing of Elasticsearch and Kibana. Like many in the community, we have been watching this very closely. Here’s the tldr for context. On January 21st, Elastic posted a blog post sharing their concerns with Amazon/AWS misleading and confusing the community, saying “They have been doing things that we think are just NOT OK since 2015 and it has only gotten worse.” This lead them to relicense Elasticsearch and Kibana with a dual license, a proprietary license and the Sever Side Public License (SSPL). AWS responded two days later stating that they are “stepping up for a truly open source Elasticsearch,” and shared their plans to create and maintain forks of Elasticsearch and Kibana based on the latest ALv2-licensed codebases. There’s a ton of detail and nuance beneath the surface, so we invited a handful of folks on the show to share their perspective. On today’s show you’ll hear from: Adam Jacob (co-founder and board member of Chef), Heather Meeker (open-source lawyer and the author of the SSPL license), Manish Jain (founder and CTO at Dgraph Labs), Paul Dix (co-founder and CTO at InfluxDB), VM (Vicky) Brasseur (open source & free software business strategist), and Markus Stenqvist (everyday web dev from Sweden).

This week on The Changelog we’re talking about the recent falling out between Elastic and AWS around the relicensing of Elasticsearch and Kibana. Like many in the community, we have been watching this very closely. Here’s the tldr for context. On January 21st, Elastic posted a blog post sharing their concerns with Amazon/AWS misleading and confusing the community, saying “They have been doing things that we think are just NOT OK since 2015 and it has only gotten worse.” This lead them to relicense Elasticsearch and Kibana with a dual license, a proprietary license and the Sever Side Public License (SSPL). AWS responded two days later stating that they are “stepping up for a truly open source Elasticsearch,” and shared their plans to create and maintain forks of Elasticsearch and Kibana based on the latest ALv2-licensed codebases. There’s a ton of detail and nuance beneath the surface, so we invited a handful of folks on the show to share their perspective. On today’s show you’ll hear from: Adam Jacob (co-founder and board member of Chef), Heather Meeker (open-source lawyer and the author of the SSPL license), Manish Jain (founder and CTO at Dgraph Labs), Paul Dix (co-founder and CTO at InfluxDB), VM (Vicky) Brasseur (open source & free software business strategist), and Markus Stenqvist (everyday web dev from Sweden).

We are delighted to be joined today by Paul Dix. Paul is an Award-winning Behaviour Specialist who has helped schools all over the world transform their behaviour policies. He is author of the book “When the adults change, everything changes” and leads the very popular Ban the booths campaign. Paul starts a new venture this coming weekend when his new radio station for teachers, Teacher Hug Radio, launches at TeacherHugRadio.co.uk. www.teacherhugradio.co.uk --- Send in a voice message: https://anchor.fm/edufuturistspodcast/message

Have a listen. Please share and comment, give me a review if you know how (I don’t

In this episode, Paul Dix talks about the origins of InfluxDB, how they've built it into a massive project and where they are heading next. Paul shares great insights on how they found early product-market fit, decided to build a database as a product and why they saw a unique opportunity for their technology with the open source community. Technologies discussed: Redis, MongoDB, Rust, Influx Database, Flagsmith, DataDog, Apache, Database, JavaScript, API, Open Source, SQL, MySQL

A podcast about factors that influence behaviour in education, all in handy 15 minute (ish) bite sized chunks. Each week a different guest chats about a different aspect of behaviour and leaves you with three handy tips on behaviour. This Podcast is brought to you by Changing Behaviour UK LTD changing-behaviour.co.uk/ who you can follow on Twitter @change_beh If you enjoy an episode don't forget to subscribe to the podcast to receive updates on new episodes. This week Clare Edmondson (founder of Changing Behaviour UK LTD, SEMH/SEN specialist, leader and teacher) Chats to Jack Taylor about behaviour and consistency. About Jack Taylor in his words: " I am an Assistant Principal in a West London school. For the past 3 years my role was focused on behaviour, systems and structures, but this year I have moved to Raising Standards Leader. I am a Drama specialist and also play a role within the Safeguarding Team." Jack is currently reading: Leaders Eat Last by Simon Sinek but next on my list is ‘When the Adults Change, Everything Changes' by Paul Dix, as I have heard it is very good! Jack's top tips on consistency: 1. Be consistent at all times. If you say you're going to phone home, phone home. 2. If you have a bad lesson or day with a particular class or student, you must let it go and treat the next time you see them as a fresh start. 3. Follow the policies. They are created for us, so our job is to make sure we all use them. If we don't, we only make ours and others lives more difficult.

This podcast is for every practitioner, and the principals who lead our schools. This week we discuss behaviour management with one on the UK's leading experts. CSA's Dave Stevens of WA, interviews Paul Dix the once difficult child, relentless teacher and now award-winning behaviour trainer. Paul has been working with the most difficult behaviours in the most challenging urban schools and colleges for the last 25 years. He founded Pivotal Education and The TBAP Trust transforming behaviour, teaching and learning in schools and colleges in the UK and internationally. His voice has echoed through many classrooms. But, if you think this podcast is for a school other than yours, you've missed the point. A leading thinker in behaviour management and behaviour change, his inspirational perspectives and fascinating narratives reveal a ferocious passion for education. Join them both as they explore tips and strategies to encourage teacher-student relationships in the classroom. From the “at risk” to the “attention rousing” – Paul explores how minor adjustments in our craft produce monumental shifts in our cultures.

Welcome to this weeks Naylor’s Natter . This week is a special episode that I have been sitting on for some time. As you will all know , I was due to help host with my colleague Mr Simon Cox the behemoth that is rED Blackpool. At this conference , I was due to speak about behaviour , not because I am some kind of expert but because I am a student of behaviour . I would like to think that after years of honing my own behaviour management that I am stronger in this area than at any stage of my career. I attribute this to learning from and listening to many of the big voices in behaviour over 20 years . I started by learning from Lee Canter’s assertive discipline and this was a book I re-read each and every August before returning to school. I also discovered the behavior guru Bill Rogers and read many of Bill’s books and devoured his videos. The talk I referred to earlier was entitled ‘Behaviour- Ideology, evidence and pragmatism’ . Behaviour more than any other issue in school is highly controversial and teachers and leaders have many and varied styles and rationales for the behaviour policy they adopt . Teachers and leaders seem to have a strong position on their preferred behaviour approach and some seem to favour a particular camp or approach . This is very much teacher’s own choice and I fully understand that teachers are attached to their own particular style or strategy . The strap line for this podcast is talking to teacher and this is very much a philosophy that we at Naylor’s natter want to promote. On the podcast we have spoken to Sam Strickland, Tom Bennett , Kiran Gill , Jules Daulby and many other on their philosophy of behaviour . What hopefully listeners will find is that whatever your preferred style , there is something to be gained from listening to everyone in the debate on behaviour . This week’s guest is Paul Dix. Paul has written the hugely successful ‘When the adults change, everything changes’ and is an experienced teacher and a leading voice in education . What struck me in our pre-lockdown February half-term conversation is how much great advice for teachers there is within this book and how practical its application can be . Paul speaks humbly about his own practice in the classroom , his rationale for writing the book to help teachers like himself and how reading this book many change your view of how you approach behaviour but also of his approach . Lot’s of the debate on social media is quite binary , this approach is good that one isn’t . This behaviour expert is right , this one is wrong and the levels of praise or vitriol can be off putting particularly with new teachers. This is a podcast to approach with an open mind , there will be something for you here whatever your current view on behaviour . You will hopefully see as I did , the common themes coming through from all the podcasts we have done on behaviour . I found Paul utterly charming and giving of his time and whilst I wont adopt everything we discussed , he really made me think about how to refine my own practice and that of the school . Thank you Paul We have our regular TDT section which this week is anything but regular as we have leadership legend and friend of the show Jill Berry back to talk about leadership. In podcast pedagogy this week I am reading the researched guide to the curriculum – an evidence informed guide for teachers edited by Claire Sealey who I will be speaking to soon about this new John Catt book . I am also revisiting retrieval practice – research and resources for every classroom from the wonderful Kate Jones . --- Send in a voice message: https://anchor.fm/naylorsnatter/message

Relational database management systems have been the mainstay of IT departments since they were first commercially introduced by Oracle in the 1970s. But over the past decade, a new generation of database categories have taken over as the top choice for enterprise IT projects. In the past few years, developers have started to reach a consensus about which of these “specialty database categories” can best handle specific use cases where relational databases haven’t kept up. According to DB-Engines, the database management categories with the fastest user growth in the past two years are Time Series databases, Graph databases, and Key-Value stores. During that time, relational database usage has stayed the same or declined slightly. Organizations now track, measure and analyze metrics from a wide range of sources that provide new data every second. According to IDC, the amount of data being produced worldwide is expected to grow nearly fivefold by 2025 to 175 zettabytes per year, driven by the proliferation of IoT sensors, serverless infrastructure, containerization and microservices. Most of this is time-stamped data generated at high frequency and in great volume that requires rapid ingestion and real-time querying to extract maximum value. This means that the future of tech innovation will require real-time system observability, with granular insights to make more precise decisions to optimize operations and improve customer experience. Paul Dix, creator of InfluxDB (open-source time-series database) and the founder and CTO of InfluxData joins me on Tech Talks Daily. With over two decades of experience helping companies like Microsoft, Google, McAfee, Thomson Reuters, and Air Force Space Command build software, Paul has unique insights to share on how and why time-series data is going to be the biggest hurdle and opportunity for tech organization in the future.  

Paul is an ex teacher and behavioural specialist. He's a speaker, an author and a ‘teacher wrangler' and trouble-shooter. He has had 25 years' experience dealing with challenging behaviour in the classroom in schools dealing with lots of different sort of problems. Paul is the founder of Pivotal Education and author of When the Adults Change Everything Changes. Paul struggled in education himself and draws on his own experience as a student and teacher to help teachers understand the child's perspective. Listen to this episode with Paul Dix if you want to learn: Why punishment in the classroom (and at home) doesn't work. (See our positive discipline class) How kids can read a teacher and know exactly when he's lost it and use it to provoke him (enjoy the Fruit of the Loom story) How easy it is for adults to reach for punishment when their own emotions are aroused How important it is to remove adult emotion so that the child can see the rational straight line between their behaviour and consequences. Emotional adults will never correct inappropriate behaviour About the different cultures in different schools surrounding the use of sanctions More positive ways of responding to frustrating disruptive behaviours in the classroom How key the relationship between parents and teachers is and why it's better to go to the teacher with a problem than over their head to a higher authority. Paul warns against the Sunday night email to the school! Why exclusion booths (where the child is subject to both physical and psychological control and isolation) are an appalling response (by a minority of schools) to relatively minor misbehaviours About positive strategies like greeting children at the beginning of the day, recognition boards, hot chocolate Fridays, 2 minute discos at the end of the day, fantastic walking. Having very consistent routines and acknowledging the good behaviour and structured consistent responses by all teachers to poor behaviour. How to have ‘restorative conversations' when things have gone wrong. (This is akin to the Mistakes Process we teach at TPP)   Paul talks a lot about the need for parents to keep calm and keep the emotion out of it when disciplining them. He concedes this is easier said than done. If you haven't already listened to our interview with Bonnie Harris do so to get lots of ideas about how to restore calm when your buttons have been pushed. We also have a workshop entitled How to be a Calmer Parent. In our celebration of vulnerability and perfect imperfection Paul shares with us a very funny Low Parenting Moment of his own that many of us can identify with. And his top tip for raising children to be confident, happy and successful.    Links: to get in touch with Paul go to www.whentheadultschange.com

La bio au bifidus actif de Jean-Paul Dix : Sean Connery du 16 décembre 2019. Émission de pop culture en direct les lundis de 19h à 20h30. www.pantoufles-explosives.com

In this, The New Stack Makers podcast episode, Paul Dix, co-founder and CTO of InfluxData, discusses what is in store for 2020 for databases, both on an industry scale and how InfluxData's development teams hope to rise to today's challenges. Distributed tracing, serverless “pay as you go” business models, InfluxData's Flux programming languages for databases and the outlook for stateful database applications in Kubernetes were also under discussion as Dix spoke freely and candidly about the different topics.

La bio au bifidus actif de Jean-Paul Dix : Buzz l'éclair du 9 décembre 2019. Émission de pop culture en direct les lundis de 19h à 20h30. www.pantoufles-explosives.com

Our reading today: Psalm 6

Paul Dix is the cofounder and CTO at InfluxDB, makers of an open source time-series database. Over the last 20-plus years, he’s held technology, consultant, and leadership positions at companies like Microsoft, McAfee, Google, and Thomson Reuters. Join Corey and Paul as they discuss everything there is to discuss about time-series databases, the two different kinds of time-series events, the importance of timing when launching a product, how to build applications on top of time-series data, creating a new programming language (Flux), why you should create new programming languages when it makes sense, and more.

Once largely reserved for the finance industry, times series databases are increasingly emerging as must-haves for many organizations. A classic SQL database,  for example, is not designed to process thousands or — in many cases — millions of data points per second that a time series database can monitor, track,  analyze and assimilate for forecasting applications for real-time analytics and business intelligence. These applications often include application, server, network  monitoring, for industrial or IoT data. However, many organizations are faced with the conundrum of not being able to afford investing in the required hardware infrastructure for time series data analysis or most of their operations are cloud-based and they have faced a dearth of viable alternatives. As a solution, InfluxData, a leading data has launched InfluxDB Cloud 2.0, the first serverless time series platform as a service (PaaS). In this The New Stack Makers podcast, Paul Dix, co-founder and CTO, InfluxData, discussed InfluxDB Cloud 2.0, and how the evolution of time series databases have evolved to create a need for a cloud-based alternative.

Paul Dix is the Founder and CTO of InfluxData, creator of the popular open source time series database, InfluxDB. In this episode, Paul discusses finding balance between commercial and open source offerings. Transcript Intro Michael Schwartz: Welcome back! You’re listening to Open Source Underdogs. I’m your host, Mike Schwartz, and this week, we’re honored to...

Guest: Paul Dix @pauldix Full show notes are at https://developeronfire.com/podcast/episode-429-paul-dix-solving-for-real-needs

Step Conference 2019 – Paul Dix & David Cameron Q&A Paul Dix (@pauldixtweets) David Cameron @realdcameron STEP (@STeachersEP) STEP 2019 Conference | STEP

This month’s conversations with General Secretary Geoff Barton include: 1. Emma Knights, CEO, National Governance Association: on good governance via governors and trustees, and the role of headteachers as governors 2. Carol Jones, Chair, the Leading Women’s Alliance: on the mission to bring more women into headship and available support for them 3. Paul Dix, Executive Director, Pivotal Education: on simplifying behaviour rules, retaining humanity, and building consistency across staff 4. Charly Young, CEO, and Aiseosa Eweka-Okera, Young Ambassador, The Girls Network: on the role of the Girls Networking in raising the aspirations of young females by providing role-models and mentors 5. Sian Hampton, CEO, and Lee Miveld, Head of Alternative Provision, Archway Learning Trust, Nottinghamshire: on stepping from headship to executive leadership, what a commitment to 100% inclusion means in practice, and giving support to all young people against chaotic, often violent backgrounds 6. Malcolm Trobe, ASCL NPQEL Programme Director and Consultant: on early lessons from the NPQEL about the opportunities and challenges of executive leadership

This week on The New Stack Context, our weekly news wrapup podcast, we spoke Paul Dix, founder and chief technology officer of InfluxData, about why time series databases are needed now. The New Stack sponsor InfluxData launched InfluxDB, an open source time series platform, in 2013. Since then, the software has had millions of downloads, built an expanding list of enterprise customers, and fostered a growing community. InfluxData CMO Mark Herring writes on The New Stack this week that most data is best understood in a time dimension, so the time series space is really just getting started. Paul spoke with us about why this is the case, and also shared some info about the company's new query language for time series data, called Flux, as well. In the second half of the show, we'll review our top stories for the week and discuss Exoscale's Container Stack, a conference all about doing DevOps with Kubernetes which will be held in Zurich on Jan. 30-31.

Paul Dix, founder and principal of Pivotal Education, discusses his approach to and tremendous success implementing restorative behavior management strategies in schools.

Genesis 37: 1-11 Joel 2: 25-30a

In this episode of HashiCast we talk to Paul Dix from InfluxDB. Paul Dix is cofounder and CTO of InfluxData, the company behind InfluxDB, the open source time series database. He has helped build software for startups, large companies and organizations like Microsoft, Google, McAfee, Thomson Reuters, and Air Force Space Command. He is the series editor for Addison Wesley's Data & Analytics book and video series. In 2010 Paul wrote the book Service Oriented Design with Ruby and Rails for Addison Wesley's Professional Ruby series. In 2009 he started the NYC Machine Learning Meetup, which has over 9,000 members. Paul holds a degree in computer science from Columbia University. Join us as we talk all things timeseries, metrics and monitoring. Links: https://www.influxdata.com

Paul Dix joined the show and talked with us about InfluxDB, building a company with OSS, improving the language, and other interesting projects and news.

Paul Dix joined the show and talked with us about InfluxDB, building a company with OSS, improving the language, and other interesting projects and news.

Paul Dix joined the show and talked with us about InfluxDB, building a company with OSS, improving the language, and other interesting projects and news.

Episode 180! Ollie welcomes Pivotal Principal Trainer, Paul Woodward onto the show this week. Paul Dix interviewed Paul shortly after he joined Pivotal Education and we have included some of that conversation this week. More recently, Ollie had the pleasure of interviewing Paul again to find out a lot more about his educational beliefs and … Continue reading Paul Woodward – Stories from around the world – PP180 →

In this podcast, Paul Dix, Chief Technology Officer and Founder of InfluxData draws upon his experience of the last 4 years building a viable business around InfluxDB and its related projects. He explores the pros and cons of various models, as well as the existential threat of the major cloud vendors. The open source dream … Continue reading InfluxData – The open source business model is under siege!

To kick off the GrafanaCon user conference, taking place in New York this week, The New Stack held a special pancake and podcast panel discussion, to mull over these very topics. For the event, the panel was comprised of Paul Dix, chief technology officer for InfluxData, keeper of the InfluxDB time-series database; Raj Dutt, cofounder and CEO of Raintank, which offers a commercial distribution of the open source Grafana visualization monitoring software; Theodore Staack, a software developer at office supply retailer Staples; and Matthew Brender, Intel developer advocate. Learn more at: https://thenewstack.io/grafanacon-pancake-podcast-intricacies-composing-new-monitoring-stack/

Join TES' very own Sarah Simon as she talks to Steven Keevil from Mid Kent College about whether it is important to be "down with the kids", Sarah hears how Mike Gaston, principal at Totton College, spent a day as a student in his own college and, finally, she speaks to Paul Dix about what happens when the behaviour management honeymoon is over. See acast.com/privacy for privacy and opt-out information.

Join the TES' very own Sarah Simons as she talks to behaviour expert Paul Dix on how to manage mixed age classes. She speaks to Canadian teacher Kate Nonesuch, who gives advice about giving advice and, finally, hear what Sarah learnt about teaching from standing on the shifting sands of the Sahara Desert. See acast.com/privacy for privacy and opt-out information.

It that time of year when practitioners walk into their classrooms, workshops, studios or salons and look out across a sea of new faces. What are the best strategies to help set the right tone, to get to know the learners and to set some positive routines in action?   In this episode of the TES FE Podcast, Sarah Simons discusses structure, seating plans and smiling with Paul Dix, one of the UK’s most sought after experts in behaviour management. See acast.com/privacy for privacy and opt-out information.

Main Features: Paul Dix from Pivotal Education in the UK talks with Cameron about Behaviour Management in Schools. Corinne speaks with Annabel Astbury about ABC Splash. Regular Features: Education in the News, Cameron and Corinne talk education and politics.

The Rogues chat with Paul Dix about service-oriented design.

The Rogues chat with Paul Dix about service-oriented design.

The Rogues chat with Paul Dix about service-oriented design.

This episode was originally published on May 2, 2007. Paul Dix on natural language processing with Ruby.

This episode was originally published on May 2, 2007. Paul Dix on natural language processing with Ruby.