Scan contact card
HIPAA being the business driver, Application Security (AppSec) had to be build into the existing DevOps of an acquired company.
The existing Application Security (AppSec) Program was too disjointed, which resulted in an unclear picture of the security posture of the application portfolio. Plus, the program was too expensive.
MANUS 360 leveraged Percy's highly competent knowledge, skills, and ability to benefit a healthcare client. The organization needed assistance in accounting for information security requirements. Percy was instrumental in assessing the state of the organization but also contributed to a strategy to implement an application security program. We look forward to working with Percy on other engagements in the future.
Strong work ethic, highly skilled, dedicated, deep technical expertise, team work is something that comes to my mind when I think about Percy! He is extremely supportive of the team, makes sure everyone is equipped to get the job done. He leads by example making sure the projects are delivered on time and to the best quality. He is an all round great guy to work with. I highly recommend Percy to anyone who has a potential opportunity to work with!
Percy has helped us tremendously this past year. He implement a range of processes and procedures around our workflows including Tech PM project dashboard, Consultant interest & skills tracking application, he also improved individual performance, cohesion and collaboration within our Tech PM team. I'd like to thank Percy for the strategic leadership he brought to the company, his high level of integrity and his good sense of empathy. I consider him a good friend and wish him all the best in his future endeavors.
See all Testimonials
Dual Major:
If AI keeps getting better at prediction, our biggest risk isn’t hallucinations — it’s sameness. And sycophancy.
In my previous post, I shared how I addressed drift, hallucinations, and context limits when working with AI. Those problems are real, but they’re solvable — and the models are improving.
The harder problem is this: AI is built on everything humans have already done. It can remix the past, but it cannot originate. It will confidently agree with your worst ideas. And it has no stake in whether you succeed or fail.
I’ve been using AI since ChatGPT launched. For quick questions, any model works fine. But when I tried using it for bigger projects — building training programs, complex software, multi-week deliverables — I kept hitting the same three walls:
I got frustrated. Really frustrated. So I did something different.
A friend recently came to me with a common frustration: “The organization has way too many meetings.” If this sounds familiar, you’re not alone. Many professionals find themselves drowning in back-to-back meetings, struggling to keep track of action items, and feeling like their actual work is getting sidelined.
Meetings are essential for collaboration, but they become a problem when they lack structure, clear takeaways, or efficient follow-ups. Simply reducing the number of meetings isn’t always the answer — what’s needed is a smarter way to manage and track them. That’s where AI comes in — not to replace your judgment, but to augment it.
In the ever-evolving landscape of Application Security (AppSec), the term “shift left” has become somewhat of a mantra. This concept implies that the onus of writing secure code is progressively shifting towards software engineers. Consequently, a myriad of AppSec tools are being integrated into the engineers’ build processes, subtly altering the way they construct their code.
But what if we could take a slightly divergent approach to this “shift left” movement? What if we could mitigate its impact on the daily lives of software engineers?
Your number one priority in building a new application? Getting it into the hands of potential customers as fast as possible. Understood, but what are the risks of this practice? Your Application Security (AppSec) is an afterthought, and the risk exposure of your company is unknown. Now, I am not here to judge this approach, but rather applaud you to want to address the issue. This article provides you with a method to determine how much time (=$$) is needed to address potential vulnerabilities in your application.
See all Blogs