text
stringlengths
0
2.46k
• Using a sandbox for interactive tutorials, such as an emulation environment
• Accessibility and empowerment through interactive tutorials and demonstrations
• Using a tutorial website, such as niscraft, as an example use case for interactive tutorials
• Adam has a conversation with an unnamed person about using a speed boat to get across a lake, and the conversation then turns to how to make a tool that helps with open source dependency analysis.
• The unnamed person thinks that a tool that helps with open source dependency analysis is a great idea and could be very powerful.
• Adam says that making such a tool would require a collaboration of sorts and that he knows very little about hardware stuff.
• The conversation then turns to a new topic, where Adam is speaking with Ross, the founder and CEO of Socket, about the problem of security concerns when consuming open source dependencies.
• Ross explains that Socket helps solve this problem by fully analyzing dependencies and detecting attacks, malware, and vulnerabilities, and bringing this information to the developer.
• Adam asks about the installation process, and Ross explains that it is easy and can be done through a CLI, GitHub app, or API.
• Ross also mentions that most users install Socket through the GitHub app, which is a fast and simple process.
• M Scott discusses his first name, Matthew, and how his parents never called him by it
• He and the host have a long history, dating back to a conference where the host's wife, Andrea, was a speaker
• M Scott co-owns Corgi Bites, a consultancy that focuses on modernizing and maintaining software systems
• He discusses his passion for fixing bugs and turning old code into new, efficient systems
• M Scott shares a challenging project where he helped a client transition from a cloud infrastructure to a platform as a service solution
• He mentions the current macroeconomic downturn and its impact on his business
• Economic factors affecting small software companies, including reduced VC funding, inflation, and interest rates
• The value of software services and rehab projects being reassessed in the current market
• The impact of low-code and no-code platforms on the software industry, making it easier for companies to build quick solutions
• The potential for organizations to move beyond low-code and no-code platforms and build custom software
• The emerging market for helping organizations extend or move beyond low-code and no-code platforms
• The potential impact of AI on the software industry and its effect on business models
• The need for companies to adapt and change their business models in response to market shifts
• Building solutions to help teams manage software dependencies
• Freshly: a product analyzing dependency freshness and quality
• Evaluating multiple nodes on the dependency graph for meta analysis
• Connection between dependency freshness and security
• Liability index: a metric measuring the distance to a secure version
• Graphing dependency metrics over time to paint a picture for leadership
• Bringing essential maintenance activities to the forefront of team priorities
• Invisible dependencies and package management challenges
• Importance of keeping dependencies up to date to prevent supply chain attacks
• Role of package ecosystems like npm in notifying users of outdated dependencies
• Balance between staying up to date and not over-prioritizing updates
• Risk tolerance and varying levels of security and productivity impact
• Need for regular dependency updates and a cultural shift in software development teams
• Discussing the challenges of presenting technical information to non-technical leaders
• The importance of an authoritative and finite way to measure technical debt or system performance
• Generating a report or dashboard to present technical data to leadership in a consumable format
• Using data to create a "freshness factor" or competition among teams or organizations
• The time-consuming nature of building software, even with AI assistance
• Previewing upcoming episodes of the podcast, including a future episode with Jared and Breakmaster Cylinder
[0.00 --> 19.52] this week on the change law we're going back to the hallway track of all things open 2023
[19.52 --> 25.40] in raleigh north carolina today's episode features high key lena kegas co-founder of neon
[25.40 --> 32.40] and postgres hacker talking about well postgres and of course neon little side note here because
[32.40 --> 37.96] neon is actually one of the sponsors of this podcast we met neon at all things open and we
[37.96 --> 42.38] pursued them we wanted to use their stuff and we asked them hey would you be interested in sponsoring
[42.38 --> 47.58] us and they said yes and it just so happens they're sponsoring this episode this is not intentional
[47.58 --> 53.82] just so you know up second is robert abukalil bioinformatics software engineer who's working
[53.82 --> 61.70] on bringing desktop applications to the web with wasm and last up is m scott ford on the state
[61.70 --> 66.32] of fixing bugs and what's been going on with this software consultancy called corgibites
[66.32 --> 73.32] of course a big thank you to our friends and our partners at fastly and fly this podcast got to you
[73.32 --> 80.18] fast because fastly they are super fast globally check them out at fastly.com and our good friends
[80.18 --> 86.08] at fly will help you put your app and your database in 30 plus regions on six continents with no ops
[86.08 --> 88.52] check them out at fly.io
[88.52 --> 104.50] what's up friends this episode is brought to you by our friends at neon on demand scalability
[104.50 --> 111.62] bottomless storage and database branching and i'm here with nakita shamganov co-founder and ceo of neon
[111.62 --> 119.32] so nakita imagine you are a tour guide give me a tour to the world of neon so let's look at a modern
[119.32 --> 125.78] developer as people say never bet against javascript so more than 50 probability this person is writing
[125.78 --> 133.38] javascript and typescript using react next js deploying their code on a platform like purcell
[133.38 --> 141.92] and really care about design so working with figma working with a local designer or maybe starting to
[141.92 --> 149.10] work with an ai designer and using technology like purcell just shipped called v0 and then like you got to
[149.10 --> 154.90] store data somewhere so you go to neon or use purcell postgres which is powered by neon you push a
[154.90 --> 162.10] button and now you're able to write and read from neon and then that kind of just works out of the box
[162.10 --> 168.70] the majority of your time you spend crafting your application crafting the front end and then the
[168.70 --> 173.80] database is just kind of like it's kind of there and just kind of works and you don't think too much
[173.80 --> 180.64] about it and when you run previews when you run next versions of your software you can send your
[180.64 --> 186.42] collaborators your other engineers on your team or your product managers or designers a version of
[186.42 --> 191.00] your app the version of the future that you want to debate if you want to comment on and it's fully
[191.00 --> 197.64] sandbox you know from your front end to back end to the database that's like a good part of this world
[197.64 --> 203.38] the world is obviously much bigger than just building front end apps there's also back end apps there are
[203.38 --> 209.26] python apps there are java apps and all of those things we're perfecting the world for the world that i
[209.26 --> 214.94] just described and we think that the rest of the world will follow uh and the rest of the world is
[214.94 --> 223.60] java apps rast apps back end apps queues scheduling aws lambda kubernetes containers again the tech world
[223.60 --> 231.52] of the back end is just enormous but i think perfecting this first world that i described will create a
[231.52 --> 236.44] standard in developer experience that the rest of the developer world will just follow so you have
[236.44 --> 242.32] versell postgres powered by neon you've got neon as an integration to versell you've got neon out there
[242.32 --> 247.72] at neon.tech as self-serve where anybody could just go and sign up and start up right now you're optimizing
[247.72 --> 252.66] for this new standard but what's the response been like what's the community saying what's the community's
[252.66 --> 260.04] response we are lately onboarding close to 2500 databases a day that's more than one database a
[260.04 --> 265.94] minute of somebody in the world coming to neon either directly or through the help of our partners
[265.94 --> 272.02] and they're able to experience what it feels like to program against database that looks like a url and
[272.02 --> 277.38] program against database that can support branching and be like a good buddy for you in the in the
[277.38 --> 283.52] software development life cycle so that's exciting and while that's that's exciting the urgency at neon
[283.52 --> 288.76] is currently is unparalleled there you go if you want to experience the future go to neon.tech
[288.76 --> 294.54] on demand scalability bottomless storage database branching everything you want for the postgres of the
[294.54 --> 297.54] future once again neon.tech
[297.54 --> 301.54] so
[301.54 --> 306.54] so
[306.54 --> 310.54] so
[310.54 --> 314.54] so
[314.54 --> 316.54] so
[316.54 --> 320.54] so
[320.54 --> 338.42] let's begin the beginning postgres yes postgres 1986 something like that wasn't it forever
[338.42 --> 344.62] i mean this released from berkeley university in 1995 okay i'm not sure how long it was developing the
[344.62 --> 349.54] university before that several years i read there's roots back into the 80s but i could be wrong it could be
[349.54 --> 356.54] either way that's ancient history right that's a long time ago and yet it's the darling of
[356.54 --> 362.54] most developers today postgres it's become popular like you know when i started to hack on postgres it
[362.54 --> 367.54] was not the case like it was not the most popular one it was not the darling so you would actually have
[367.54 --> 373.54] to explain i'm not sure what happened i think post is just matured um so people used to ask the question