Ergun Ozyurt

Can your team get past your pull request bouncer? One of the problems with requiring all PRs to be approved is that it assumes that all the code that’s merged in is the best it could possibly be. But there’s always times where something is needed more urgently or the PR gets so big that people struggle to review it effectively. Being honest about your codebase and admitting that everything could be better frees you up to merge in so long as your tests pass. Let your tools maintain things like code formatting. Reviewing the code could happen even before a PR is made on a call or from pair programming. And even after it’s been merged, if there’s a good reason to make it better. True continuous integration speeds up your feedback loop and lets your teams get more done – leading to more engineering experience for the team and a stronger codebase.

13

1 Comment

TDD is expensive Like many other niche technologies Delivery of software is not only a technical problem It’s logistical and people problem as well It can be using Kotlin in Java company It can be adding a better database engine It can be applying Event sourcing to all systems You can say all of those are great But there are a couple of non-technical problems 🧠 Knowledge The whole team must know the new solution They need space to learn and practice You may get training from an expert Both cost money and time 🚦 Risk You face the bus factor What if the devs will leave? (they will) How will you maintain the niche solution? How much will it cost to hire or train a replacement? 👩 Hiring Adding new technologies narrows the pool of hires The more niche you go the harder is to find a good fit The longer hiring process will strain delivery You'll have to balance with higher salaries ☯️ Alignment What about your current team? 80% of them like tests but aren’t fans of TDD What will you do? Force them to learn or let them go? The culture will take a hit and retention will sink What can you do instead? Keep it simple Keep it boring Focus on the basics Drive incremental improvement Find alignment before picking new tech Get excited about the features and business If you don’t need to fix niche problems You get more time to deliver value

24

13 Comments

APIs Are Silent Until They’re Not: The Importance of Response Validation” I once worked on a project where the API’s response format was inconsistent. Sometimes, the price field was returned as a string ("100") and other times as a number (100). This inconsistency didn’t cause issues in early testing but broke the front end during integration. Debugging revealed the issue quickly, but it could have been avoided if response validation had been part of our tests earlier. Now, I always include: 1. Schema validation to ensure responses adhere to agreed formats. 2. Negative testing to check how APIs handle invalid requests. API testing is about more than just functionality; it’s about ensuring stability in the bigger picture. How do you approach response validation in your testing?

10

1 Comment

🚀 Exciting Times Ahead for Software Testing! 🚀 I've been diving into the capabilities of the new Claude 3.5 model, and it's clear we're at the forefront of a shift in how we approach software testing. With its ability to simulate user interactions and behave like an actual user, we can now: Run comprehensive end-to-end tests, covering user journeys from start to finish. Improve usability testing, gaining insights into UI/UX and accessibility. Automate interactive and functional tests, ensuring all user inputs and workflows are seamless. Perform exploratory testing in ways that mimic real user behavior, catching edge cases we might not think of. Conduct load and stress tests that simulate thousands of users, helping identify performance bottlenecks before they hit production. Ensure cross-platform consistency, making sure the experience is smooth across all devices and environments. This level of automation and realism is not just a game-changer—it redefines what we consider possible in software quality assurance. I'm genuinely excited to see how these capabilities will evolve and transform the way we think about testing our software. What do you think the biggest benefit of AI-driven user simulation in testing will be for our industry? Let me know your thoughts below! #automatedtesting #aitesting #testing #softwaredevelopment

9

4 Comments

Ever tried wrangling code like it's a herd of cats? 🐱 Welcome to the world of Technology Delivery Management. Picture this: It's Friday. You've promised the client a demo. The code? Not cooperating. Why? Because someone thought 'temporary fix' was code for 'permanent solution' and now you're playing a high-stakes game of Jenga 🧱 with your project timeline. Let's talk about the meeting invites that multiply like rabbits. You wanted productivity? You get a marathon 🏃‍♂️ of discussions about discussions, where the main topic is rescheduling for more discussions. And the documentation. Oh, the documentation. It's supposed to be helpful. Instead, it's a treasure hunt 🗺️. The treasure? Knowing how something actually works versus how it's supposed to work. The map? Non-existent. But here's the kicker: the 'quick fixes' that are anything but quick. They're like duct tape on a leaking pipe. Sure, it holds—for exactly two seconds before it turns into a fountain of 'I told you so.' So, why do we stick around? For the magic moments✨. When the code finally compiles without errors, the client's feedback is a smile, not a sigh, and the team high-fives 🙏 not because it's over, but because we conquered. Laugh at the chaos. Share your most bewildering tech delivery problem. Let's find the humor in our hurdles and remember why we love this crazy ride 🎢.

11

🤝 Pair Testing with Developers: A Collaboration for Quality 🤝 Pair testing with developers has helped me catch issues early and get valuable insights into the code. Here’s why it works: 🔹 Early Bug Detection: Pair testing often reveals potential issues before they reach the testing phase. 🔹 Shared Knowledge: Developers gain insights into testing, and QA understands the codebase better. 🔹 Faster Resolution: Immediate feedback means we can address issues on the spot, saving time in the long run. How do you collaborate with developers in your role? #PairTesting #Collaboration #QualityAssurance #QAAndDev #SoftwareTesting

17

7 Comments

Your dev team is under resourced Spoiler - it always will be Don't get trapped thinking if you just had two more (or fifty more) devs you'd be able to work through the backlog and get ahead. The problem is that teams try and filter and prioritise *down stream* on outputs. 100's of outputs. Try filtering and prioritising *up stream* on strategic outcomes that matter to the business (and across the business).

12

9 Comments

🤔 Is the debate around remote and hybrid work setups getting stale, or is it more relevant than ever? Our guest Rob Wade Head of IT at Kuflink emphasises the value of remote work for both employees and businesses, but are we really having the productive discussions needed to optimise these setups? Let's dive into the benefits, challenges, and everything in between. Share your thoughts and experiences below! 👇 🚀🎬 Watch Part Two now: YouTube: https://lnkd.in/e-s4qy5k 🔊 Prefer to listen: Apple Podcasts: https://lnkd.in/epwksZFh Spotify: https://lnkd.in/eEAXFPBt #Leadership #Inspiration #Motivation #Growth #Podcast #SoftwareQuality #DataAnalysis #BugPrevention #RemoteWork #HybridWork #Productivity #TechTalk

6

Ownership between engineering teams is extremely hard topic. Specifically when teams are owning part of the app / framework / API. And from my experience it always goes through some weird cycle: 1. Component created, everyone starting contributing to it. Obviously, there is no guidelines, generic principles, or even code style. When everyone owns something - that means that no one responsible. 2. Eventually component become critical for business, errors in this component becomes more expensive, time to support it - increasing. Business decided that some team need to own this component. 3. Owning team will start paying tech debt for all these years of mindless committs, refactor something, rewrites. 4. Since guidelines are still not prepared, and component is still kind of messy - owning team does not allow anyone to commit there anymore, or asking tons of changes to merge request. To the point that no one wants to work with that team, or touch that component. Instead of this teams starting creating feature requests. 5. Business can’t be stopped, so owning team starts satisfying those feature requests with paying tech debt in parallel. More teams coming up with feature requests, and owning team starts drawning under never ending requests. They coming up with prioritization frameworks, which always makes someone unhappy because of lower priority of their requests. 6. Finally when team is tired, burned out, and their backlog is way larger than they can consume - someone come up with contribution model - list of guidlines, instructions and requirement on how other team can contribute to the component. Congratulations - now you have a platform team! What will be more optimal way? Create contribution model / guideline generic for the whole company, and apply it every time when more than one team using same component. Save your people :)

58

5 Comments

📢TOP TIP for AWS focused DevOps/Platform/Site Reliability Engineers looking for a new position📢 I have spoken to 3 Engineering Directors this week, and they all told me they are getting so many applications for their mid-senior level roles. They openly admit that they have less time than ever to read profiles thoroughly and need the resume to stand out to them EASILY & QUICKLY. Here is what was on their watchlist when reviewing a profile👀 🎯AWS, Terraform, Kubernetes & CI/CD experience 🎯Software Development skills 🎯Evidence of the key technologies used per role (spell it out for them) 🎯Where you have made an impact on the business/the project ("I" not "us") 🎯How you have saved time and/or money 🎯Evidence of strong communication skills If you'd like to know what the industry leaders in Cloud & Platform Engineering are looking for feel free to reach out to me📩 #tethr #devops #sre #platform #resume

11

𝗧𝗼 𝗔𝗹𝗹 𝗧𝗵𝗼𝘀𝗲 𝗪𝗮𝗻𝘁𝗶𝗻𝗴 𝗔 𝗣𝗮𝘆 𝗥𝗶𝘀𝗲 𝗜𝗻 𝟮𝟬𝟮𝟱: 𝘵𝘩𝘪𝘴 𝘪𝘴 𝘧𝘰𝘳 𝘺𝘰𝘶 - 💰 If you’re an AEM developer or tech professional thinking about asking for a pay rise in 2025, here’s some advice I’ve picked up along the way. It’s not just about what you ask for but how you go about it. 𝟭. 𝗞𝗻𝗼𝘄 𝗬𝗼𝘂𝗿 𝗩𝗮𝗹𝘂𝗲. Take a moment to reflect—how have you contributed this/last year? Maybe you built reusable components that saved weeks of development time or optimized integrations that enhanced team efficiency. These aren’t small wins. Measure them, and when possible, link them to business outcomes. 𝟮. 𝗙𝗿𝗮𝗺𝗲 𝗜𝘁 𝗦𝗺𝗮𝗿𝘁𝗹𝘆. Think beyond yourself and tie your impact to the company’s goals. For example: "This AEM workflow enhancement improved our content velocity by 30%, and I’d love to discuss how my contributions align with our team’s direction." 𝟯. 𝗞𝗲𝗲𝗽 𝗮𝗻 𝗘𝘆𝗲 𝗼𝗻 𝗧𝗿𝗲𝗻𝗱𝘀. The landscape is shifting quickly—AEM developers skilled in cloud integration and headless solutions are highly sought after. Understand where your expertise fits within market benchmarks. Staying informed is a strength. 𝟰. 𝗗𝗲𝗺𝗼𝗻𝘀𝘁𝗿𝗮𝘁𝗲 𝗖𝗼𝗺𝗺𝗶𝘁𝗺𝗲𝗻𝘁. Think of the pay rise conversation not as an ending, but a starting point. How can you grow alongside the organization? Whether it’s leading migrations, mentoring, or improving processes, make it clear you’re playing the long game. At its core, asking for a raise should feel natural if you’ve earned it, so long as you approach it with confidence and humility. 𝗔𝗻𝗱 𝘁𝗼 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀 & 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 𝘁𝗵𝗶𝘀—let’s remember that recognizing contributions is key to fostering engagement and retention. Creating a space where team members feel supported to advocate for themselves benefits everyone. Here’s to making 2025 a year of growth, recognition, and teamwork. 🌟

13

Do you want to know what is Gorilla Testing? ✅ Monkey Testing - Monkey Testing, also known as random testing, means trying random things to see how your software responds. It's like letting a curious monkey loose on your app to find any hidden issues. 1. No predefined test cases here! Key Features: - Trying random actions - Stress testing - Finding unexpected bugs ✅ Gorilla Testing - Gorilla Testing is all about carefully checking specific parts of your app. It's like having a focused gorilla making sure your critical features are rock solid. - Crafted test cases are meticulously designed to thoroughly test targeted features. Key Features: - Focused testing - Deep dive into important features - Emphasis on quality - Manual testing with human insight Why Use Both? - Combining Monkey Testing and Gorilla Testing in your testing strategy provides the best of both worlds. - Monkey Testing uncovers hidden vulnerabilities, while Gorilla Testing ensures the reliability of your most critical features. - Together, they form a powerhouse duo that elevates the quality of your software and boosts user satisfaction. Credits : Nada Alkatout

4

#backtokotlin #androiddev | I've just had a rather productive morning today. I was able to catch up on some of the work for my temp QA job while also dealing with my own recovery, which is still slightly inconvenient at the moment. But I'll work through it. I always do. And then I wanted to spend the 2nd part of my Saturday resuming my Android/Kotlin development refresher. It has been a couple of years since my last active mobile app development. But this feels almost like riding a bike. The more I do, the more familiar it all becomes once again. It is while revisiting Kotlin and Android development that reminded me of how much joy mobile app development used to give me. I mean, sure I can also do the whole full-stacked web API shit. But this is the front-end development aspect that I am referring to. What really excites me about my new job as a front-end developer is that I won't just get to work with Android development, but I will also get to do Swift-related development for the iOS platform. I love this feeling of being able to rediscover the joy it gives me. Can you imagine? I've been doing Android/iOS development since 2012...2013. Wow, that's almost 12 years already. Are you also a mobile app developer or a front-end developer working on a mobile app? What excites you the most about your work? What brings you the most satisfaction? Share with me in the comments. #mobileapps #mobileappdev #recap #refresher #newjob #frontenddevelopers #frontenddevelopment #iOS #android #iosdevelopers #androiddevelopers #swiftprogramming #kotlin #joy #rediscovery

1

*** 99% of Product Managers - What is an API can you explain with a simple example? and you will invariably get the restaurant and butler example - butler is the API and it leaves you no wiser, ask them to give another example and they wouldn’t have any ;) *** First up - most of the literature on internet propagates very narrow definitions of APIs - written probably by product, product marketing and content marketing folks who themselves have never worked a real API. API stands for application programming interface ***notice the word interface a commonality with another popular term UI (user interface). ** Similar to how user interface allows you to interact with physical or digital surfaces, application programming interface allows you to interact with a piece of software/code and allows you to build something using that piece of software. Unclear? Let me give some non restaurant butler physical examples ;) Electricity supply and power socket. If you want to access electricity at home to let's say run an electrical appliance what do you do? You plug into the socket. Here electricity is the base software(in software terminology called a library, framework, software development kit). You are trying to build your own software which in this case is running an electrical appliance and the way you are able to interact with base software is the power socket which is the API. The power socket is the interface which allows you to interact and access electricity (base software). It also forces certain protocols/contract that access is possible using a 3 pin/2 pin plug which is the crux of an API, it enforces a standard way of access. Liked this example? Want to see more examples and different API examples in different software contexts - installed software, browser, internet - see this detailed talk that gives lots of examples, deconstructs myths around current definitions and shows you live demos. https://lnkd.in/gGuCaX8h Follow me at https://lnkd.in/dVGHnkRB AND https://lnkd.in/g7J_sDyN

37

7 Comments

Book Launch Chronicle || Episode 6 We made announcement of this event yesterday and as of 10pm, we had hit 50 signups with mixture of QA Engineers, Product Managers, DevOps, TechOps, Designers and Developers. This is a balance mixture and for those asking me if they can attend, please take this as your invitation. Who should attend this event? Either you are a tech enthusiast or newbie, tech professionals, test and qa professionals, industry leader, people looking to transition from their career into tech, university undergraduates, and those looking to upskill their career. Register 👉bit.ly/fstbooklaunch Software Testing cut across every phase of career and different industries. The book speaks to those who don’t know much about tech or testing, those who are professionals and founders looking to elevate their products. Register 👉bit.ly/fstbooklaunch Yes this event top piority is the book launch but it is doubling as the international software testers day celebration 🍾 hence the touch of owambe vibe 🎊. Register 👉bit.ly/fstbooklaunch To all my industry golden leaders that reviewed and foreworded this book, I want to say a big THANK YOU. Your feedbacks means a lot to me. Register 👉bit.ly/fstbooklaunch Like I would always say, I’m still at the starting point of the software testing sea 🌊, I know there is so much adventure to sail through ahead, and this September 7, 2024 marks the beginning of a new phase for me in my career, business and the software testing industry in Africa. If you haven’t signed up, you still have some time to do so. Register 👉bit.ly/fstbooklaunch Your TestBook Author ❤️ #abcofsoftwaretesting #techowambe #qualityassurance #testing #tech #community

45

***99% of PMs - I learnt all I needed to learn about APIs and I have understood how APIs power products under the hood but what's the point, I don't know what extra value it has added to my life?**** Are you in the same boat? Ok let me explain to you how this knowledge really helps you build better products for your customers Let's say you are a PM at Spotify and let's say Spotify has decided to invest in the creator platform (Musicians, Podcasters, Indie labels) to increase the diversity of content on their platform. Now there are multiple ways you can strengthen the platform for your creators - obviously you can give a nice app/online flow for the creator but what if the creator has been creating content for quite some time and let's say the creators are existing podcasters who already has a catalogue/library of 100s of pieces of content. Do you really want your podcaster to upload all pieces one by one. Now, to solve this - one great way is to build an upload API where the creator can directly upload details - respective media files, their meta data, cover art and description. And you will think of the customer scenarios when designing this API 1. ***First you need to build a way to upload media files to a URL. curl -X PUT "https: //api. spotify. com/upload/creatorid/albumid/file1" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: video/mp4" \ --data-binary "@/path/to/video1.mp4" which probably returns the file ids 2. ***Now the user will need to add meta data for the respective media*** You will build an API to be able to add meta-data for every URL curl -X POST "https: //api. spotify. com/upload/creatorid/albumid/file1" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '[ { "title": "Video 1 Title", "description": "Description for video 1", "tags": ["tag1", "tag2"], "category": "Education", "privacy": "public" }, ... ]' 3. ***Finally, you think getting analytics for the uploaded files later will be an important use case for the creator*** curl -X GET "https: // api. spotify. com/ analytics" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "file_ids": ["file1", "file2", "file3"], "start_date": "2024-01-01", "end_date": "2024-01-31", "metrics": ["plays", "likes", "comments", "watch_time"] }' So you see, APIs are ***intimately linked to customer use cases*** and to build APIs in a way that cater to customer use cases which feels natural is super important. So, like we build UX flows which cater to natural interactions for the user, same is how we build APIs and this is how APIs can be a strong pillar of your product strategy. Follow me for high quality content, not product philosophy but practical insights https://lnkd.in/gHweK_q7 AND also here https://lnkd.in/ggUKftFq My Channel - https://lnkd.in/gs6qnNUJ My Playbook - https://lnkd.in/gHzyN-Xc

6

Your projects are not delivered by the number of resources listed on a spreadsheet… ✅ They are delivered by people... Some still believe that if a project has the right number of developers, everything will be fine… They can happily swap one developer for another… Or better yet, swap out several developers... ❌ With no impact… It doesn’t work like that… Developers are not just code-generating machines, they are people… On your project, they: 👉 Learned about the domain. 👉 Built relationships with the team. 👉 Visualised how your project could be built. 👉 Asked questions and gathered knowledge. 👉 Made the best decisions based on prior conversations. 👉 Gained an understanding of why things are done the way they are. It takes time and effort for new developers to get up to speed with an inflight project… 🧑🏻‍💻 When you swap out developers on a project, your timelines will take a hit… 👩‍💻

9

2 Comments

Data engineers should be particularly attentive to the valuable lessons of TDD. Not only must they create reliable data pipelines but also care for the high quality of those pipelines' outputs. Here are 3 pieces of advice I find helpful: 1) Write data validation tests before writing data cleaning code. 2) A critical data validation test failure should prevent changes in production data. Warning tests should catch rare but valid cases that deserve further investigation. 3) Do it also during data exploration phase. Often, what might initially appear as anomalies could actually be valid edge cases. This presents an excellent opportunity to improve documentation with a better understanding of the data.

8

Does anyone else in the software development industry, particularly testers, BA's and devs, find it frustrating when you try to fill out a web form online and it is unusable, then you decide to let the person or org whose site it is, know, so they don't miss out on communications they clearly built the form in order to receive.... Then after screenshotting and documenting rnough info that their dev team will be able to locate, reproduce and fix the pronlem, suddenly you realise you were doing "me time stuff" but it kinda feels like you were just at work...? Lol... Worse actually, because at work, someone is interested in hearing what you saw and documented. Whereas chances are my email about the impossible to fill out phone number field I just encountered, will probably disappear into a black hole known as "customerservice@..." I just tried to fill out a form, where my phone number was a required field. I tried numerous formats for my phone number, none of which were accepted. Including +6420.... 6420... 020..... 02 .... (020).... And then I even tried a landline number in case for some unknown reason they had decided to only accept landlines (that most of us don't even have any more, lol) and had not put any tips on the form to inform the user of this... various versions of the format of an 03.... number were also rejected. The form was wanting people located in Christchurch NZ to respond in case you are thinking it was rejecting my NZ number because I am not in the US... I dutifully took screenshots and sent the url and a brief email explaining the issue to the contact email for the website. Anyone else ever have this and like to join my vent? 🤣 😂 (No, LI, I don't want to rewrite my vent with AI, though then it might have a (fictional) happy ending 😁)

1

2 Comments