👨🏻‍💻 Jonathan Soares’ Post

Tackling Time Zone Differences in Offshore Dev? We've got you covered! Discover 5 key strategies to master time zone management in our latest #blogpost. Enhance communication, boost productivity, and keep your team in sync, wherever they are! Read here: https://lnkd.in/gAFwHkYe #offshoredevelopment #timezonehacks #iconodc #projectmanagement

Saw it, felt it, cried, and cursed as well. It's surprising that even though these best software engineering and IT practices have been around for decades, they are still ignored. Is it wishful thinking, ego, or the belief that one is above the decades of experience and lessons from countless engineers and professionals? I'm doing my best to share what I've learned, but I still encounter people who ignore examples from my life, references to great books, and proven practices, believing they can get away with it. The worst is when those people are juniors or lack comparable experience and competence in the area. I guess sometimes, the best we can do is try to save the sinking ship, but once it's beyond the point of return - jump out. What's your experience? How have you tried to influence and lead best practices in your team and organization?

Working with offshore engineering teams can be a black box. If you don't know what you’re getting, you’ll lose sleep worrying about missed deadlines, quality control, and the communication issues connected with distant time zones. My solution is to resolve your most pressing issues with a North American team as long as your business is situated in NA. If your business is generating revenue, it just makes sense to take care of the big issues locally. Once everything is working smoothly, then we can look at opportunities for cost savings by working with an offshore team. This is why I am against the hybrid model, even though I manage teams on both sides of the globe. They are different tools for different situations. Offshore teams are useful when you’re not experiencing significant tech issues, trying to build a new product in a cost-effective way, and your overall priority is keeping costs down. Local teams are a better choice when rapid communication and swift delivery are your highest priorities. If you'd like to explore the best options for your IT project, reach out and we'll talk. #SubcoDevs #offshoreteam #itprojects #itservices

If I had a dime for every time a development company from another country told me that quality cannot be measured in money… I’d have quite a few dimes… 🤦♂️ Yes, that is correct… the quality we deliver is not magically better because we’re charging more. Our quality is better because I hired the best engineers I could find and those guys cost quite a bit and because of that the cost is higher. Money gives me access to better and more experienced talent. However, there are many important factors in delivering quality software, I’ve eliminated offshore development not because I don’t think there is talent around the world… I’ve eliminated it because having a US development team (especially mostly local) helps with all the others issues (communication, timezone, trust, economical, etc…) Some people get so offended that I promote our “US-based” team… but you know who doesn’t complain? Our clients! Lol 😂 🇺🇸

**Enhancing Software Testing with Clear Bug Documentation** 1. Documentation vs. Communication: Clear documentation complements verbal communication, preventing oversight and disputes. 2. Consequences of Inadequate Documentation: Without records, bugs are forgotten, impacting accountability and product quality. 3. Tracking and Accountability Loss: Poor bug tracking leads to fragmented defect lifecycles, compromising product quality. 4. Real-world Impact: Undocumented bugs risk unresolved issues, affecting user satisfaction. 5. Maintaining Defect Lifecycle: Comprehensive documentation ensures efficient bug tracking and collaboration, enhancing product quality. 6. Building Trust and Transparency: Transparent documentation fosters trust between teams, promoting accountability. 7. Measuring Progress: Documented bugs serve as metrics for tracking progress and prioritizing fixes. In summary, clear bug documentation is crucial for efficient testing, accountability, and superior product outcomes. #SoftwareTesting #BugDocumentation #Efficiency

🛠️🚀 Software Production Release Step by Step Guide 🚀🛠️ 📝 Planning: - Identify the goals and features for the upcoming release. - Prioritize tasks based on importance and dependencies. - Define timelines and allocate resources accordingly. 💻 Development: - Programmers start coding based on the planned features. - Regular code reviews and collaboration to maintain code quality. - Version control systems track changes for better collaboration. 🛠️ Building Artifact: - Compile the source code into executable or deployable artifacts. - Generate documentation and other necessary files. - Automation tools can be used to streamline this process. 🧪 Testing: - Conduct various levels of testing (unit, integration, system, etc.). - Identify and fix bugs or issues. - Ensure compatibility with different platforms and configurations. 🌐 Environments: - Set up different environments for development, testing, and production. - Ensure consistency across environments to minimize deployment issues. - Monitor and troubleshoot any discrepancies between environments. 🚀 Release: - Once testing is successful, prepare for the release. - Generate release notes documenting changes and updates. - Coordinate with other teams for a smooth rollout. #SoftwareDevelopment #ReleaseManagement

A day in developer life. Start a day with morning slogan : Development is my passion 😀 8AM to 9AM - Daily status meeting 9 AM to 10 AM meeting with the backend team. 10 AM to 12 PM - Technical doubt clarification meetings for devs. Development is my passion 😀 01 PM to 2 PM- Report preparation for the manager. 2 PM to 3 PM - Design review meeting or other meeting etc. 3 PM to 4 PM - Daily status to onshore management. 4 PM - 5 PM - Daily status for managers not even in the project or in the company 😀 Development is my passion 😀 yes, 5 PM !!!! My shift is complete. Oh no !!! I didn't get time for development. 5PM - 8 PM working in stories. 8 PM to 9 PM Status meeting by offshore management. Development is my passion 😀 9 PM to 10 PM dev sync. 10 PM to 11 PM - Checking that anybody else needs a status report. More supervision, more productivity in creating status. Report creation is my passion 😌

Things that some developers and managers believe to be impossible, but I KNOW from experience to be perfectly achievable (in actual commercial projects): - 100% test coverage - Linear commit history - Actual Continuous Integration (everyone merges daily)

Test plans are the architectural blueprints of successful testing endeavors, and understanding their attributes is the key to seamless project execution. Let's unravel the intricacies together: 🔍 Scope: Define the boundaries of your testing, outlining what will and won't be covered to ensure comprehensive coverage. 🛠️ Approach: Craft a strategic approach detailing how testing will be conducted, aligning it with project goals and objectives. 👥 Roles & Responsibilities: Clearly define the responsibilities of each team member, fostering collaboration and accountability. 📅 Schedule: Establish a realistic and well-structured timeline, ensuring that testing aligns with project milestones. 🚧 Risks: Identify potential risks and develop mitigation strategies, ensuring a proactive approach to challenges. 🌐 Test Environment: Specify the required testing environment, including hardware, software, and configurations. 📈 Entry and Exit Criteria: Clearly define the conditions for entering and exiting each testing phase, maintaining process consistency. 📦 Test Deliverables: Enumerate the expected outputs from each testing phase, providing a tangible measure of progress. Which test plan attribute do you find most crucial in your projects? Share your thoughts below! 👇 #SoftwareTesting #QualityAssurance #TestPlans #QACommunity #TestManagement #AgileTesting #SoftwareDevelopment #CodeQuality

How companies deliver code to production...... 1️⃣ Initiation begins with a product owner crafting user stories based on requirements. 2️⃣ The development team incorporates these user stories from the backlog into a two-week sprint. 3️⃣ Developers commit their source code into the Git code repository. 4️⃣ Jenkins triggers a build, subjecting the source code to rigorous checks like unit tests, code coverage thresholds, and SonarQube gates. 5️⃣ Upon a successful build, it is stored in Artifactory and deployed into the development environment. 6️⃣ Multiple development teams might be involved, with each feature independently tested by deploying to QA1 and QA2. 7️⃣ QA teams take charge of the new QA environments, conducting thorough testing encompassing QA, regression, and performance. 8️⃣ Successful QA builds move to the UAT environment. 9️⃣ Upon successful UAT testing, the builds transition into release candidates, poised for deployment to the production environment as per the schedule. The Site Reliability Engineering (SRE) team takes over, ensuring vigilant monitoring of the production environment.