The power of software is enormous, but the code can only be as good as the humans who write it. Despite popular belief, "being good" has nothing to do with character predisposition. It is a product of an intentional effort to nurture care and compassion.
Today we talk with Liz Acosta, a software engineer and a developer advocate at Stacklet. Liz's past professions as a copywriter, social media manager, and odd job freelancer give her a unique perspective on software development and enables her to help teams collaborate with empathy.
When you finish listening to the episode, connect with Liz on LinkedIn or find her on Stacklet.
Mentioned in this episode:
Liz on LinedIn at https://www.linkedin.com/in/lizacostalinkedin/
Liz on Stacklet at https://stacklet.io/blog/author/liz-acosta
Exercism at https://exercism.org
Empathy in Tech at https://empathyintech.com
Building useful software requires more than just knowing how to write code. It demands curiosity to understand the problem which the software is supposed to resolve. It also requires the willingness to understand the people - not only those who will use it but also those who are building this software with you!
Today we talk with Dawn Ahukanna, the design principal and front-end architect at IBM. She leads an integrated and consistent user-focused design across enterprise software focused on data analytics and cognitive user experiences. She shares the methods and the tools she uses when figuring out how people work - an essential piece of knowledge if you want to create the best user experience.
When you finish listening to the episode, make sure to connect with Dawn on Twitter and LinkedIn.
Mentioned in this episode:
Dawn on Twitter at https://twitter.com/dawnahukanna
Dawn on LinkedIn at https://www.linkedin.com/in/dawnahukanna
Dawn’s website at http://dahukanna.net
Working together in a team requires a lot of emotional intelligence, adaptability, and empathy. Bringing two teams working together after acquisition and a merger might seem like requiring superpowers on top of that.
Today we talk with Matt Dixon, the founder, and CEO of Front Range Systems. Matt is a tech executive helping newly acquired technology businesses create a unified culture within their workplaces. Matt gives us a sneak-peak into his practices of helping teams develop a growth mindset, adapt to new technological challenges, and become high-performing.
When you finish listening to the episode, check out the Front Range Systems website at https://frontrangesystems.com, and connect with Matt on Twitter.
TypeScript has been around for quite a while, and its popularity speaks for itself. It has never been more important to understand how to gradually and sustainably shift to TypeScript within the existing code-base.
Today we talk with Sam Lanning, an independent software contractor in the humanitarian sector with many years of experience at GitHub and Semmle. Sam's vast experience in using TypeScript to speed up coding, eliminate debugging, and reduce technical debt helps us see the benefits of this popular programming language and foresee how to transition to it.
When you finish listening to the episode, find Sam on GitHub and connect with them on Twitter and LinkedIn.
Mentioned in this episode:
Sam on Github at https://github.com/s0
Sam at LinkedIn at https://uk.linkedin.com/in/smlanning
Sam at Twitter at https://twitter.com/samlanning
TypeScript at https://www.typescriptlang.org
We often use real-life metaphors to make software development concepts more approachable and understandable, especially for the people just entering the field. Sometimes, however, the reverse approach could help a seasoned coder to cope with the real world.
Today we talk with Casey Watts, the author of Debugging Your Brain, a clear applied psychology, and a concise self-help book. The human brain is buggy, just as any legacy code is. Casey tells us about techniques that can help us refactor our thinking, speed up our thought processes and ultimately debug our brains.
When you finish listening to the episode, connect with Casey on LinkedIn and Twitter, visit his website at https://www.caseywatts.com and https://www.debuggingyourbrain.com, and check out his book Debugging Your Brain.
Mentioned in this episode:
Casey on LinkedIn at https://www.linkedin.com/in/caseywatts/
Casey on Twitter at https://twitter.com/heycaseywattsup
Debugging Your Brain at https://www.amazon.com/Debugging-Your-Brain-Casey-Watts/dp/0578755033?
Debugging Your Brain Website at https://www.debuggingyourbrain.com
Casey’s Website at https://www.caseywatts.com
Cognitive distortions at https://www.debuggingyourbrain.com/distortions/
Many programming concepts seem too complex and intimidating to outsiders. That is perhaps the main reason why writing code remains such an exclusive profession, even in the age where virtually everything depends on a written code! But does everything have to be so complicated?
Today, we talk with Sy Brand, Microsoft C++ Developer Advocate, and a specialist for compilers and debuggers for embedded accelerators. Sy is also known for their YouTube Channel - Computer Science with Sy's Cats - where they explain programming and computer science concepts with household objects and cats. After watching only a few of Sy's videos, you will feel that programming can, and should, be much more approachable and inclusive.
When you finish listening to the episode, connect with Sy on Twitter, start following their YouTube channel, and check out one of their live coding sessions at Twitch.
Mentioned in this episode:
Sy Brand on Twitter at https://twitter.com/TartanLlama
Computer Science with Sy’s Cats at https://www.youtube.com/c/SyBrandPlusCats/featured
Sy Brand on Twitch at https://www.twitch.tv/tartanllama
Ivan Čukić, Functional Programming in C++ at https://www.amazon.com/Functional-Programming-programs-functional-techniques/dp/1617293814
Writing Error Messages for Humans at https://www.flutterwave.design/writing-error-messages-for-humans/
Imagine if you could perform static analysis, find bugs, and enforce code standards in more than seventeen languages with a single tool. Imagine if you could scan your code with more than 1,000 community pre-written rules and if you could easily add your own rules to match your code perfectly. Imagine if you could then flag the issues and get results in pull requests, Slack, or anywhere else without as much as a click of a mouse.
Well, it appears that you can do all of this and more. Today we talk with Isaac Evans, an MIT alumnus, a former computer scientist at the US Department of Defence, and a founder and CEO of r2c. His company, r2c, stands behind Semgrep, a lightweight, offline, open-source, static analysis tool that profoundly improves software security and reliability to safeguard human progress.
When you finish listening to the episode, see how Sengrep can improve your code at https://semgrep.dev, or visit https://r2c.dev if you need enterprise solutions for large businesses.
Mentioned in this episode:
Isaac Evans on LinkedIn at https://www.linkedin.com/in/isaacevans/
Semgrep at https://semgrep.dev
r2c at https://r2c.dev
Brian Foote, Joseph Yoder, The Selfish Class at http://www.laputan.org/selfish/selfish.html
Richard Dawkins, The Selfish Gene at https://www.amazon.com/Selfish-Gene-Anniversary-Landmark-Science-dp-0198788606/dp/0198788606/ref=dp_ob_title_bk
Many IT industry giants (including Google, Facebook, Microsoft, Uber, Airbnb, and Twitter) employ gigantic monorepos to scale build systems and version control software. Although only recently named, monorepos have been around for several decades.
Today we talk with Darko Fabijan. Darko is the co-founder of Semaphore CI, where he and his team explore new tools and ideas that improve developers’ lives. We dive deep into the benefits and challenges the transition to and utilization of monorepos can bring to your workflow and software development practice.
When you finish listening to the episode, connect with Darko on Twitter and visit the Semaphore CI website at https://semaphoreci.com, where you will find great solutions for decluttering your workflow.
Mentioned in this episode:
Darko on Twitter at https://twitter.com/darkofabijan
Semaphore CI at https://semaphoreci.com
A big part of dealing with legacy systems is not on the level of software architecture but interior design. The code needs to be welcoming for people who use it and maintain it, free of clutter, clean and tidy.
Today we talk with Ester Daniel Ytterbrink. Ester Daniel is a coder who likes to think about how people work as a group to create great software sustainably. They have a blog (Chocolate Driven Development) where they write about software development with human interaction and psychology in focus. They tell us about the main principles of software interior design, guiding you to build more comfortable, functional, and efficient code.
When you finish listening to the episode, visit Ester Daniel's blog, where you can connect with them and get some great ideas.
Mentioned in this episode:
Ester Daniel on Twitter at https://twitter.com/edytterbrink
Chocolate Driven Development Blog at https://www.chocolatedrivendevelopment.com
Douglas Squirrel, et al, Agile Conversations: Transform your Conversations, Transform Your Culture at https://www.amazon.com/Agile-Conversations-Transform-Your-Culture/dp/B086D5RBWS/
Don Norman, The Design of Everyday Things at https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654/
The first step to mastering any skill is demystifying it. However, this is not easy to achieve on your own, and often masters of the craft around you are not as helpful as you would hope. It is easy to forget how it is to be a novice once we achieve expertise in some field, and this leads many of us to lose the ability to introduce the craft to the incoming forces patiently and in simple terms.
Today we talk with Sharon DeCaro. Sharon has been working as a software engineer for five years. However, this wasn't her career choice when she enrolled in the mathematics and music program at her university. Listen to Sharon as she tells us about her journey into the software industry, the hurdles she encountered, and the ways she overcame them to become a software engineer.
When you finish listening to this episode, make sure to connect with Sharon on LinkedIn.
Mentioned in this episode:
Sharon on LinkedIn at https://www.linkedin.com/in/sjdecaro/
Andrea Goulet, Carmen Shirkey Collins, Empathy Driven Software Development at https://www.empathyintech.com
We talk a lot about software on this show. But in this episode, we steer away from our usual practice and look at one piece of hardware that every computer user is in touch with the most. Yes, it is a keyboard!
Today we talk with Jesse Vincent - a software developer turned hardware manufacturer. Jesse is best known for his work with the Pearl programming language and the ticket-tracking system Request Tracker. However, since he invented one of the most comfortable keyboards on the market - now sold-out Keyboardio Model 01 - many associate him with hardware production.
Jesse doesn't hold back. He reveals many secrets of modern hardware manufacturing and how to use your software experience to organize your production process.
When you finish listening to the episode, make sure to support the production of the new Keyboardio Model 100 on Kickstarter (ends July 31, 2021), connect with Jesse on Twitter, and visit Keyboardio website at https://shop.keyboard.io.
Mentioned in this episode:
Jesse Vincent Wikipedia page at https://en.wikipedia.org/wiki/Jesse_Vincent
Jesse Vincent on Twitter at https://twitter.com/obra
Keyboardio Model 100 Kickstarter Campaign https://www.kickstarter.com/projects/keyboardio/model-100?ref=104lo3
Keyboardio website at https://shop.keyboard.io
TRON TK1 keyboard at http://xahlee.info/kbd/TRON_keyboard.html
FingerWorks TouchStream at https://ergocanada.com/products/keyboards/fingerworks_lp.html
Microsoft Natural Ergonomic Keyboards at https://en.wikipedia.org/wiki/Microsoft_ergonomic_keyboards
We seldomly dive deep into discussing any particular programming language on this show. However, today we are making an exception, and we talk with Chrissy LeMaire about PowerShell. Chrissy is a GitHub star, double Microsoft MVP, and a co-author of the book Learn dbatools in a Month of Lunches. She is currently a blue teamer who uses PowerShell to make the world more secure. Chrissy shares some neat PowerShell secrets that transform this framework from an ideal programming language for beginners to a well-rounded and powerful developing tool.
When you finish listening to the episode, connect with Chrissy on Twitter, get dbatools at https://dbatools.io and check out Chrissy’s book Learn dbatools in a Month of Lunches.
Mentioned in this episode:
Chrissy on Twitter at https://twitter.com/cl
dbatools at https://dbatools.io
Chrissy LeMaire, Rob Sewell, Jess Pomfret, Cláudio Silva, Learn dbatools in a Month of Lunches at https://www.manning.com/books/learn-dbatools-in-a-month-of-lunches
Steve McConnell, Code Complete: A Practical Handbook of Software Construction, 2nd Ed, at https://www.amazon.com/s?k=the+code+complete&ref=nb_sb_noss_2
We behave with the cloud as a subset of technology like a teen who just learned how to drive. We are at the point where capabilities have far exceeded the ability to comprehend consequences. We have the power in our hands to change our life and other people's lives both in positive and negative ways. However, we lack the experience to foresee these results.
Today we talk with Bobby Allen, Vice President of Strategic Alliances at Turbonomic and cloud therapist. He helps us understand the advantages and pitfalls of the cloud and teaches us how to assess our own needs and the risks we might face while using the technology.
When you finish listening to the episode, make sure to connect with Bobby on Twitter and LinkedIn, and visit his website at https://bobbyjallen.me.
Mentioned in this episode:
Bobby on LinkedIn at https://www.linkedin.com/in/ballen-clt/
Bobby on Twitter at https://twitter.com/ballen_clt
Bobby’s website at https://bobbyjallen.me
Turbonomic at https://www.turbonomic.com
Technical debt is a recurring theme of this show. We talk about it almost as often as it pops out in any legacy code! Today we go back to discussing technical debt with Jim Humelsine. Jim has been a software development professional since 1985. Jim's passion is design patterns, but he recently expanded his interest to software practices and procedures. Jim is also an economics and especially game theory enthusiast, and on top of everything, he is a trombone player! We dive deep with Jim into the economics of technical debt, the root causes of its ever-presence, and the ways to get rid of it. When you finish listening to the episode, make sure to connect with Jim on Twitter and LinkedIn.
Mentioned in this episode:
Jim on Twitter at https://twitter.com/jhumelsine
Jim on LinkedIn at https://www.linkedin.com/in/james-humelsine-16b0749/
Freakonomics podcast at https://freakonomics.com/archive/
Many legacy systems lack adequate test coverage. They might not have much coverage at all, or the existing tests might be inefficient or paint a wrong picture about the stability of the system. Enhancing test coverage in legacy applications is a complex task with many pitfalls.
Today we talk with Floyd Hilton, a software developer with many years of experience in multiple domains, including semiconductor manufacturing, financial aid delivery, energy conservation, and healthcare. He co-founded the Augusta Polyglot Group, which meets once a month to teach and learn new languages. Floyd's current interest is in finding the best strategies for adding testing to existing software systems. He shares with us some of these strategies and the tools he uses when beefing up test coverage in legacy systems.
When you finish listening to the episode, make sure to connect with Floyd on Twitter and LinkedIn, and visit his website at http://www.floydhilton.com,
Mentioned in this episode:
Floyd on Twitter at https://twitter.com/fhilton
Floyd on LinkedIn at https://www.linkedin.com/in/floydhilton/
Floyd’s website at http://www.floydhilton.com
Augusta Polyglot Group at https://augusta-polyglot.github.io
DbUp at https://dbup.readthedocs.io/en/latest/
Cypress at https://www.cypress.io
There has been a noticeable uptick in the adoption of public cloud providers. At the same time, the voices advocating for the abandonment of traditional data centers are getting louder. Keeping servers around to keep running their business might be overkill for many companies. For others, it could be the only reasonable choice. And even if you decide to transition to the cloud, how do you know which of its features you need?
Today we talk to Sarah Musick, the systems engineering principal at CloudGenera, a workload placement decision engine, where she spearheads the onboarding efforts with enterprise customers. Sarah is a big believer in the targeted adoption of the public cloud in tech - the approach based on the understanding that the cloud should serve the application rather than the other way around. She helps us understand how to assess our data management needs and how to choose the options that best serve those needs.
When you finish listening to the episode, make sure you connect with Sarah on LinkedIn and visit CloudGenera website.
Mentioned in this episode:
Sarah Musick on LinkedIn: https://www.linkedin.com/in/sarahlmusick/
CloudGenera Website: https://go.cloudgenera.com
Common Lisp was written in the 80s as a kind of an amalgam of the existing Lisps at the time. To make sure the Common Lisp would stay relevant, it was made backward compatible so that existing legacy systems could run on it. One thing in common to these big old systems like Lisp is a lot more mutation, and the cool thing about this legacy is that it has a baked experience – it learns and it has learned.
Today we talk to Eric Normand, an experienced functional programmer, trainer, speaker, and consultant on all things functional programming. He started writing Lisp in 2000 and is now a Clojure expert, producing the most comprehensive suite of Clojure training material at purelyfunctional.tv. He also consults with companies to use functional programming to better serve business objectives.
We talk about problems in legacy code basis utilizing functional programming, the abstract nature of programs, the wisdom of Lisp, and more.
When you’re done listening to the episode, make sure to check out Eric’s Clojure training and his podcast, as well as connect with him on LinkedIn.
Mentioned in this episode:
Eric Normand on LinkedIn: linkedin.com/in/eric-normand-61a70366/
Eric Normand’s podcast: Lispcast.com
Eric Normand’s websites: https://lispcast.com and https://purelyfunctional.tv
Eric Normand’s Clojure training: Purelyfunctional.tv
Eric Normand’s book Grokking Simplicity: https://www.manning.com/books/grokking-simplicity?utm_source=lispcast&utm_medium=affiliate&utm_campaign=book_normand_grokking_8_20_19&a_aid=lispcast&a_bid=72596968Use discount code TSSIMPLICITY for 50% off.
Software engineers perceive that technology advances in an orderly, linear fashion. This makes the novelties very attractive. However, the reality is that we tend to go through technology in cycles. Recognizing this is crucial for understanding how to make the right technical decisions while preserving the value of the old technology.
Is it better to build from scratch or build on what you have? When do you invest in something brand new, and when do you lean onto the foundations of the existing expertise?
Today we search for answers to these questions with Marianne Bellotti, the author of Kill It with Fire –Manage Aging Computer Systems (and Futureproof Modern Ones). Marianne is internationally known for tackling some of the oldest, messiest, and most complicated computer systems in the world, and she currently runs identity and access control at Rebellion Defense.
When you finish listening to the episode, make sure you follow Marianne on Twitter and get a copy of her book.
Mentioned in this episode:
Marianne Bellotti on Twitter at https://twitter.com/bellmar
Marianne Bellotti, Kill It with Fire –Manage Aging Computer Systems (and Futureproof Modern Ones) at https://www.amazon.com/Kill-Fire-Manage-Computer-Systems/dp/1718501188
Rebellion Defence at https://rebelliondefense.com
For most teams, dependency freshness is a pain that is often ignored. “If it works –don’t change it” is the prevailing attitude, but as a lot of applications become web-focused, dependencies inevitably start gaining traction. Why does dependency freshness matter, and how do we proactively stay on top of it?
Today we present Freshli - the dependency freshness tool we have been working on. The microphone goes to the team involved: Cassandra Carothers, Technical Sales Manager here at Corgibytes, and Catalina De la Cuesta, Chris Cumming, and Dave Farinelli, our Lead Code Whisperers. The Freshli tool captures historical libyear metrics about a project's dependencies. Freshli stays alongside your codebase and works together with code quality tools, showing where your project is going overtime. It is designed to work with multiple languages, and it currently supports Ruby, Perl, Python, PHP, and .NET.
If you are interested to know more about Freshli, make sure you reach out to our team on LinkedIn after you’ve listened to the episode.
Mentioned in this episode:
Cassandra Carothers at linkedin.com/in/cassandramcarothers/
Catalina De la Cuesta at linkedin.com/in/catalinadelacuesta/
Dave Farinelli at linkedin.com/in/dfar-io/
Chris Cumming at linkedin.com/in/chris-cumming/
Libyear at https://libyear.com
Corgibytes at https://corgibytes.com
Freshli at GitHub at https://github.com/corgibytes/freshli-lib
When developers talk about what they find exciting, they usually talk about new things. Very little content is about the actual job, about working in the existing system. When they do talk about legacy, they usually focus on how much they hate it. Where does that animosity come from and how do we confront it?
Today we get to the bottom of it with Barry O’Sullivan. Barry is a modern web development contractor with 15 years of experience in legacy web applications. He is the founder of DDIE and the co-organizer of PHP Dublin. We discuss the fear response to legacy code, the mocking of those who created it, and the ignorance of those who are quick to mock. We look at the common mistakes that lead to the fear of legacy code and discuss some common-sense solutions to overcome what is essentially a social and skill-based problem with technology.
When you are done listening to the episode, make sure you connect with Barry on LinkedIn, and follow him on Twitter and Github.
Mentioned in this episode:
Barry O’Sullivan on LinkedIn: https://www.linkedin.com/in/barryosu/
Barry O’Sullivan on Twitter: https://twitter.com/barryosull
Barry O’Sullivan on Github: https://github.com/barryosull
Barry O’Sullivan on the web: https://barryosull.com
PHP Dublin: https://www.meetup.com/PHP-Dublin/
Matthew Stewart, The Management Myth: Debunking Modern Business Philosophy: https://www.amazon.com/Management-Myth-Debunking-Business-Philosophy/dp/0393338525
We like to think that technology is our objective and neutral assistant, our faithful lieutenant constrained with science and armed with cold, hard data. But this is incorrect. Technology reflects the attitudes of humans who created it. It contains our biases and our preconceived notions. It reflects who we are while distorting our perception of who we think we are, transforming our impulse for binary simplifications into the strict binary framework of ones and zeroes. Inevitably, this leaves some folks out.
Today we talk with Erin White, Head of digital engagement at Virginia Commonwealth University Libraries in Richmond, VA, on their fascination with the intersections of equity, justice, and computer systems. Erin tells us how technology can both advance and hamper the achievements of social equality, and how inclusive software design can help us realize our own biases and remove them from our code.
After you finish listening to the episode, make sure you connect with Erin on LinkedIn and Twitter, where they write about technology and progressive politics.
Mentioned in this episode:
Erin on LinkedIn: https://www.linkedin.com/in/erinrwhite/
Erin on Twitter: https://twitter.com/erinrwhite
Erin White, Trans-Inclusive Design at https://alistapart.com/article/trans-inclusive-design/
Many analytical models can help you to measure some aspects of the quality of your codebase. However, only a combination of these models can give you complete information about your code's integrity and the real-world necessity for its improvement. Today we talk with Dan Sturtevant, the CEO of Silverthread Inc and a Technology and Operations Management Researcher at the Harvard Business School. Dan shares with us the solutions for diagnosing software health and aligning it with business performance goals and desired financial outcomes.
When you finish listening to the episode, make sure to connect with Dan on LinkedIn, visit Silverthread's website at https://www.silverthreadinc.com, and check out their CodeMRI diagnostics tool.
Mentioned in this episode:
Dan on LinkedIn at: https://www.linkedin.com/in/dansturtevant/
Silverthread, Inc at: https://www.silverthreadinc.com
CodeMRI at: https://www.silverthreadinc.com/codemri-diagnostics
Carliss Y. Baldwin, Design Rules, Vol. 1: The Power of Modularity at: https://amzn.to/39XSGA3
Ruby on Rails is a fast-moving community and it is not always easy to keep up with it. Given the efficiency of the framework, however, it is well worth trying. Today we talk to Robby Russell, creator of Oh My Z Shell, host of Maintainable software podcast, and CEO of Planet Argon – a software consultancy that helps organizations improve their existing Ruby on Rails applications. We chat with Robby about his own beginnings, the creation of the Oh My Z Shell, the early days of Ruby on Rails, and how to keep up with the fast-moving Rails community. When you finish listening to the episode, connect with Robby on Twitter and LinkedIn, and make sure to start following his podcast Maintainable.
Mentioned in this episode:
Robby Russell on Twitter at https://twitter.com/robbyrussell
Robby Russell on LinkedIn at linkedin.com/in/robbyrussell/
Robby Russell on GitHub github.com/robbyrussell
Planet Argon at planetargon.com
Oh My Z Shell at ohmyz.sh
Oh My Z Shell on Twitter at twitter.com/ohmyzsh
Maintainable podcast at https://maintainable.fm
Security is a big topic with many facets, and this is especially true for microservices. Microservices deployment has been around for some time, but security didn’t get much attention from developers – they simply trusted the network. Today we talk with Prabath Siriwardena and Nuwan Dias, authors of Microservices Security in Action* and deputy CTOs of the WSO2, on the state of microservices security today. We dig deep into the issues of infrastructure, available tools, procedures, and challenges in predicting the threats and integrating security patches into microservices.
When you finish listening to the episode, make sure to connect with Prabath and Nuwan on LinkedIn and Twitter, and book their services at https://wso2.com with a steep 35% discount with the code podlegacy20. And don’t miss the opportunity to read their book Microservices Security in Action for free with the codes provided below (codes expire in March 2021).
Mentioned in this episode:
Prabath Siriwardena on LinkedIn at https://www.linkedin.com/in/prabathsiriwardena/
Prabath Siriwardena on Twitter at https://twitter.com/prabath
Nuwan Dias on LinkedIn at https://www.linkedin.com/in/nuwandias/?originalSubdomain=lk
Nuwan Dias on Twitter at https://twitter.com/nuwandias
Read Prabath Siriwardena and Nuwan Dias, Microservices Security in Action at https://www.manning.com/books/microservices-security-in-action?query=nuwan for free with codes:
legmic-1CF1
legmic-3460
legmic-13D3
legmic-511B
legmic-EEE7
Use WSO2 services at https://wso2.com with 35% discount with the code podlegacy20
* Heads up! If you purchase the book through the link above, we will get a small commission which helps us continue to bring quality content to our Legacy Code Rocks! community. You won’t pay a penny more, we receive a small kickback, and you’re supporting our friends who wrote the book. Everybody wins!
In the last episode of 2020, we took a stroll through the little known corridors of coding history with Clive Thompson. Clive is a technology and science journalist for the New York Times Magazine, Wired, Smithsonian, and many other outlets. In his new book Coders: The Making of a New Tribe and the Remaking of the World*, he explores how computer programmers - the people who are increasingly running the world - think and what are their plans for changing the way WE work, think and live. In this episode, he tells us incredible stories of coding past and present, giving us a glimpse into how the future is made. When you finish listening to this episode, connect with Clive on Twitter, visit his website, and enjoy reading his books*.
Mentioned in this episode:
Clive on Twitter: https://twitter.com/pomeranian99
Clive’s website: https://www.clivethompson.net/
Clive Thompson, Coders: The Making of the New Tribe and the Remaking of the World at https://amzn.to/34Kf3pR*
About Betty Holberton at https://en.wikipedia.org/wiki/Betty_Holberton
About Margaret Hamilton at https://en.wikipedia.org/wiki/Margaret_Hamilton_(software_engineer)
Michael Abrash, Graphics Programming Black Book at https://amzn.to/3mSxoXV*
BBC micro:bit at https://microbit.org/
Jordan Mechner, The Making of Prince of Persia at https://amzn.to/2KK7hoZ*
* Heads up! If you purchase the book through the link above, we will get a small commission which helps us continue to bring quality content to our Legacy Code Rocks! community. You won’t pay a penny more, we receive a small kickback, and you’re supporting our friends who wrote the book. Everybody wins!