Listen

Listened to How to position yourself to land the job you want by Eira May 
Post details
The home team talks with Wesley Faulkner, Senior Community Manager at AWS, about what’s going on with this cycle of tech layoffs, how to position yourself for success on the job market, and why it’s worth interviewing for jobs you might not want. Plus: The two things you should do as soon as you get an offer.

 Note

I wish more APIs had an endpoint to get a whoami style response to work out if a) the credentials work and b) who they're for.

When you find a thing and want to check it's still active it's super handy, although I do appreciate that some platforms probably don't add that so you can't check if creds are active as easily

 Note

Don't know what the cause of it is but every time I see he or she instead of they I get unnecessarily annoyed. Like, just use the third person word that's more inclusive too 😠

 Listen

Listened to You’re just a devcontainer.json away with Brigit Murtaugh, PM on the Visual Studio Code team (The Changelog #529)
Post details
This week we’re joined by Brigit Murtaugh, Product Manager on the Visual Studio Code team at Microsoft, and we’re talking about Development Containers and the Dev Container spec. Ever since we talked with Cory Wilkerson about Coding in the cloud with Codespaces we’ve wanted to get the Changelog.com codebase setup with ...

 Listen

Listened to Stack Overflow's architecture, Lobsters' killer libraries, Linux is ready for modern Macs, what to expect from your framework & GoatCounter web analytics (Changelog News)
Post details
Sahn Lam details Stack Overflow’s monolith/on-prem architecture, Hillel Wayne asks the Lobsters community for killer libraries, Linux 6.2 is ready to run on M1 Macs thanks to Asahi Linux, Johan Halse writes up what to expect from your web framework & Eli Bendersky on using GoatCounter for blog analytics.

 Listen

Listened to Creating Mock APIs with Tom Akehurst
Post details
API mocking is a technique used to simulate the behavior of an API without actually connecting to the real API. It is useful for various reasons, including testing, isolation, development, and cost reduction. By using API mocking, developers can test their code without relying on the availability of the real API, isolate the code being