Aurélie Vache’s Post

I've updated the service code examples from my re:invent session with Heitor Lessa . The session has over 7000 views on YouTube and it demands up to date code IMHO. The repo is a Python serverless service with a sync and async flows and production ready code with ci/cd and observability best practices, user authentication and more. The repo was created from my AWS Lambda handler cookbook template project. Session link is in the comments. #AWS #Serverless

A gentle reminder for software engineers: • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep. What else would you add? #Copied

FYI, for upcoming Lambda deprecations, we're extending some of our function block create/update dates until 2025 to give you more time to migrate existing functions to a supported runtime. Details in the docs: https://lnkd.in/dZ7K6qY3 #serverless #lambda Specifically: For in-flight deprecations where we have already blocked creates (provided, java8, go1.x, ruby2.7, python3.7, and nodejs14.x), we will defer ‘block updates’ to 2025-02-28. For Node.js 16, we will stick to our planned deprecation date of 2024-06-12. The runtime will be marked deprecated and removed from the console on this date. We will defer block creates to 2025-02-28 and block updates to 2025-03-31. Note that the deprecation date has already been deferred by 9 months past the Node.js 16 end of LTS date, which was on 2023-09-11. For Python 3.8 and .NET 6, we will mark the runtimes as deprecated and remove from console in line with community LTS dates (2024-10-tbc and 2024-11-12, respectively). We will defer block creates to 2025-02-28 and block updates to 2025-03-31. We will send customer notifications 6 months in advance of deprecation (i.e. starting around now, for Python 3.8). Our runtime docs have been updated to reflect the above dates. https://lnkd.in/dZ7K6qY3

My latest blog post on integrating AWX Ansible playbooks with a Python Discord bot! Discover how you can streamline IT automation, schedule tasks, and monitor servers with ease. Check it out on OpenSourcePulse and let me know what you think! #DevOps #Automation #Python #Ansible #AWX #DiscordBot #OpenSourcePulse https://lnkd.in/e_BMRi2P

A gentle reminder for software engineers (you'll thank me later): • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep. What else would you add?

Learn why you need to learn something before learning

🚀 Introducing postman-github -sync – Simplify Your API Collection Workflow! 🚀 About a month ago, I had an idea. A week later I told Ademola Bhadmus At the last Test Fest hosted by The Bug Detective last month, Ademola Bhadmus was demoing this plugin (I wish I knew about the name PostPipe😂 ). Like we promised, It is done and available for all to use. To those who asked when it will be available, you can now have a feel of it. 🎉 Thanks again Ademola Bhadmus. Second tool this year and You're very versatile and it has been fun working with you. I’m excited to announce the launch of postPipe(postman-github-sync), an npm package that helps you push your Postman API collections directly to your favorite CI/CD pipelines – GitHub, GitLab, or Bitbucket – with ease! Here’s what postPipe(postman-github-sync) can do for you: 👉🏾 Seamlessly push your Postman collections (saved as JSON or by collection ID) to your pipeline. 👉🏾 Automatically manage environment variables for you. 👉🏾 A few CLI questions and you're all set – even for existing repositories! Whether you're setting up a new pipeline or working with an existing one, postpipe handles it all, helping to streamline your development process. 🎯 The best part!! No matter whether it is JS or Python ( Cypress or Selenium ) - you are covered!! 👉🏾 Try it out on pip: https://lnkd.in/daNBWbcc 👉🏾 Try it out on npm: https://lnkd.in/eqg3gf3x 👉🏾 Check it out on GitHub: https://lnkd.in/ebM94rsX If you find it helpful, We’d really appreciate your support – give the repo a ⭐️ on GitHub! You can also contribute! You might make it work for Azure DevOps as well! 🤷🏾♂️ 😉 Let me know if you have any feedback. I’d love to hear from you! Abiola Rasaq Idorenyin Ankoh Chibuzor O. Esther Idowu Esther Okafor. Thanks for the demo 😆 hashtag #npm #pip #python #postman #devtools #APIs #GitHub #CI #CD #automation #nodejs #opensource

A gentle reminder for software engineers (you'll thank me later): • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep.

A gentle reminder for software engineers (you'll thank me later): • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep. What else would you add?

A gentle reminder for software engineers (you'll thank me later): • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep. What else would you add?