Crazy Little I.T. Girl

Crazy Little I.T. Girl Contact information, map and directions, contact form, opening hours, services, ratings, photos, videos and announcements from Crazy Little I.T. Girl, Information Technology Company, Panabo.

Sharing IT insights with fun, sunshine, and hope! ☀️ From SQL tricks to System Design wisdom, I’m here to uplift and inspire IT students and pros. 💻 Because behind every bug and deadline, there’s always room for laughter and growth. 💡✨

Sometimes, it’s the smallest questions in a system that reveal the biggest problems.This photo may look funny at first, ...
15/04/2026

Sometimes, it’s the smallest questions in a system that reveal the biggest problems.

This photo may look funny at first, but it quietly highlights something serious. A system asking, “Have you ever been in an accident that resulted in your death?” and allowing a “Yes” response shows a gap not just in logic, but in analysis. 🥺

This is exactly why Systems Analysis and Design matters. 😌

Before any code is written, someone has to ask the right questions, understand real-world scenarios, and anticipate how users will interact with the system. That responsibility often falls on the Systems Analyst.

A Systems Analyst does not just document requirements. We help shape the direction of the system. We translate real-world needs into something clear and meaningful, so that what gets built is not only functional, but also logical and aligned with reality. We also take part in reengineering, improving existing systems, refining processes, and making sure that what already exists continues to evolve and make sense.

In many cases, we also write code. We build, test, and support the system alongside programmers. But beyond coding, our role is to make sure that what is being built, or even rebuilt, actually makes sense in the first place.

I’ve come to realize that systems development is not about one role being more important than another. It is a shared effort. Some focus deeply on coding, while others carry a broader view that connects users, processes, and technology. Both are necessary.

Sometimes, the work of a Systems Analyst is not always seen. But it is present in every system that works the way it should, especially in the parts that quietly prevent errors like this.

Because in the end, good systems are not just coded. They are carefully understood, improved, and reengineered over time. 😌

📸 ctto Petiks 🤍🫶🏻

15/04/2026

If DEBUGGING is the process of removing software bugs, then PROGRAMMING must be the process of putting them in? 🤔😌

With Programmer Ako – I'm on a streak! I've been a top fan for 8 months in a row. 🎉
23/03/2026

With Programmer Ako – I'm on a streak! I've been a top fan for 8 months in a row. 🎉

23/03/2026

There are moments in our lives when we are confronted with situations that test not only our competence, but also our character.

Sometimes we do everything we can. We raise concerns early, offer possible solutions, follow up when needed, and trust that the people entrusted with certain responsibilities will act on them. We believe in the process. We believe in teamwork. We believe in leadership.

Yet there are times when things go wrong and the narrative becomes unclear. Questions arise, accountability is sought, and in the middle of it all, someone may quietly carry the weight of being misunderstood or wrongly perceived. Being associated with something you know in your heart you tried to prevent is a painful place to be.

In moments like this, I am reminded of a few important lessons.

True accountability begins with self-awareness. Before pointing fingers, it is important to look inward and honestly ask whether we fulfilled the role entrusted to us. Root cause analysis is not simply about identifying where a problem surfaced, but understanding where it truly began and what actions, or lack of actions, contributed to it.

Leadership is not only about authority or position. It is about the courage to take responsibility, the humility to acknowledge oversight, and the integrity to protect the people who did their part with genuine effort and good intention.

Another difficult realization is seeing how people sometimes behave differently when situations involve authority or pressure. Words spoken in private may not always be reflected the same way in public. For someone who has extended trust, support, and understanding to others, it can be painful to realize that the same honesty or courage may not always be returned when the moment calls for it.

Moments like this quietly teach us about loyalty and integrity. They remind us that true character is revealed not when things are comfortable, but when it becomes difficult to stand by the truth.

Still, I choose to believe that sincerity, diligence, and integrity are never wasted. Even when misunderstood, genuine effort carries its own quiet strength.

In the end, problems may pass, discussions may fade, but the way we handled the truth, the way we treated others, and the integrity we kept will always speak for themselves.

Good night. 😌💔🙏🏻

04/02/2026

ERP vs. In-House Developed Information Systems: Which Is Better?

As I teach IT Audit and Controls this semester, one recurring question emerges during our discussions about ERP systems:

Is an ERP always the best solution, or can a customized, in-house developed system be the better choice? 🤔

From an audit and governance perspective, ERP systems offer well-known advantages. They provide integrated modules across finance, HR, procurement, and operations. They enforce standardized workflows, support segregation of duties, and maintain consistent audit trails. For large and process-driven organizations, these built-in controls significantly reduce control gaps and manual interventions.

From a development and operations standpoint, however, the reality on the ground is often more complex. 🥹

ERP implementations can be costly, time-intensive, and rigid. Business processes frequently need to adjust to the system rather than the system adapting to the business. Users may struggle with workflows that do not fully reflect how work is actually done, which can introduce workarounds and weaken intended controls.

This is where customized, in-house developed information systems present a compelling alternative.

In-house systems allow developers to design solutions that mirror actual business processes. Enhancements can be implemented faster, user feedback can be addressed directly, and system logic can evolve alongside organizational needs. When appropriately implemented, in-house systems can strengthen controls by embedding validations, approval workflows, and access restrictions aligned with institutional policies.

However, from an audit perspective, customization introduces its own risks. These include reliance on key technical personnel, insufficient documentation, weak change management, and limited segregation of duties if governance is not intentionally designed. Without strong controls, even a technically sound system can become a long-term risk.

So, which is better? 🤔

From both an auditor’s and a developer’s lens, the answer is not ERP versus in-house development. The answer is alignment. 😌

The most effective system is one that balances functionality, control, sustainability, and real operational needs. Whether ERP-based or custom-built, success depends on how well the system is governed, documented, secured, and understood by both its users and its builders. 🥹

In your organization, are your systems driving your processes, or are your processes driving your systems and controls? 🤔

P.S. I love brainstorming ideas with my students. Some of them have realistic POVs, some have very colorful imaginations, some are zoning out during class. 🥹🤍🫶🏻🤭

27/01/2026

When you’re a basketball enthusiast, an IT practitioner, and a part-time college instructor…

Students: Ma’am, mahirap po bah ang capstone? Makakagraduate kaya kami? 🥹🤔

Me: Kung makakagraduate bah kayo, wag nyo muna yan e overthink kasi medyo matagal pa yon. Also, baka hindi din kayo papasa sa subject natin ngayon. 🥹😌 Pero kung mahirap bah ang capstone? 🤔 Ang capstone kasi class para din yang basketball…in order for you to win it you need teamwork, good communication, and defense. 🥹😌

Students: 🤔😳😱😯

Me: Of course you will be working as a team, a united team with the same goals which is to graduate, and in order for you to be united you need to have good communication. If there’s no communication there’s no relationship, and if you don’t have good communication with your teammates there will be no teamwork and your team will definitely not work. And of course, by the end of the day, you need to defend your capstone project, both the system and your document. That’s why you need to have a solid defense.

Students: 🥹😳😱😮😲😯

Me: 😁😅🥹

18/01/2026

Margaret Hamilton wrote the software that ran the Apollo missions.
Not paperwork.
Not notes.
The actual code keeping astronauts alive.

When computer errors hit mid-flight, her software automatically dropped non-essential tasks and prevented a crash.
No hero speeches.
No last-second miracles.
Just preparation doing its job.

Men walked on the Moon and became legends.
Photos were taken.
Awards were handed out.

Margaret got a footnote —
even though her work decided whether the mission failed or everyone came home alive.

Space history loves brave men.
It quietly ignores the woman who made bravery survivable.

Yong binibenta ka na ng mga kaibigan mo kasi daw ang love life mo naka–Error 404: Not Found. Pero beh… yong nireto nilan...
10/01/2026

Yong binibenta ka na ng mga kaibigan mo kasi daw ang love life mo naka–Error 404: Not Found. Pero beh… yong nireto nilang web developer sayo parang may syntax error. Kaya ang ending, napasabi ka na lang talaga, “Oooh ok. Uhmn yeah cool.” 🥹😭🥲

P.S. Archived from 3 years ago…please don’t judge. 🥹

10/01/2026

❌ Programmer ako.
✅ Programmer ako.

Only bisaya programmers know. Ayyiieee! 🤭

The saddest part of a failed system is not the bugs. It’s a broken team.Disclaimer: This post is not meant to attack, sh...
08/01/2026

The saddest part of a failed system is not the bugs. It’s a broken team.

Disclaimer: This post is not meant to attack, shame, or single out anyone. This is not about pointing fingers or reopening wounds. This is a hopeful reflection, written with the intention of sharing lessons, encouraging growth, and helping students and future professionals learn something valuable from real experiences. 😌

Earlier today, I witnessed something heavy during a capstone defense. A student cried. He was the programmer of their team. And it made me pause and reflect, not in anger, but in concern and hope. 😌

In a development team, being a programmer is an important role, but the project's strength still comes from collaboration and shared responsibility.

Programming is critical, yes. But a capstone project is not just about writing code. It is about building a system, solving a problem, and learning how to work as a team.

“HINDI PORKET IKAW ANG PROGRAMMER, IKAW NA LANG ANG MAHALAGA. HINDI PORKET HINDI IKAW ANG PROGRAMMER, HINDI KA NA MAHALAGA.” 😌

In the industry, you will work with people who do not code. Designers, managers, testers, clients, and users are just a few. Although some of them can code too. You cannot say, “Hindi ka marunong mag-code, wala kang ambag.” That mindset will not survive outside the classroom. 😌

In a real development team, every role exists for a reason, and each role can directly help the programmer succeed.

Here’s how different roles contribute and support the development of the system:

✅ Programmer/Developer
You translate ideas and requirements into working code. But coding in isolation is risky. You rely on clear requirements, feedback, testing, and communication to build the right solution.

✅ System Analyst
They do not simply document problems; they architect solutions by analyzing real business needs, re-engineering processes, and designing system logic. Their work gives programmers clarity and structure, so the team builds the right system with the right features. This alignment improves business processes, enhances user experience, strengthens security, and delivers real organizational value.

✅ UI/UX Designer or Workflow Planner
They think like users. They design screen flows, layouts, and interactions. They help answer questions like: Madali ba gamitin? Logical ba ang flow? Intuitive ba ang experience? This directly affects how your code is used.

✅ Tester/Quality Assurance
They test features, find bugs, check edge cases, and validate behavior. Fresh eyes catch things programmers sometimes miss. Hindi ito panghuhusga. It is protection for your system.

✅ Documenter/Researcher
They write technical documentation, user manuals, related studies, and explanations. During defense, this is crucial. Hindi lahat ng value nasa source code. Clarity matters.

✅ Project Manager/Coordinator
They track progress, manage deadlines, communicate with advisers, and keep the team aligned. Without coordination, even the best programmer will struggle to finish.

✅ Presenter/Spokesperson
They help explain the system clearly during defense. A brilliant system that cannot be explained properly will still fail.

Each role does not compete with the programmer. Each role supports the programmer. 😌

And beyond roles, there is something even more important: .

As the saying goes, “Teamwork makes the dream work!” Totoo naman! That’s exactly how great systems are built. 💪🏻

Your capstone project is not just a mere subject nor a requirement to graduate. It is practice for real life. It teaches us:
🎧 how to listen
💡 how to explain technical ideas simply
🤍 how to accept feedback
🤝 how to collaborate
🫶🏻 how to fail, adjust, and grow

Hindi kahinaan ang humingi ng tulong. Hindi rin kabawasan sa galing ang makinig sa teammates. In fact, the best developers I know are not just great coders. They are great collaborators. 😊

So, to future programmers, developers, and or any other IT professionals: Value your team. Respect every role. Learn to work with people, not against them. 🥹

In the end, you are measured not only by your code but also by how well you worked as a team.

Sabay sabay kayong matuto. Sabay sabay kayong lalago. Hopefully, sabay sabay kayong gagraduate on time. 🥹🤍🙏🏻

To save, or not to save, that's the question. 🤔🥹😇
07/01/2026

To save, or not to save, that's the question. 🤔🥹😇

Happy New Year! Blessings, good health, and love for you all! 🎉🤍🙏🏻🫶🏻🥂
31/12/2025

Happy New Year! Blessings, good health, and love for you all! 🎉🤍🙏🏻🫶🏻🥂

Address

Panabo
8105

Website

Alerts

Be the first to know and let us send you an email when Crazy Little I.T. Girl posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Share

Category