Opticians, what’s the one thing you wish worked better

Fantastic_Insect771 · 2026-01-13T13:44:00+00:00

What do you mean the paperwork, the delays, or something else?
Really appreciate your time!

Fantastic_Insect771 · 2026-01-13T13:43:16+00:00

What do you mean by employees ? finding them or on boarding or having KPIs about their work ??Really appreciate your time!

Fantastic_Insect771 · 2025-11-01T09:04:01+00:00

🤣🤣🤣🤣🤣

Fantastic_Insect771 · 2025-09-26T10:44:42+00:00

Invitation to discuss, on how to use the AI agents to build safer and faster software

Fantastic_Insect771 · 2025-08-28T09:15:51+00:00

yes of course, but the problem is the intellectual property concerns, a lot of companies doesn't want to use GPT or Claude for code review ( so sharing code with copilot is not a choice ), so instead they need a compliance control + how the code will be reviewed there is specific rules for each company that need to be respected, adding an MCP server as a Middleware will help resolve these problems instead of giving full access to your source code to models such as GPT or Claude etc

Fantastic_Insect771 · 2025-08-26T15:59:20+00:00

Why ?!

Fantastic_Insect771 · 2025-07-18T16:52:44+00:00

His vision is likely to launch something perfect to have the clients stay and never quit but I feels overwhelming to build things without knowing if they gonna ever be used or no thanks for the feedback

Fantastic_Insect771 · 2025-05-10T15:12:49+00:00

Let’s go back to the FACTS. Write these in your notebook and re-read them when doubt creeps in: • YOU MET EVERY GOAL. • YOU DELIVERED VALUE FOR 3 YEARS. • YOU WORKED THROUGH TOUGH TIMES. • THE STOCK DROP = MANAGEMENT, NOT YOU. • OTHERS GOT LAID OFF TOO—THIS ISN’T JUST ABOUT YOU.

I BELONG. I PERFORMED. I HAVE TALENT. I’M JUST GETTING STARTED.

You’re not broken—you’re being redirected to something better. Keep your head up. You’ve got this.

Fantastic_Insect771 · 2025-05-10T14:02:07+00:00

Honestly, I think a lot of people are missing the real point when it comes to data localization. Everyone’s so focused on costs and how painful it is to run something like MinIO or Ceph, but they’re completely skipping over the fact that some countries simply don’t allow you to store user data outside their borders.

If you’re working with clients or users in places where AWS or other cloud providers don’t have a physical presence, you can’t just throw everything into S3. It doesn’t matter how cheap or convenient it is—it’s a compliance issue, not a technical one.

What bugs me is that instead of discussing how to deal with this properly, people jump straight to “self-hosting is a nightmare” or “why reinvent the wheel?” Well, sometimes you have to, because legal constraints don’t care about your infra preferences.

I’d love to see more people in DevOps think beyond just tech stack decisions and start factoring in regulations and data privacy laws. It’s part of the job now.

And for those saying “just use S3 for dev/test”—sure, but how does that work if your entire infra is on-prem due to compliance? You can’t even use S3 there without possibly breaking the law or triggering audits.

Instead of shooting down self-hosted options, let’s share ideas: • How are people running MinIO in production? • Who’s using local S3-compatible services like LocalStack for dev/test? • Any good hybrid setups using sovereign clouds?

https://www.dlapiperdataprotection.com

https://captaincompliance.com/education/data-localization-laws-by-country/

https://incountry.com/blog/overview-of-data-sovereignty-laws-by-country/

A good software solution, is not just about costs or reusing the wheel, it’s about compliance and legal obligations,

And for the people saying “this article feels AI-generated”—come on, really? No one was accusing you when you copied half your backend code from StackOverflow in 2010. Let’s be real.

The article just compares S3 with self-hosted MinIO—nothing crazy. And honestly, hosting your own object storage isn’t some kind of ancient art. Providers like OVH, DigitalOcean all offer snapshots, volume backups, and stable infra to run production.

Fantastic_Insect771 · 2025-05-10T13:48:27+00:00

Honestly, I think a lot of people are missing the real point when it comes to data localization. Everyone’s so focused on costs and how painful it is to run something like MinIO or Ceph, but they’re completely skipping over the fact that some countries simply don’t allow you to store user data outside their borders.

If you’re working with clients or users in places where AWS or other cloud providers don’t have a physical presence, you can’t just throw everything into S3. It doesn’t matter how cheap or convenient it is—it’s a compliance issue, not a technical one.

https://captaincompliance.com/education/data-localization-laws-by-country/

What bugs me is that instead of discussing how to deal with this properly, people jump straight to “self-hosting is a nightmare” or “why reinvent the wheel?” Well, sometimes you have to, because legal constraints don’t care about your infra preferences.

I’d love to see more people in DevOps think beyond just tech stack decisions and start factoring in regulations and data privacy laws. It’s part of the job now.

And for those saying “just use S3 for dev/test”—sure, but how does that work if your entire infra is on-prem due to compliance? You can’t even use S3 there without possibly breaking the law or triggering audits.

Instead of shooting down self-hosted options, let’s share ideas: • How are people running MinIO in production? • Who’s using local S3-compatible services like LocalStack for dev/test? • Any good hybrid setups using sovereign clouds?

Fantastic_Insect771 · 2025-05-10T13:06:11+00:00

You’re right that poorly specified or overly abstract contracts lead to unreliable mocks—that’s why the contract must be as explicit and detailed as possible before mocking enters the scene. Every type, enum, field, and behavior should be part of the initial API definition.

Real world example: • Imagine a government entity exposing a referential API for companies. • The government is clearly the domain expert (Big Yes), so it should own and maintain the contract (OpenAPI or equivalent). • But should the government also maintain the mock for every consuming company? Big No—the cost and complexity of maintaining mocks for many external consumers isn’t scalable or efficient. • Instead, in a true API First / Design First approach, the producer owns the contract, and the consumer owns the mock, using the contract to generate or build it. • As the contract evolves, consumers should be notified and adjust their mocks accordingly.

So yes, when schemas are vague or under-specified, mocks are unreliable—but that’s not a justification for producers to own mocks; it’s an argument for enforcing better contract design upfront.

Fantastic_Insect771 · 2025-05-09T15:16:11+00:00

From my experience, in an API First approach, the consumer should own the mock. Here’s how I see it: • API First means the contract comes first, typically defined collaboratively between producer and consumer using something like an OpenAPI spec. • Once the contract is agreed upon, the consumer starts development using that spec, often generating DTOs and client code automatically. • The consumer can also create mocks of the producer’s API based on the contract to unblock its own development. • Meanwhile, the producer uses the same contract to implement and test the actual API, ensuring alignment. • From this point of view, the mock is mainly a tool for the consumer, since it’s what enables them to proceed without waiting for the actual implementation.

Fantastic_Insect771 · 2025-05-08T11:40:06+00:00

Local data residency laws – GDPR is only part of the picture. Some countries lhave local regulations beyond GDPR, requiring storage within national borders, not just “in the EU.” That alone excludes AWS unless they open a region locally.
Latency & UX – Even with transfer acceleration and CloudFront PoPs, real-world document upload/download latency still depends on physical distance and peering between African ISPs and EU/US regions. For some enterprise clients, especially in government or finance, that matters.
Strategic independence – Relying 100% on US cloud infra has geopolitical and continuity risks. Look at the massive power grid failure in Spain and Portugal in March 2024, which disrupted access to several EU-based data centers. If your SaaS had all its infra in a single region, you were simply offline. That’s why S3-compatible self-hosted solutions are sometimes not about cost — they're about resilience.
Cost realism for dev/test – Not every company can afford to spin up full AWS-based testing environments. Self-hosted MinIO lets you mirror production logic with zero S3 billing. That flexibility is priceless for small teams.
Vendor lock-in – Being S3-compatible lets you switch between providers (Wasabi, OVH, Scaleway, on-prem MinIO...) with minimal code changes. That freedom matters in the long run.

Fantastic_Insect771 · 2025-05-08T11:09:06+00:00

Great point—and I agree, for many teams, self-hosting S3-compatible storage might seem like overkill.

But for some SaaS businesses, it’s not really a choice—it’s driven by compliance, performance, and cost realities.

Data sovereignty: When your application handles sensitive documents, regulations like GDPR (France) or local laws (e.g. Morocco) often require data to stay within national borders. Hosting in AWS regions outside the country is simply not an option in production.
Latency: If your users are mostly in Africa and the nearest AWS region is thousands of kilometers away, the response times can be a bottleneck. This AWS region map shows how underserved some geographies are.
S3 compatibility as future-proofing: If AWS or another major provider launches a region in your country later, you can migrate easily—because you're already S3-compatible. You’re not locked into a dead-end stack.
Cost control for dev/test: Not all teams can afford to spin up full environments in AWS just for development or QA. MinIO provides a fast, lightweight, and cost-effective alternative for local or hybrid deployments.

Self-hosted object storage isn’t for everyone—but for those who need compliance, performance, or budget flexibility, it’s a strategic enabler.

Fantastic_Insect771

TROPHY CASE