Bungii’s Post

Code that connects, integrates, and innovates. As a Senior API Developer, I’m all about optimizing performance and creating seamless experiences. Let’s build something extraordinary! 💻🌍" #SeniorAPIDeveloper #APIDevelopment #TechInnovation #SoftwareArchitecture #CodingLife #IntegrationSolutions #APIExpert #DigitalInnovation #TechLeadership #ProgrammingLife #WebDevelopment #TechCraftsmanship #DeveloperJourney #BuildingTheFuture #ScalableTech #TechSolutions

#API Success – Let your APIceberg be seen 👀 We all know just how much work and investment can go into an API program - or maybe we need a reminder?   🧙♂️ Who is involved ( non-exhaustive): Architect, Developer, Engineer, Designer, Technical Writer, Integrator, Tester, Security Engineer, Operations Engineer, Platform Engineer, Product Manager, Program Manager, Strategist, Business Analyst, Marketing Manager, Sales Manager, Partnership Manager, Evangelist, Developer Relations Manager, Solutions Consultant 🥨 How ( non-exhaustive): Identify Needs, Define Use Cases, Research Market, Outline Features, Create Specification, Validate Concept, Design Schema, Define Endpoints, Document Contracts, Review Compliance, Develop Prototype, Test Functionality, Iterate Design, Implement Security, Validate Scalability, Optimize Performance, Publish Documentation, Market Adoption, Gather Feedback, Refine Version, Release Version. ❓ Why: Fundamentally to allow business to leverage technology more effectively, expand their reach, and create new value propositions for customers and partners. 💭 What’s my point: I consult daily with passionate, hardworking teams on their API programs. The sheer dedication and knowledge astounds me as teams race to meet goals and work cross functionally to ensure success. In my experience after all the work is done Adoption of the API is the ultimate validation of this effort ( not always). ❗ Make sure your API is readily seen and adopted! 💱

Application Support Engineer – Remote Jobs Listing https://lnkd.in/dQ4GeNde JOB REQUIREMENTS: - Use REST services & Postman API - Monitor production apps & message distributions - Participate in cross-functional teams - Support technology & processes - Manage communication channel configurations - Orchestrate User Acceptance Testing (UAT) - Peer review code, designs, & tests - Work in Agile (e.g., Scrum, SAFe) - Write & verify infrastructure documentation - Communicate effectively & learn from mistakes

🌟 Meet Judy Mosley, our next #IconsOfQuality! 🌟 As the first QA Engineer at TextUs, Judy has been instrumental in building robust automation testing practices and empowering her team to test with confidence. Discover Judy's journey, her insights on testing trends, and her advice for those starting out in software development in our latest blog post. 👉 Check out the full feature: https://bit.ly/4gjr60u #SoftwareTesting #QualityAssurance #BrowserStack

Well said but be aware that learning and teaching across disciplines is a time-intensive process. So this approach could potentially have an impact on the time to market of your software product. Nevertheless a good take since it’s almost always better to have different specialists in a team compared to only a team consisting of generalists.

did you know Postman had the ability to create flows? here is why this matters: we can't build useful Agents without connecting to the place people work. But people work all over the place, you need a ton of API integrations. Postman already helps you consume an API quickly. Now they're helping you orchestrate these API calls. And the next step is obvious: you speak and you get a good boilerplate of the flow built for you. A lot of integrations platforms provide this text to flow experience. What makes postman special is that they store thousands of API collections, so they're in a great place to train the best API integrator.

Recently, I’ve come across Bruno, an incredible open-source alternative to Postman. Bruno is an innovative API testing tool offering offline capabilities, superior security, and seamless integration with version control systems. Its open-source nature and user-friendly scripting make it a preferred choice for developers and QA professionals looking for flexibility and control. 🔹 Storage and Data Management: Postman: Cloud storage requiring internet connection. Bruno: Direct file system storage, offline access, and seamless Git integration. 🔹 Security and Data Control: Postman: Uses proxy servers, posing security risks. Bruno: Direct requests from your machine, ensuring full data control. 🔹 Team Collaboration: Postman: Paid team collaboration features. Bruno: Free, open-source, and easy collaboration through any version control system. 🔹 Collection Runs: Postman: Limited runs based on subscription. Bruno: Unlimited runs, catering to high testing demands. 🔹 Scripting and Assertions: Postman: Requires complex scripting. Bruno: Simplified declarative scripting, optimizing the testing process. Learn more: https://www.usebruno.com Sample collection for practice: https://lnkd.in/gEkrdue5 #APITesting #Automation #Bruno #Postman #QA #SoftwareTesting #DevTools #ManualTesting

We all love the happy path in software. Discussions about new features usually revolve around this elusive thing. Software engineers tend to think a bit more about the "what if X and what if Y?". QA engineers are taking it to the extreme, and that is important for the success of your product As a product owner you need to make sure that you discuss story extremes with a software- and a QA engineer; the 3 amigo's. It is your duty as a product owner to have the final say in what should happen in extreme situations, and not the QA or software engineer, because the world isn't always black and white. Example: "A bottle of wine costs £2 and a customer has £9 credit. Can this customer buy 5 bottles of wine?" The answer is probably no. But what if the customer has £99999 credit, and wants to buy 5000 bottles from you. From a sales perspective you might want to allow this sale to go ahead, but the engineers logic would normally prevent it. It's important to have these conversations and capture the scenarios & answers in acceptance tests. A good starting point is https://lnkd.in/ehjNNrns

Software engineer, software developer, software architect, solution architect, enterprise architect, tester, QA, PO, PM, etc. Once upon a time a developer with super powers was totally responsible for a "software". A long time ago, the most common scenario in a software development projects was, one person, or a small group developing a software navigating throught the different phases and roles. Likewise, the same person was gathering requirements, creating documentation, developing, testing, working on the infrastructure, publishing, mantaining in production, etc.... But, luckily that's being changing at all. Many new roles, small and well defined responsibilities, agility, clear deliverables, focus on what matters, etc. I can say that software development has changed for the better, making visible how important is to improve your processes, roles, definitions, documentation, tools, frameworks, patterns, designs, etc. So what used to be "good" in the past, perhaps its not enough or "good" today. Therefore, we can see that many changes have been necessary over the years to support businesses and provide reliable solutions. Then, we cannot be satisfied with the "good" of today. In my next post I will talk about roles and responsibilities, something that sometimes gets confusing, since a job description to the signing of tasks by the team members.

😡 Have you ever used a software product and said, "didn't anyone TEST this thing before release!?" Well, the trend over the last 20 years has been to get rid of manual QA teams... Three points stood out in a recent conversation about software QA... 1️⃣ Developers must write their own unit, functional, e2e tests, and smoke test their work in pre-prod envs. It's fine to have dedicated SDETs embedded on cross-functional squads help with this. 2️⃣ Manual QA is not a release gate like it used to be. Don't hold up deployment on human processes! But that doesn't mean get rid of them, in my opinion. It means use them as ongoing parallel risk management. Find issues before customers do. (Often those won't be test-covered issues; they can be usability and design issues too). 3️⃣ Customer Success teams, especially in B2B software can be great for this, as opposed to a dedicated QA team. What you're getting is a natural user advocate, not a button pusher. Button pushing is what test automation is for. WDYT? #softwareengineering #qualityassurance #testdrivendevelopment