In the first episode of our new podcast series, Leaders of Code, we sat down with Don Woodlock, Head of Global Healthcare Solutions at InterSystems, and Stack Overflow CEO Prashanth Chandrasekar to discuss data strategy's critical role in AI development.
In our very first episode, Stack Overflow CEO Prashanth Chandrasekar talks to Don Woodlock, Head of Global Healthcare Solutions at InterSystems, about the challenges in their AI journey and the critical role of a robust data strategy in any successful AI initiative.
Ryan welcomes Zach Lloyd, founder and CEO of Warp, to the show to talk about reimagining the terminal. They also discuss why Warp was built in Rust (“it’s definitely harder”), how AI is transforming developer tools, and what Zach (formerly a principal engineer at Google) learned building Docs and Sheets.
How Diffblue leverages machine learning techniques to write effective unit tests.
And how the platform engineering landscape is evolving.
Ryan is joined by Fynn Glover (CEO) and Ben Papillon (CTO), cofounders of Schematic, for a conversation about managing feature flags in software development. They explore theoretical and practical applications of feature flags, the issue of tech debt, and how orgs could manage entitlements and pricing models more effectively.
Ben and Ryan are joined by RJ Tuit, Head of UI Platform and Client Architect at ClickUp, formerly an engineering director at Microsoft. They talk about ClickUp’s vision for a comprehensive productivity platform, the complexities of measuring productivity and UX in software development, how to navigate the hype around AI, and more. Plus: What it was like scaling Microsoft’s cloud services to meet the unprecedented demands of a global workforce in quarantine.
Most job interviews are stressful. This one is not.
On this episode: Al Sweigart is a software developer, developer advocate, and author of ten Python books. He tells Ben and Ryan why he’s such a fan of the language, why it’s a great programming language for beginners, and how it became the default for so many data science and backend AI projects.
Ben and Ryan are joined by software developer and listener Patrick Carlile for a conversation about how the job market for software engineers has changed since the dot-com days, navigating boom-and-bust hiring cycles, and the developers finding work at Walmart and In-N-Out. Plus: “Party in the front, business in the back” isn’t just for haircuts anymore.
The home team convenes to discuss the XZ backdoor attack, what great software engineers have in common, how GenAI is changing the face of drug development, and the rise of managed service providers for AI.
Why replacing programmers with AI won’t be so easy.
While these two areas of study may seem very similar, they do have some differences.
While the future may be a mystery, you can design software to accommodate future changes. But how much future-proofing gets in the way of good design?
An essential part of requirements analysis is understanding which quality characteristics are the most important so that designers can address them appropriately.
French, Swahili, Perl, Danish, Spanish, and C#.
While computing has changed a lot in the 20 years since the SOLID principles were conceived, they are still the best practices for designing software.
Code quality affects the mental state of a programmer, communication within their team, and the incentives attached to their work. Improve your code and you can improve your organizational health and competence as a whole.
Here's three areas where data visualization can make your engineering life easier.
Stretch work assignments are tasks or projects that are a bit beyond an engineer’s current skill or knowledge level and that allow them to improve and learn new things. When done correctly these assignments serve a dual purpose of providing learning opportunities for your engineers, while at the same time completing a project or task that will help your company.
Open source won. Now, the OSS way of working is making inroads into new territories: the corporate engineering department.
There are benefits to being a technical lead at a less software intensive business.
It's now been more than 50 years since the first IFIP Conference on Software Engineering, and in that time there have been many different software engineering methodologies, processes, and models proposed to help software developers achieve that predictable and cost-effective process. But 50 years later, we still seem to see the same kinds of problems we always have: late delivery, unsatisfactory results, and complete project failures.
