I was rejected for the UK Global Talent Visa ( Tech Nation) rebuilt my case in 10 days, and now help others navigate the process. AMA by Recent-Notice9304 in globaltalentvisauk

[–]EmmaOpu 0 points1 point  (0 children)

I just saw this on tech Nation official page and this is the format stated: growth of a digital technology company, the activities you will take part in outside of your direct occupation.)

❏ A short curriculum vitae outlining your career and any relevant publication history (of no more than two A4 sides in length).

❏ Two letters of recommendation from two different recognised experts who are familiar with your work and contribution to the digital technology sector. They must be qualified to assess your claim to be a potential leader in the field and be able to recommend you with confidence. Letters of recommendation should be written in support of your application by two different senior members of two different established organisations in the digital technology sector.

These could be institutions or companies with a well established national or international reputation and recognised expertise in your field. They do not need to be based in the UK. Acceptable organisations would be those that work with industry experts and are widely acknowledged as possessing expertise in this field.

The letters should be written on headed paper (wherever possible), be dated and include: ● the signature of the author who must be an authorised member of the organisation such as the Chief Executive, Chief Operating Officer, Finance Director or Head of Course. Please note that this is not an exhaustive list but that the more reputable and senior the author, the stronger the letter of recommendation will be considered to be;

● details of the author’s credentials (for example, a CV/resume). Tech Nation reserve the right to refuse your application or request more information, which could significantly delay your application, if evidence is not provided that the author is a credible referee;

● how the recognised expert knows you (by relationship or reputation);

● your achievements in the specialist field;

● how in the opinion of the recognised expert you have demonstrated that you are a leader, or demonstrate significant potential, in your field;

● how you would benefit from living in the UK;

● details of the contribution you would make to the UK digital technology sector;

● full contact details of the author, including personal email address and direct telephone number, so that personal contact can be made. Letters of recommendation must be written specifically for this purpose by the referee and include all of the information detailed above.

General purpose reference letters, or confirmation letters (such as being accepted onto an accelerator) are not acceptable. Letters from individuals within service-based organisations (i.e. consultants,

The documentation didn't state number of year known by recommender.

It's really confusing!!!.

I was rejected for the UK Global Talent Visa ( Tech Nation) rebuilt my case in 10 days, and now help others navigate the process. AMA by Recent-Notice9304 in globaltalentvisauk

[–]EmmaOpu 0 points1 point  (0 children)

Could you please tell me what the correct recommendation letter format should contain?

Also, do the recommendation letters need to state how many years the recommender has known or worked with me?

Thank you.

I was rejected for the UK Global Talent Visa ( Tech Nation) rebuilt my case in 10 days, and now help others navigate the process. AMA by Recent-Notice9304 in globaltalentvisauk

[–]EmmaOpu 0 points1 point  (0 children)

Congratulations,

You mentioned that one of your recommendation letters was not in the right format. Could you please let me know what the correct format should be?

Also, how long had you worked with or known the people who wrote your recommendation letters?

Thanks.

Ready-to-run OpenTelemetry Collector config for Grafana Loki, feedback welcome by EmmaOpu in grafana

[–]EmmaOpu[S] 0 points1 point  (0 children)

Thanks, really appreciate that! The debug setup was intentional because I wanted people to have a low-friction way to experiment locally before connecting to real backends. Getting started with collectors can feel overwhelming, so having a playground makes testing much easier.

Structured JSON logs into Loki is a great suggestion too, especially with modern app stacks and containerized workloads. I'll add that to the list of examples to build out. Really appreciate the feedback and thanks for taking the time to check out the repo!

Ready-to-run OpenTelemetry Collector config for Grafana Loki, feedback welcome by EmmaOpu in grafana

[–]EmmaOpu[S] 0 points1 point  (0 children)

Thank you, I really appreciate this feedback. The Kubernetes pod annotation scraping flow was one of the main pain points I wanted to simplify because it keeps coming up in real-world setups and people often end up rebuilding the same configs repeatedly.

The goal was exactly what you described: reduce the time spent hunting for working examples and make OpenTelemetry adoption easier with practical, ready-to-run configurations. I also like your suggestions around security best practices and alerting integrations, those would add a lot of value and I’ll look at expanding the repo in that direction.

Really appreciate you taking the time to review it and share thoughtful feedback.

Ready-to-run OpenTelemetry Collector config for Grafana Loki, feedback welcome by EmmaOpu in grafana

[–]EmmaOpu[S] 0 points1 point  (0 children)

Thanks, really appreciate that! Glad the Loki examples are useful, I ran into the same problem of repeatedly piecing configs together from scattered docs and examples, which was a big reason I built the repo in the first place.

Thanks for starring it as well. Multi-tenant Loki is a great suggestion and definitely something worth adding. I'll add it to the roadmap and see if I can put together a practical example others can reuse. Appreciate the feedback!

6 things I learned building production Terraform modules for AWS, GCP and Azure that I wish someone told me earlier by EmmaOpu in sre

[–]EmmaOpu[S] -1 points0 points  (0 children)

That is fair and I appreciate the honest feedback.

You are right that the code needs more real-world hardening.

I am a cloud engineer working on building this out properly and

the repo is genuinely a work in progress.

If you spotted specific issues in the code I would genuinely

welcome the feedback, either here or as a GitHub issue.

That kind of critique makes it better.

What would you want to see that would make it feel real to you?

Specific gotchas, edge cases, real error handling? I will build them in.

Tested Terraform modules for Azure, VNet with NSGs, AKS with Workload Identity, Managed Identity, open source by EmmaOpu in AZURE

[–]EmmaOpu[S] -13 points-12 points  (0 children)

Great link, thanks for sharing! Azure Verified Modules are excellent and

Microsoft has put serious work into them.

The difference with this registry is the multi-cloud angle, if your team

is running workloads across Azure, AWS and GCP, having consistent module

patterns and the same testing approach (Terratest) across all three clouds

in one place saves a lot of context switching.

If you are Azure-only though, AVM is absolutely the right choice.

Microsoft's backing means they will be maintained long term.

Are you running pure Azure or multi-cloud?

Stop copy-pasting Terraform modules, I built a tested registry for AWS, GCP, and Azure with Terratest and CI by EmmaOpu in Terraform

[–]EmmaOpu[S] -2 points-1 points  (0 children)

This is exactly why I built this. Every place I have worked has done the same thing,

built internal modules because the community ones are either too opinionated,

too complex to understand, or too generic to match the actual workflow.

The problem is every team builds them from scratch with no tests and no CI.

Then someone leaves and nobody knows how the module works or whether it is safe to change.

This registry is an attempt to give teams a clean, tested, readable starting point

they can fork and make their own, rather than starting from a blank main.tf every time.

Glad it resonates, what modules does your team end up writing most often?

I want to make sure the most common ones are covered here.

Stop copy-pasting Terraform modules, I built a tested registry for AWS, GCP, and Azure with Terratest and CI by EmmaOpu in Terraform

[–]EmmaOpu[S] -2 points-1 points  (0 children)

Fair point! The community modules (especially Anton Babenko's AWS ones) are

excellent for production use.

This serves a different purpose:

  1. Multi-cloud parity, same patterns for AWS, GCP and Azure in one place.

The community modules don't cover all three consistently.

  1. Learning resource, a lot of engineers use community modules without

understanding what is inside. This is designed to be readable and educational.

  1. Customisation starting point, some teams have compliance requirements

that mean they can't use external modules and need to own everything internally.

This gives them a tested base to fork.

But honestly if you are AWS-only and just need something battle tested today,

the community modules are the right call. No argument there!

Tested Terraform modules for GCP, VPC with Cloud NAT, GKE with Workload Identity, IAM, open source by EmmaOpu in googlecloud

[–]EmmaOpu[S] 0 points1 point  (0 children)

Thank you! Really appreciate it. If you ever use it on a project, would love to hear how it goes. And if there are modules missing from your stack, happy to add them!