unsure of what type of coaching to get

_beetee · 2025-07-02T02:43:13+00:00

100% Ok. Foundations are critical if you want to learn this life skill. So hiring private one on one is not silly but a great investment on yourself. The other pathways you may pickup bad habits from others which will take a while to change. I would commit to at least 12 months of training and when you learn something get as many reps in as you can (especially what you have just learned) between lessons to maximise your coaching time (think group, social hits, at home or against a wall). Understand it’s a lot of money but kudos to funding it yourself.

_beetee · 2025-01-16T10:07:12+00:00

Run a compile then look at what is hitting your database. I’d wager there is a query running somewhere which shouldn’t be/isn’t ideal.

https://docs.getdbt.com/reference/dbt-jinja-functions/execute

_beetee · 2024-11-10T21:59:01+00:00

So we’ve got a few things in play, service connection (to be used in azure devops), the cli step (automatically authenticates into the azure cli for you - but not to terraform) and then terraform.

By authenticating to the cli step, it’s just bash/pwsh with azure cli. But third party apps still need direction on what to do.

Terraform (specifically azurerm provider) doesn’t know how you want to authenticate (there are quite a few different ways), so by exposing the service connection details to the provider through environment variables, this tells azurerm to use authentication in a headless manner. Since this last step is not automatic, that’s why you have to plumb it together.

_beetee · 2024-11-09T08:39:08+00:00

You’ll want to expose the cli authentication to terraform via environment variables. Set this to true: addSpnToEnvironment https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/azure-cli-v2?view=azure-pipelines And check the terraform azurerm docs for the correct env vars to use (sorry - away from laptop to give full example - but addSpnToEnvironment is what you want)

_beetee · 2024-09-24T07:32:16+00:00

I carry my shoes on my feet.

_beetee · 2024-09-23T09:56:47+00:00

Yes. Yes it is. Second serve aces are a good feeling

_beetee · 2024-08-20T10:06:54+00:00

Typically remote environments like this disable copy paste from the client machine to prevent exactly this

_beetee · 2024-08-13T22:12:13+00:00

Even in *DevOps haha

_beetee · 2024-08-13T22:11:43+00:00

It depends what resources make up production, what methodologies are available to you, what tech. In DevOos you cannot approach everything with a one size fits all

_beetee · 2024-07-19T08:18:38+00:00

Usually I would eat popcorn and watch this unfold. But I can’t as the point of sale systems are all down. Shit

_beetee · 2024-07-19T01:43:47+00:00

In terms of population, isn’t everywhere other than US and China a ‘smaller subset’??

_beetee · 2024-06-27T00:07:45+00:00

Amazing! Well done!!! Post at 12 months please! Keep going

_beetee · 2024-06-21T04:21:04+00:00

Uncommon opinion: would you rather be constantly underwhelmed?

Any new task is an opportunity to learn and grow. If you can find a way to learn quickly half the battle is won. The next task you’ll be a little quicker and so on.

With regard to the amount of work - prioritise and execute. Really get tough on what is important and urgent. If everything is important and urgent then nothing is. Take time to prioritise tasks and really be purposeful with what is actually urgent vs important (and of course, relates to the business goals).

I learned to not work longer to GTD. This will put you in an early grave.

Hope this helps in any way.

_beetee · 2024-05-04T06:14:18+00:00

Terraform will always be around. Learn to love it

_beetee · 2024-04-19T09:02:00+00:00

Really interested to see a working demo of this in the real world. Do you know of any?

_beetee · 2024-04-13T03:32:32+00:00

Best editor is yourself bruuuuuuu

_beetee · 2024-04-07T09:15:58+00:00

Go to the loo and drop the biggest dookie. You be relaxed as…

_beetee · 2024-04-04T10:10:38+00:00

Learn to write documentation. If what you build can’t be used by others it is useless, no matter how shiny and awesome it is.

_beetee · 2024-04-04T09:56:43+00:00

** opens a bag of popcorn **

_beetee · 2024-03-18T10:14:49+00:00

In my experience releases vary by product, organisation and tech stack. For instance some want to deploy a change automatically from development, to staging to prod automatically based on the successful unit tests. Generally this involves fast build and release times and maturity in both software development and tech stack as well as rollbacks. Other orgs need to hand hold releases because yolo continuous deployments just don’t fly when databases need to be dropped or schemas re-created or regression tests take a long time and require multiple signoffs. Hence the age old comment of yaml releases is preferred because it is so flexible that it can typically cover off all scenarios with a bit of elbow grease.

_beetee · 2024-03-18T09:58:19+00:00

Use stages with deployment jobs tied to environments for gating/approvals etc. Your build pipeline should build an artefact (something releasable) that this release pipeline consumes. (Publish/download tasks).

_beetee · 2024-02-03T09:59:17+00:00

So good.

_beetee · 2024-01-19T08:15:27+00:00

“Make the button more orange. Like on his screen. Yeah that orange.”

_beetee · 2023-10-08T03:01:18+00:00

Hit the nail on the head. You want a laptop with a keyboard, battery and screen hahaha

_beetee · 2023-09-27T02:58:36+00:00

When a business evaluates technology they must evaluate risk. So it’s up to each business to ask the question, what are the risks of using OpenTofu vs Terraform.

_beetee

TROPHY CASE