Cybercriminals are getting creative—using AI, social engineering, and “vibe-coded” online culture to launch new types of scams and attacks. This episode explores the strange but serious ways fraudsters operate today, and what IT professionals can do to keep ahead of the curve.

The future of IT isn't just about code—it's about the intersection of cutting-edge fields. This episode dives into the exciting career paths emerging from the fusion of artificial intelligence, design thinking, and cybersecurity. We'll explore how these disciplines are creating new roles and opportunities, from designing secure AI systems to building user-friendly security tools. Join us to learn how to prepare for the jobs of tomorrow by bridging the gap between these powerful fields.

From theory to practice—how tomorrow’s defenders are forged today.

From the lecture hall to the SOC (Security Operations Center), how do students become front-line defenders of the digital world? This episode looks at the journey from learning the fundamentals of cybersecurity in school to applying them in real-world threats. Guests share their experiences, challenges, and tips for anyone aspiring to enter cybersecurity.

The good side of hacking—and why we need more of it.

Hacking isn’t always a bad thing. This episode dives into the world of ethical hacking, where professionals deliberately exploit systems to identify vulnerabilities before malicious actors can. We’ll discuss the skills required to succeed in this field, how ethical hackers work with organizations, and why understanding your system’s weaknesses is one of the best ways to protect it from real-world threats.

On this episode, we have Jason Torres, Miguel Fermin, and Rafael Quisumbing joining us to discuss "Global Exposure" and the differences between working here in the Philippines and abroad.

The tech world has gone borderless, creating new career paths and challenges. This episode explores the key differences and opportunities of working for a company in the Philippines versus a global or international one. Our guests will share insights on cultural nuances, salary and benefits, work-life balance, and career growth trajectories in both local and international settings. We'll provide practical advice for IT professionals looking to expand their horizons, whether by working remotely for a foreign company or pursuing a career abroad.

What are some of the biggest cultural or professional differences you’ve observed between working for a local company and a global one? (Generalization)

One of the biggest differences is the approach to communication and hierarchy. Local companies may have a more structured, hierarchical communication style, while global companies often favor a more flat and direct approach. There are also differences in professional pace; global teams often operate with a greater sense of urgency due to time zone differences and tight international deadlines. Lastly, a diverse global team exposes you to different work ethics and perspectives, fostering a more adaptable and inclusive professional mindset.

How do compensation, benefits, and work-life balance typically compare when you’re working for a company based in another country? (Generalization)

Compensation and benefits are generally higher with global companies, especially those based in developed countries. This can include better salaries, more comprehensive health benefits, and clearer opportunities for bonuses or equity. However, the work-life balance can vary. While some global companies promote flexibility, the demands of working across different time zones might extend your work hours. It is also worth noting that benefits like paid time off and holidays may align with the company's home country, not the employee's, which can be a point of adjustment.

What are the biggest challenges or hurdles to getting a job with a global company or pursuing a career abroad? (Generalization)

One of the biggest hurdles is visa sponsorship and work permits, which can be a complex and lengthy process. For remote roles, competition is fierce, and showcasing your skills and experience to a global audience is key. You might also face the challenge of proving that your local experience and credentials are on par with international standards. Additionally, the initial adjustment to a new work culture, especially in terms of communication norms and professional expectations, can be a significant hurdle to overcome.

What’s one piece of advice you’d give to someone working in the Philippines who wants to gain more global exposure? (Generalization)

The best advice is to start building a global brand for yourself right now. This means actively contributing to open-source projects, participating in international tech communities online, and building a professional portfolio that is accessible to anyone, anywhere. Focus on gaining highly sought-after skills like cloud computing, AI, or cybersecurity. By demonstrating your expertise on a global stage, you can attract opportunities without even having to leave your current location.

On this episode, we have Raphael Quisumbing, Miguel Fermin, and Jason Tores joining us to discuss the world of startup equity and exits.

For anyone working at or dreaming of joining a startup, understanding equity is crucial. This episode demystifies the world of stock options, vesting schedules, and company valuation. Our guests will break down how startup equity works, the key terms you need to know, and what happens during a successful exit, whether through an acquisition or an IPO. We'll share practical advice on how to navigate compensation conversations and maximize the value of your stake in a growing company.

What are the fundamental types of equity an employee can receive, and what’s the difference between them? (Generalization)

The two most common types are stock options and restricted stock units (RSUs). With stock options, you get the right to buy a certain number of shares at a predetermined price, called the strike price, after a vesting period. RSUs, on the other hand, are a grant of actual shares that are given to you once they vest. The key difference is that with options, you have to pay to acquire the stock, while with RSUs, the stock is simply given to you.

What is a vesting schedule, and why is it so important for employees to understand? (Generalization)

A vesting schedule is the timeline that determines when an employee gets ownership of their equity. It's usually a four-year schedule with a one-year cliff, meaning you have to work for at least a year before you get any of the equity. After that, the rest of the equity typically vests in monthly increments. Understanding your vesting schedule is crucial because it dictates when your equity is truly yours, and it heavily influences decisions like when to leave a company or whether to exercise your stock options.

How do mergers, acquisitions, and IPOs impact employee equity? (Generalization)

In a merger or acquisition, employee equity is typically cashed out or converted into shares of the acquiring company. The terms of the deal can vary, so it's essential to understand the specific agreement. In an Initial Public Offering (IPO), the company's shares become available on the public stock market. This allows employees to sell their vested shares for cash, subject to a lock-up period that prevents an immediate sell-off. Both events represent the primary ways for employees to realize the financial value of their equity.

What are some key questions employees should ask about equity during a job negotiation? (Generalization)

When negotiating for equity, you should always ask about the type of equity being offered (e.g., options or RSUs). It’s also crucial to understand the vesting schedule and any performance-based conditions. Inquire about the company's latest valuation and the total number of shares outstanding, as this helps you calculate the actual percentage of the company your equity represents. Finally, ask about the company’s path to an exit (e.g., IPO or acquisition) and any policies regarding exercising your options if you leave the company.

Why writing maintainable code is a career skill, not a coding style.

On this episode, we have Alex, Christopher Bryan, Charles Mejica Madronero, and Edd Alc joining us to discuss clean code and why writing maintainable code is a career skill, not just a coding style.

Clean code isn’t about perfection—it’s about clarity, maintainability, and collaboration. In this episode, we talk to developers who prioritize writing code that other people (including their future selves) can read, debug, and scale. We’ll unpack why clean code matters beyond job interviews, how it impacts teams and long-term projects, and the habits that separate average coders from great ones over time.

What’s your personal definition of clean code? (Generalization)

My personal definition of clean code is code that is easy to read, easy to understand, and easy to change. It’s code that tells a story, so that another developer can look at it and immediately grasp its purpose without excessive comments. It’s also code that has a clear structure and organization, making it predictable and simple to navigate. Essentially, it's code that prioritizes the human reader over the machine.

Have you ever had to clean up someone else’s messy codebase? What was that like? (Generalization)

Absolutely. Cleaning up a messy codebase is a common rite of passage for many developers. It can be a very challenging and frustrating experience, much like trying to untangle a massive knot of string. The process often involves a lot of detective work to understand the original intent of the code, and a significant amount of time spent on refactoring and writing tests to ensure changes don't break existing functionality. While difficult, it's also a powerful learning experience that highlights the importance of good code hygiene.

What small habits help you write cleaner, more maintainable code every day? (Generalization)

A few small habits make a big difference. I always aim to use descriptive variable and function names so their purpose is immediately clear. I also try to keep functions small and focused on a single task, following the Single Responsibility Principle. Additionally, I’m a firm believer in automated testing; a good suite of tests acts as a safety net that allows me to refactor and improve code confidently without fear of introducing new bugs.

Is there ever a time when writing clean code is not the priority? (Generalization)

Yes, there are rare situations where clean code is not the top priority. This most often happens in a crisis or emergency, such as when a critical system is down and needs to be fixed immediately. In such cases, the priority is to get the system working again as quickly as possible. Similarly, during a rapid prototyping or proof-of-concept phase, a developer might prioritize speed and functionality to validate an idea. However, in these situations, it's crucial to acknowledge the "mess" and plan to refactor it later to avoid long-term technical debt.

Are developers being replaced—or just evolving?

On this episode, we have Alex, Christopher Bryan, Charles Mejica Madronero, and Edd Alc joining us to discuss the rise of low-code, no-code, and AI-generated code and explore who's building what now.

The rise of low-code, no-code, and AI-generated code is changing who gets to build software—and how fast it gets built. This episode explores what these tools mean for traditional developers, citizen developers, and tech teams as a whole. We’ll talk about opportunities, limitations, and whether this shift is empowering or threatening the future of software engineering as we know it.

What are the biggest misconceptions about low-code and no-code platforms? (Generalization)

One of the biggest misconceptions is that these tools are only for simple websites or prototypes. In reality, modern low-code platforms are powerful enough to build complex, enterprise-level applications with custom logic. Another misconception is that they will completely replace developers. Instead, they are better seen as tools that automate repetitive tasks, freeing up developers to focus on more challenging architectural problems, integrations, and unique features.

Can someone build a real career using only these tools? (Generalization)

Yes, a person can build a real and valuable career as a "citizen developer" or "low-code engineer." However, this career often looks different from a traditional software engineering path. Success depends on a deep understanding of business processes, problem-solving, and data integration. Professionals who master these tools can become highly valuable by rapidly delivering solutions and bridging the gap between business needs and technical implementation.

How should developers respond to the rise of AI-generated code? (Generalization)

Developers should respond to AI-generated code not with fear, but by embracing it as a new and powerful tool. AI will likely handle more boilerplate and repetitive coding tasks, allowing developers to focus on higher-level design, complex logic, and architectural challenges. The role of a developer is shifting to one of a technical leader who can write, debug, and critically evaluate the code AI produces, ensuring it's robust, secure, and fits within the larger system.

What kinds of projects are a good fit for low-code solutions—and which aren’t? (Generalization)

Low-code solutions are an excellent fit for projects with well-defined business logic and standard requirements, such as internal tools, customer portals, or simple mobile apps. They are ideal when speed and rapid iteration are the top priorities. They are generally not a good fit for projects that require highly custom, performance-critical, or complex algorithms, such as high-frequency trading platforms, graphics engines, or specialized machine learning models that demand fine-grained control over the code.