What We Think
February 12, 2026
As infrastructure scales, DevOps engineers often face the challenge of maintaining multiple container environments. Logging into individual servers via SSH to check container health is inefficient and error-prone. To solve this, you need a robust solution to manage remote Docker with Portainer.
February 12, 2026
In modern digital content platforms, many systems rely on techniques like Non-Negative Matrix Factorization (NMF) to power their recommendations. At the same time, users are often overwhelmed by a large number of choices. Consequently, most people now prefer scrolling through recommended lists. Instead of actively searching for new content, they simply pick something that catches their eye. As a result, the quality of these recommendations plays a key role in shaping the user experience on the platform.
February 12, 2026
When working with languages like JavaScript, Java, C#, Python, and many others, you will always encounter two fundamental concepts: Value Types and Reference Types. They may sound a bit technical, but they simply describe how data is stored in memory and how it behaves when assigned to variables or passed to functions.
let a = 10;
let b = a; // b receives a copy
a = 20;
console.log(a); // 20
console.log(b); // 10
let obj1 = { name: "David" };
let obj2 = obj1; // both point to the same object
obj1.name = "Alex";
console.log(obj1.name); // Alex
console.log(obj2.name); // Alex
| Feature | Value Type | Reference Type |
|---|---|---|
| Stored in | Stack | Heap (reference on stack) |
| What is stored | Actual value | Address pointing to data |
| Assignment behavior | Copies the value | Copies the reference |
| Independence between variables | Yes | No |
| Examples | int, float, bool | object, array, class |
let obj1 = { name: "Dũng", info: { age: 30 }};
let obj2 = structuredClone(obj1);
obj1.info.age = 31;
console.log(obj2.info.age); // 30 (independent)
February 12, 2026
Artificial Intelligence (AI) is no longer a futuristic concept; it is rapidly transforming the IT industry. From assisting developers in writing code to analyzing massive datasets, AI has become an integral part of the Software Development Life Cycle (SDLC).
This rapid evolution raises an important question—especially for Quality Control (QC) professionals:
Will AI replace us? To answer this, we must look beyond the hype and understand the synergy between human intuition and machine efficiency.
To understand AI’s impact, we must first redefine what QC actually does. Many believe QC is just about "finding bugs." In reality, even at a junior level, a QC professional is a guardian of quality throughout the SDLC by:
AI excels in tasks that require high-speed processing and repetitive workflows. It doesn’t get tired, and it doesn’t lose focus.
While AI is powerful, it lacks the "human touch" required for high-level quality assurance. There are dimensions of testing that code simply cannot reach:
QC professionals can think like real users, question unclear requirements, and notice subtle issues that don’t “feel right.” This human perspective is something AI cannot replicate.
AI isn’t taking your job; it’s upgrading your role. As a Junior QC, you can leverage AI to accelerate your growth:
Example: When testing a Login feature, let AI suggest the standard cases. You then focus your energy on the complex security redirects or specific localized business rules.
The repetitive parts of testing may be automated, but the Quality Engineer will always be needed. To stay ahead:
This article was inspired by and references insights from:
Will AI Replace Software Testers? — GeeksforGeeks
Ready to elevate your software quality with the perfect blend of AI efficiency and human expertise? Our team is here to help.
Contact Our Experts TodayFebruary 12, 2026
In the era of accelerated development, integrating generative AI tools like Google Gemini and GitHub Copilot into our workflow is becoming essential for boosting productivity. However, adopting these tools in client projects, especially in offshore development settings, requires overcoming a critical hurdle: client approval.
The Comtor (Communication Translator) plays a vital role in this process, translating not just language, but also technical necessity into business value that addresses client security and cultural concerns.
Here are specific examples of dialogues a Comtor can use to secure AI tool usage permission.
Before introducing the solution, the Comtor must first acknowledge the client's perspective, especially their concerns regarding data security, code ownership, and compliance.
Comtor Dialogue:
“We understand that utilizing new AI tools like Gemini/Copilot raises concerns regarding code ownership and data confidentiality. Can you please specify your current security policy regarding the use of external generative AI, and what level of control you require over the data being processed?"
The Comtor must shift the focus from "using an AI tool" to "achieving required quality and efficiency." The focus should be on how AI helps solve existing project challenges.
Comtor Dialog:
"Our current project requires extensive unit testing, which is increasing our manual effort. By using Copilot for generating unit test cases, we anticipate a 20% reduction in coding time while ensuring higher test coverage. This allows us to allocate more resources to complex logic.”
"To mitigate security risks, we propose using the Enterprise version of Gemini/Copilot, which guarantees that our proprietary code is not used for training the model. We can also establish an SLA for data handling."
Once the client is receptive, the Comtor must define the precise scope and establish governance rules, aligning with the project's minimum visibility level.
Comtor Dialog:
"Initially, we only seek permission to apply AI to the Coding and Unit Test phases. We will start by restricting usage to non-critical modules and will document every instance of AI-generated code."
"We will share a regular report on AI usage, detailing the time saved and any code review findings related to AI-generated snippets, aligning with our agreed minimum visibility level. After three sprints, we can review the results and decide on expansion."
A Comtor's success in gaining AI tool approval hinges on replacing fear with assurance. By being proactive in addressing security, quantifying the efficiency gains, and providing clear governance structures, the Comtor transforms the request from a risk to a strategic productivity gain for the project.
Whether you need scalable software solutions, expert IT outsourcing, or a long-term development partner, ISB Vietnam is here to deliver. Let’s build something great together—reach out to us today. Or click here to explore more ISB Vietnam's case studies.
Refer
https://unsplash.com/s/photos
February 12, 2026
In the Java ecosystem, dealing with Microsoft Office documents is a ubiquitous requirement. Whether you are generating financial reports, exporting data grids, or parsing user uploads, Apache POI is the de facto standard library for the job.
February 11, 2026
As global companies scale their technology teams, software delivery increasingly happens across borders, cultures, and time zones. While this creates opportunities for speed and cost efficiency, it also introduces a less visible challenge: cross-cultural communication.
In the first episode of the ISB Vietnam Podcast, hosts Nikki Skovmose Business Development Rep and Peter Ratcliff, International Sales Manager, explore how cultural differences between East and West shape the way software teams communicate, make decisions, and deliver results.
Rather than focusing on theory, the discussion is grounded in practical lessons from real-life experience, drawn from hosts Nikki and Peter’s combined decades of work with international clients and distributed engineering teams.
For founders and CTOs considering offshore development but unsure where to start, this episode offers a practical, experience-based view on how to reduce risk, improve collaboration, and turn outsourcing into a long-term competitive advantage.
🎧 Watch the full episode on our YouTube channel:
👉 https://www.youtube.com/watch?v=0DjOawhwKOchttps://
More episodes are coming soon, covering leadership, delivery, and real-world experiences of building software across cultures - recorded from the heart of Vietnam, Ho Chi Minh City, where ISB Vietnam is headquartered.
January 6, 2026
If you are a developer or a technical writer, you know the pain of creating sequence diagrams. You open a GUI tool like Visio or Lucidchart, drag a box, drag another box, draw a line, realize the line isn't straight, adjust the line, and then realize you need to move everything to the right to fit a new actor.
It’s tedious. It’s hard to version control. It feels like drawing, not engineering.
Enter Mermaid.js. Mermaid allows you to create diagrams using text and code. It renders Markdown-like syntax into beautiful, professional diagrams. In this guide, we will master the art of writing Sequence Diagrams as code.
Mermaid is a JavaScript-based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.
Diagrams as Code: You store your diagrams in your Git repository as .md files.
Version Control: You can see diffs in your diagrams just like you see changes in your code.
Speed: No more pixel-pushing. You focus on the logic; Mermaid handles the layout.
Integration: Supported natively by GitHub, GitLab, Notion, Obsidian, and VS Code.
To create a sequence diagram in a Markdown file, you use a code block with the mermaid identifier.
Let's start with the absolute basics: Alice talking to Bob.
sequenceDiagram
Alice->>Bob: Hello Bob, how are you?
Bob-->>Alice: I am good, thanks!The Output: The code above tells Mermaid to draw two participants. The ->> represents a solid arrow (request), and -->> represents a dotted arrow (response).
By default, Mermaid creates participants in the order they appear. However, for complex diagrams, you often want to define them explicitly to control the order or use aliases.
participant: Renders as a rectangle (default).
actor: Renders as a stick figure.
as: Allows you to use short aliases in your code.
sequenceDiagram
actor U as User
participant FE as Frontend
participant API as Backend API
participant DB as Database
U->>FE: Clicks button
FE->>API: GET /users
API->>DB: Select * from usersThe Output: Notice how we used U, FE, and API in the code, but the diagram renders the full names.
In a real system, a service takes time to process a request. We visualize this using "activation bars" (the vertical rectangles on the lifeline).
Long way: activate Alice / deactivate Alice
Short way (Recommended): Add + to the end of the arrow to activate, and - to deactivate.
sequenceDiagram
participant Client
participant Server
participant DB
Client->>+Server: Request Data
Note right of Server: Server is processing...
Server->>+DB: Query Data
DB-->>-Server: Return Results
Server-->>-Client: 200 OKThe Output: The grey bars indicate that the Server and Database are "busy" processing the request. This is crucial for analyzing performance bottlenecks.
Software isn't linear; it has loops and if/else conditions. Mermaid handles this with loop, alt (alternative), and opt (optional).
This is used to show mutually exclusive paths, such as a successful login vs. a failed login.
sequenceDiagram
actor User
participant Auth as Auth Service
User->>Auth: Submit Credentials
alt Credentials Valid
Auth-->>User: Return Token (200 OK)
else Credentials Invalid
Auth-->>User: Return Error (401 Unauthorized)
end
Used for repeated actions, such as polling or retries.
sequenceDiagram
participant Client
participant Server
loop Every 5 seconds
Client->>Server: Health Check
Server-->>Client: Healthy
endThe Output (Complex Logic): Here is a visualization of how these logical blocks appear in a rendered diagram.
Use Notes: You can add notes to clarify specific steps using Note right of [Actor] or Note over [Actor1],[Actor2].
Keep it Simple: If your sequence diagram is getting too wide or too long, consider breaking it into two separate diagrams.
Use the Live Editor: When learning, use the Mermaid Live Editor. It gives you instant feedback as you type.
Switching to "Diagrams as Code" with Mermaid is a game-changer for developer productivity. It keeps your documentation close to your code, makes updates trivial, and ensures your diagrams always look consistent.
Next time you need to document an API flow, close Visio and open your Markdown editor. Your future self (and your team) will thank you.
Ready to get started?
Contact IVC for a free consultation and discover how we can help your business grow online.
January 6, 2026
Mendix is an enterprise Low-Code application development platform (owned by Siemens).
This platform allows organizations to build, deploy, and manage software applications rapidly without the need for extensive manual coding.
Key Highlights: Accelerates software development, integrates AI (via the Mendix AI assistant - MAIA), easily integrates with other systems (such as SAP, AWS), and supports comprehensive digital transformation.
Goal: To help companies modernize legacy systems, automate processes, and create new digital experiences for customers.
Many major global corporations across various sectors (Finance, Manufacturing, Logistics, Healthcare, etc.) are using Mendix to solve specific challenges:
Siemens Energy: Used Mendix to scale from 4,000 to 40,000 internal users. They developed over 200 apps to drive innovation and increase workflow efficiency globally.
Zurich Insurance: Uses Mendix to simplify business processes and support business strategy through rapid app development, serving customers better.
Glico (Food & Confectionery): Applied in Smart Manufacturing and their digital transformation journey to manage production processes more effectively.
WADA (World Anti-Doping Agency): Uses it to deliver software faster, helping manage athlete data and keep sports clean.
Jabil (Manufacturing): Deployed over 100 apps to improve global factory operations and promote high customization in manufacturing.
HTM (Public Transport): Achieved 60% faster application development speeds, improving employee efficiency and transport system management.
Not every software project should use Mendix. It is best suited when:
Urgent/Time-critical: Applications need to be completed in weeks rather than months.
Frequent Changes: Business processes change constantly; apps need rapid modification without crashing the system.
Internal Digital Transformation: Custom-built ERP/CRM systems, employee portals, warehouse management, and supply chain management apps.
Legacy Modernization: Replacing outdated software (like Lotus Notes, FoxPro) with modern web interfaces.
These are employees who understand business processes (HR, Accounting, Logistics...) but do not have deep programming knowledge.
Why it fits:
Drag & Drop Interface: Mendix provides "Mendix Studio" on the web. Users can drag and drop buttons, forms, and design workflows using visual diagrams without writing a single line of code.
Solving the "Excel" Pain: Suitable for those managing data with dozens of disjointed Excel files who want to turn them into a centralized, secure management app.
Rapid Prototyping: Business users can visualize app ideas to present to IT teams or leadership.
Those who already know Java, JavaScript, CSS, SQL...
Why it fits:
Eliminating Tedious Work: Mendix automates repetitive tasks like database setup, basic security, or UI/UX design. Developers can focus on complex logic.
Extensibility: Unlike closed "No-code" tools, Mendix allows developers to write code (Java actions, JavaScript widgets) to handle complex requirements that drag-and-drop tools cannot.
System Integration: Excellent support for connecting APIs (REST, SOAP, OData) and integrating with major systems like SAP, Salesforce, and AWS rapidly.
Source: https://www.mendix.com/
January 6, 2026
Plan Mode was introduced by Cursor in October 2025. Plan Mode assists AI Agents in executing Complex Projects and long-term tasks by providing clear Context and Direction right from the start. In other words, Plan mode sets up a plan before execution in Cursor AI.
I have a plan to change language from English to Vietnamese in my demo project.
Start planning by pressing Shift + Tab in the agent input.
" change language from English to Vietnamese"
Cursor will ask you a few questions to Clarify your Requirements .
you only select the Answer and click Continue
Cursor will create a detailed plan (Markdown file)
It lets you review/edit the plan like a design document.
Then click to Build the plan when ready.
You can Review the results once more before applying them
As you can see, Plan Mode will be very useful when you have the following needs:
Whether you need scalable software solutions, expert IT outsourcing, or a long-term development partner, ISB Vietnam is here to deliver. Let’s build something great together—reach out to us today. Or click here to explore more ISB Vietnam's case studies.
More Cursor AI