DEV Community: Myra M.

Compliance in the Cloud Isn’t a Checkbox

Myra M. — Sat, 30 Aug 2025 14:42:33 +0000

It’s tempting to think of cloud compliance as a to-do list: enable encryption, check. Set retention policy, check. Enable multi-factor authentication, check.

But real compliance isn’t a task—it’s a posture.

Cloud platforms (AWS, Azure, GCP) hand you the tools, but they don’t hand you governance. Compliance is about how those tools are configured, why they’re configured that way, and whether the configuration aligns with your regulatory obligations—today and in six months when the system evolves.

Here’s what professionals know that most overlook:

Audit Trails Are Not Enough

Logging is the bare minimum. Without log validation and retention monitoring, you’re collecting noise. Compliance requires proving intent—not just documenting activity. If no one reviews the logs or knows what "abnormal" looks like, it’s not a control. It’s tech debt.

Cloud Misconfigurations Are the #1 Breach Vector

Most breaches don't come from zero-days. They come from open S3 buckets, overly permissive IAM roles, and expired encryption keys. Compliance must include continuous configuration monitoring—not just annual reviews or auditor check-ins.

Shared Responsibility Doesn’t Mean Shared Accountability

Cloud vendors say “you’re responsible for your data.” Compliance asks: who in your org owns the risk if it’s exposed? It’s easy to push it to IT, but if the business doesn’t understand the implications, it’s just another blind spot.

Governance Is the Hidden Metric

You can’t automate your way out of poor governance. Compliance maturity is about discipline—tight change management, role-based access, incident response drills, and periodic control validation. It’s slow work. That’s why it works.

Final Thought

The cloud is dynamic. Compliance is not static. Don’t treat it like a checkbox—treat it like a conversation that needs to keep happening.

Because the minute you stop asking questions, your compliance stops evolving.

Sometimes, AI Fails Quietly

Myra M. — Sat, 23 Aug 2025 20:58:25 +0000

I’ve been thinking about something lately when it comes to AI and analytics.

Everyone talks about speed — how fast we can generate insights, dashboards, and predictions. But almost nobody talks about what happens when the AI is wrong.

The tricky part is, it doesn’t always fail loudly.

Sometimes the numbers look reasonable.

The charts make sense.

The recommendations sound logical.

So we trust it — and move forward.

But I think the next big shift won’t be in using AI… it’ll be in 'validating it'.

Quiet systems working in the background.

Double-checking results against trusted data.

Catching subtle mismatches the AI won’t flag on its own.

Not to distrust AI.

Not to slow progress.

But to make sure we 'know what we know'.

In this next phase, speed won’t be the differentiator anymore.

Confidence will.

The Silent Power of Solo Devs: Why You Don’t Need a Team to Build Something Great

Myra M. — Sat, 16 Aug 2025 18:43:09 +0000

The Myth of the Team

The tech industry loves a team story.

Product managers, scrum masters, design leads, sprint boards, async stand-ups, collaborative wireframes, cross-functional squads—you name it. There’s an entire ecosystem built on the belief that a team is essential to shipping anything worth celebrating.

But sometimes, the best work doesn’t come from collaboration.

Sometimes, it comes from silence, solitude, and a developer with no distractions, no committee, and no one to check in with but themselves.

When You Work Alone, You Work Honestly

Solo devs don’t have time for office theater.

We don’t bluff our way through sprint reviews, we don’t hide behind group credits, and we don’t wait for permission to pivot. Everything we build is ours—flaws, fixes, features, and all. We don’t waste hours on Slack trying to explain a design decision. We make it. We test it. We move.

And in that process, there’s something quietly powerful happening:

We become better thinkers.

Why Solo Doesn’t Mean Small

The word “solo” gets tossed around like an apology, like it’s something less than. But being a solo dev doesn’t mean being unambitious—it means being strategic.

You’re the engineer and the product manager.

You’re shipping features, not status reports.

You’re testing, learning, and iterating in real time.

A solo dev who knows how to scope, prioritize, and build with intention will outperform a bloated five-person team chasing perfection every time.

Real Quiet Wins

You won’t see many articles about solo devs launching quiet tools. They don’t trend. They don’t make the “Top 10 VC-backed startups” list. But they exist, and they’re making money, solving problems, and gaining traction without all the noise.

They’re the indie newsletter signup form that converts better than a Fortune 500 landing page.

They’re the one-feature app that does exactly what it says on the tin.

They’re the reason you bookmarked that tool two years ago and still use it today.

And nine times out of ten? One person built it.

What You Gain Without a Team

Speed: No need to schedule a check-in to fix a bug.

Clarity: You build what you need, not what a team debates.

Focus: You own the roadmap and the rhythm.

Peace: You’re not managing personalities—you’re managing problems.

And let’s be honest: not everyone is blessed with a dream team. Some of us had to learn to build alone because no one showed up. Some of us got kicked off teams and decided to keep going anyway.

Some of us were never invited to the table—so we built our own.

Final Word

You don’t need a team to build something great.

You need an idea.
You need commitment.
You need quiet.
You need discipline.

And if you’ve got those things?

You’ve already got more than most teams ever figure out.

Beyond the Build: How Hackathons Fuel Soft Skills and Personal Growth

Myra M. — Sat, 09 Aug 2025 13:17:16 +0000

When people think of hackathons, they picture long nights of coding, caffeine, and the frantic push to meet a deadline. But what doesn’t always make the highlight reel is the quiet, powerful growth that happens between the keystrokes.

Hackathons aren’t just about building a product — they’re about building people.

Communication Under Pressure
In a hackathon, ideas move fast. You learn to explain complex concepts in plain language, listen actively, and adapt on the fly. It’s not about being the loudest voice in the room — it’s about being the clearest.
Collaboration With Strangers
You might be working with teammates you’ve just met, from different backgrounds, industries, and even time zones. By the end, you’ve developed a shorthand — a way of working together that turns chaos into cohesion.
Creative Problem-Solving
Constraints breed creativity. Limited time, resources, and tools push you to find innovative solutions you wouldn’t have thought of in a more comfortable setting.
Resilience and Adaptability
Things break. Plans change. Code fails at 3 a.m. Hackathons teach you to pivot without panic, to recover quickly, and to keep moving forward.
Confidence in Your Capabilities
The rush of presenting a finished project — even if it’s not perfect — reminds you that you can learn, adapt, and deliver under pressure. That confidence doesn’t fade when the hackathon ends.

The Real Win
Sure, hackathons can add a shiny project to your portfolio. But the bigger prize is the set of human skills you carry into every future role — skills that make you not just a better coder, but a better teammate, leader, and problem-solver.

In the end, hackathons build more than apps. They build adaptability, empathy, creativity, and confidence. They build you.

Live Mock API: User Data Sandbox Explore a no-auth, read-only user data API

Myra M. — Fri, 01 Aug 2025 20:05:17 +0000

Live Mock API: Users

Experience a public, no-auth, read-only API that returns a list of mock users live.

Click here to try the Users API

Example response:


json
[
  {
    "id": 1,
    "name": "Leanne Graham",
    "username": "Bret",
    "email": "Sincere@april.biz"
  }
]

No API keys. No redirects. Demo-ready for analytics, dashboards, or learning workflows.

About This API
This mock endpoint is hosted on Beeceptor, which offers free testing APIs without requiring any setup or sign-up. Great for building UI demos or exploring structures like real user objects or to-dos.

When AI Feels Too Real: The Perils and Power of Emotionally Intelligent Machines

Myra M. — Sat, 26 Jul 2025 11:02:41 +0000

Most AI discussions orbit ChatGPT upgrades and job loss fears. But there's a quieter shift happening: machines learning empathy.

AI can now detect tone, mirror emotion, and respond with uncanny compassion. Think virtual therapists, grief bots, even dating sims. The tech is impressive—but are we bonding with code?

Synthetic empathy feels helpful, until it's manipulative. These tools are trained on biased data. What if they "misread" someone who doesn't fit the mold? Or worse, influence decisions based on emotional triggers?

We're not just building smarter assistants. We're building machines that influence trust, behavior, and relationships. That line between teammate and tool? It's starting to blur.

If your AI is designed to connect emotionally, your team better include ethics, UX, compliance, and real human insight.

10 Dev Tools That Sound Great... But Nobody's Really Using Them

Myra M. — Sun, 20 Jul 2025 09:47:51 +0000

Tech loves trends. Blink and you’ll miss the next must-have tool getting hyped to the moon. But for every actually useful innovation, there are a dozen tools that make noise, look impressive, and then quietly fade into the background—rarely touched, rarely missed.

Let’s call it out. Here are 10 dev tools that sound amazing, dominate conferences and Reddit threads... and still end up collecting digital dust.

Kubernetes
The Prom King of DevOps. It runs the cloud! It scales your pizza tracker! But unless you work at a hyperscaler or DevOps-heavy org, you’re probably just copying Helm charts someone else wrote. Most engineers don't even need it.
Notion (for engineering docs)
Everyone loves the aesthetic. And then someone tries to search for a decision made last quarter and ends up six databases deep in a toggle graveyard. Docs need structure, not just vibes.
Electron Apps
Cross-platform and cute—until your machine starts wheezing. Everyone talks about building the next Slack or VS Code with Electron, but nobody wants to QA it after the RAM apocalypse.
GraphQL
Sounds sleek: get exactly the data you want. Reality: overengineered queries, N+1 bugs, and your frontend team becoming accidental backend maintainers. REST didn’t die. It just went back to work.
AI Code Assistants
Cool demos, real promise... but most teams are still doing double-checks on everything it generates. You save time on boilerplate and lose it debugging the “confidence score: 94%” hallucination.
Blockchain for Everything
Blockchain! For healthcare! For storage! For version control! For meetings?? The tech isn’t useless, but when you need an actual product instead of a whitepaper, everyone disappears.
Low-Code Platforms
Looked revolutionary... until people realized that maintaining logic in drag-and-drop UIs is like playing Jenga with wet spaghetti. Great for MVPs, a nightmare for scale.
JAMstack Tools
Gatsby, Netlify, and friends were supposed to be the future. Then you needed real-time features, user accounts, or a CMS... and ended up rebuilding everything in Next.js anyway.
Static Site Generators (SSGs)
So hot in the mid-2010s. Then you needed to update content daily and remembered you’d hardcoded everything into Markdown. Shoutout to the devs who turned their personal blog into a full-time refactor.
Containerized Local Dev Environments
Sounds clean. Isolation! Repeatability! But if you’ve ever watched someone spend two days debugging a broken Docker volume so they can run npm install, you know the dream doesn’t match the struggle.

Tech loves shiny objects. But usefulness isn’t about noise—it’s about adoption, longevity, and how well a tool integrates into daily workflows.

Some tools rise above the hype. The rest? They go back in the toolbox.

Why I’m Betting on BI, Compliance & QA — Not AI Hype

Myra M. — Sat, 19 Jul 2025 14:45:21 +0000

Everyone’s chasing AI. I get it — it's flashy. But I’m focused on something else: job security, sustainability, and roles that can’t be automated overnight.

Business Intelligence, Compliance, and QA might not sound sexy, but these roles keep businesses from imploding. They’re the quiet backbone of every major org. And guess what? These roles aren’t going away.

We’re in a weird moment. AI is replacing junior roles. Layoffs are slamming engineers. But behind the scenes? Companies still need dashboards, clean data, tested systems, and airtight risk compliance.

I’m intentionally designing a tech path rooted in stability, autonomy, and long-term value. These roles:

Require critical thinking, not constant code

Rely on attention to detail, not clout

Offer remote/hybrid flexibility

Allow individual contributors like me to thrive

My pivot is intentional. It’s not about chasing trends — it’s about building long-term stability.

Breaking into Tech Without a Shortcut: My 9-Month Reality Check

Myra M. — Sat, 12 Jul 2025 15:35:26 +0000

Let’s be honest: some of us don’t get shortcuts. No “tap on the shoulder” jobs, no family in tech, no one whispering tips into our DMs. We’re the ones who have to crawl through the mud, self-fund everything, and still show up smiling. That’s been my story — and I know I’m not the only one.

Nine months ago, I pivoted hard into tech. I come from data, insurance, and oil & gas, but decided I wanted something safer, scalable, and futureproof. I’ve earned 30+ tech certifications since November — all while dealing with health scares, losing sleep, and taking care of my cat (who deserves a medal).

Despite that? I’m still here. I’ve applied to hundreds of jobs. Been ghosted. Had my references interviewed — then ghosted. I’ve been told I’m “unqualified” for roles that match my résumé line-for-line. But I didn’t fold. And I won’t. Because I know what I bring.

This isn’t a sob story. It’s a reality check. A lot of folks think tech is “easy” now — a cert and a job. Not for all of us. Not if you’re underrepresented. Not if you’ve been historically left out of the referral loop. Not if you’re pivoting without a CS degree.

But if you’re out here doing it anyway? I see you. And I’m with you.

# Getting Started with APIs Using Postman 🌤️

Myra M. — Mon, 07 Jul 2025 16:06:52 +0000

I just published my very first public Postman collection! 🎉

This API request pulls weather data using Open-Meteo and is a great hands-on learning tool for anyone starting with APIs or testing tools like Postman.

🧪 Check it out here!

Thanks to the amazing #Postman Supernova community for encouraging beginners like me to get started with real tools. 💡

Feel free to fork it and try your own version. Let’s learn together!

beginners #postman #testing #apis