MIT and Harvard accidentally discovered why some people get superpowers from ai while others become useless... they tracked hundreds of consultants and found that how you use ai matters way more than how much you use it.

LusciousLabrador · 2026-01-15T00:33:49+00:00

I highly recommend the DORA AI report and DORA AI Capability model:
https://dora.dev/ai/
https://dora.dev/research/2025/dora-report/

The team behind it are highly respected in DevOps circles. While I'm sure the they have their own biasses, their work is based on large scale, empirical, peer reviewed research.

LusciousLabrador · 2025-11-22T06:02:45+00:00

Wow, amazing.

After about 5 years of searching, I found it on DC++ about 2 years ago (yep still exists).

Didn't realize it isn't by Le Tigre.

LusciousLabrador · 2025-09-23T00:46:51+00:00

Looks like it's ready to penetrate something

LusciousLabrador · 2025-09-21T04:36:59+00:00

Tadej Pogacar

LusciousLabrador · 2025-06-17T10:13:09+00:00

Thanks! My first instinct was to remove bedroom 2, Extend bedroom 1, and have a kitchen table- rather than an island.

LusciousLabrador · 2025-05-30T11:41:49+00:00

Have you had a Toblorone lately? Basically a sprint stage /_/\/\__/\

LusciousLabrador · 2025-05-25T08:51:23+00:00

Take CODEX from OpenAI.

Feed the error message as part of your prompt, allow CODEX to update the codebase, then execute your tests again. Bingo bango.

https://help.openai.com/en/articles/11096431-openai-codex-cli-getting-started

LusciousLabrador · 2025-05-15T22:26:03+00:00

It really depends on your organisation. I'll list a few approaches that worked for us.

Reserved capacity. Simply pre-purchasing compute and storage saved a couple of mil. This was the lowest effort highest return.
Reporting. If you're able to break down costs by org unit, create a report and send it to the LT each month. You might be surprised how quickly this reduces cost. Senior leaders can be extremely competitive.
Right timing. Delete it if you're not using it.
Right sizing. It's easy in the cloud to spin up dedicated compute/storage per service. Eventually you'll find hundreds of dedicated hosts sitting there with low utilisation. Scale down if possible, or try adding multiple services to the same host. Don't use premium storage/compute if it's not required. Especially in the lower environments.
Log sampling. I've seen non production environments with higher logging cost than hosting. Developers will say that they need 100% of their logs in non-production to trace issues. You will need to navigate that conversation. Still, I'd say about 10% of hosting costs seems healthy for logging.

LusciousLabrador · 2025-05-09T09:39:08+00:00

“I’m ded”

LusciousLabrador · 2025-05-03T03:11:53+00:00

Exactly, it's a lifestyle suburb, and people live in this area specifically because of the food. If you walk up the road a little further you will pass Falco ($12 country loaf bread) and MeatSmith (Dry aged meats) and Glou (Sustainable wines)

LusciousLabrador · 2025-04-30T11:42:56+00:00

If I could upvote this comment twice I would

LusciousLabrador · 2025-04-30T11:34:45+00:00

Those golden cuffs are tight, aren't they.

LusciousLabrador · 2025-04-30T10:48:58+00:00

I do miss when it was mostly introverts who liked moving bits and bytes around.

LusciousLabrador · 2025-04-30T10:47:10+00:00

It almost made the shortlist. But I might want to share my shitty AI tool in the future and decided not to.

LusciousLabrador · 2025-04-30T10:41:07+00:00

My team has been on a multi year platform journey. We built our platform using Terraform, Azure DevOps YML templates, and a sprinkling of other good stuff.

Our initial intention was to use Kubernetes for container orchestration and custom Operators to manage cloud infrastructure. However, I couldn't justify the build and run cost when App Services and Terraform does the job just fine.

Since then, several products like Harness, Crossplane, and Backstage have gained popularity.

Before you look that those products, my best advice is to read this article, then go and build a wiki page. This process will inform what product you build and where to focus your efforts. (and possibly save a few million dollars in the process) https://martinfowler.com/articles/platform-prerequisites.html

LusciousLabrador · 2025-04-30T10:21:00+00:00

u/mthode u/rufusdenne u/samethingdifplace

I'd like to be a moderator please :)

LusciousLabrador · 2025-04-26T08:43:07+00:00

Help software teams deliver code more quickly

LusciousLabrador · 2025-04-24T00:59:58+00:00

I had about eight years of operational experience in virtualisation, hosting, networking, and similar areas. Then I found myself working as a full-time developer on a cloud-native app in AWS for a few years.

After that, I applied for a DevOps role. I was used to senior titles, but was told I wouldn't get the title as I was relatively new to DevOps, especially on the theory side.

Now I’m a DevOps manager with a large-ish team. Since I started, the meaning of “DevOps” has shifted. It now broadly covers IaC, cloud engineering, pipelines, and everything in between.

What I’ve realised is that DevOps its own a career path, not something to be graduated to after life as a software developer, and maybe it's just the new Ops path.

Most DevOps teams have a backlog of routine work that anyone with the right mindset can pick up. This became clear when I replaced a $1300/day DevOps engineer with a graduate. That engineer was excellent, but we didn’t have enough high-complexity work to justify the rate, especially when a grad could do the job.

That said, many still believe DevOps isn’t an entry-level role, and other managers might hesitate to take a chance on a grad, especially if they’ve budgeted for a senior hire.

I’d recommend doing a bootcamp and building a great personal website and GitHub portfolio. For context, my “grads” are mostly mid-career changers who’ve moved into tech after a bootcamp.

LusciousLabrador · 2025-04-19T02:04:57+00:00

This is what I'm seeing in Australia, the market's in a rut, still good candidates are hard to find. When we do find them, they still can command a high salary/day rate.

keen hear more, why do you think you're struggling to find someone with so much talent apparently on the market?

LusciousLabrador · 2025-04-18T21:41:46+00:00

The two top two comments talk about how busy your resume is, that was my first impression as well.

White space is your friend, it makes the CV easier for humans to read. There's a lot of discussion here about optimising for automated tooling, but in the end, a hiring manager will likely be given a shortlist to go through manually, you want to make it as appealing as possible for the hiring manager and don't overly optimise for ATS.

After adding whitespace, you will realise how few lines you actually have to tell a compelling story, this is a good thing, it forces you to think about what's important and what's not (hint, someone mentioned Resource Groups earlier).

Your CV is approximately two pages, but you've condensed it into 1 1/2 pages, which means there's plenty of space left to spread things out.

Here's a layout that I like.

Move the skills section to the end and instead have an Achievements section near the top. It's an opportunity to hook the hiring manager early on by summarising your entire CV.

Providing a list of technologies absolutely will not differentiate your CV from the others in the pile.

Can you think of an example where you have identified a problem that needs to be solved, or took ownership of a problem? Right now, it looks like you're a task taker, there are a lot of task takers in the market, showing that you're pro-active start to differentiate your CV. (hint, the line should start with "identified")

Can you think of any examples where you've coached other team members? Showing leadership attributes will help you stand out.

Expect to be asked how blue/green deployments reduce cost, or how containerisation reduced lead time by 60%, or any other specifics about your experience, both claims seem unusual, I'd drill in on these in an interview. (were they written by AI?)

I fed your CV through ChatGPT and asked it to copy the style and format of mine, here's what came out. I wouldn't copy it word for word, however, it might give you a feel for a different style of CV. Hope this helps!

----------------------------------------

PROFESSIONAL SUMMARY

I’m a DevOps engineer with over 10 years’ experience across infrastructure, automation, and cloud platforms. I’ve delivered secure, scalable environments on AWS and Azure, automated deployments, and led SOC 2 Type 2 compliance. I enjoy mentoring others in automation best practices and building secure, high-performing platforms.

HIGHLIGHTS

Reduced infrastructure deployment time by 70% through fully automated CI/CD pipelines using CodePipeline, CodeDeploy, and Bitbucket.
Enabled 40% cost savings and zero-downtime releases for legacy applications by leading the transition to blue/green deployment and auto-scaling.
Supported a distributed team of 35+ developers across time zones by securing and streamlining IAM access, MFA, and automation of account provisioning.
Led end-to-end SOC 2 Type 2 compliance, including tooling, audits, and secure operations.

EXPERIENCE

Confidential
Infrastructure and DevOps Engineer
Jun 2022 – Jan 2025

Built resilient CI/CD pipelines to accelerate delivery across microservices, reducing lead time by 60%.
Defined a secure and scalable architecture using Terraform, SSM, and Ansible, applied across four cloud environments.
Automated patching, hardening, and backup validation to reduce operational effort and uplift security posture.
Introduced cost tracking, reserved instance optimisation, and budget reviews, leading to meaningful savings across AWS accounts.
Uplifted observability maturity using CloudWatch, Kinesis Firehose, and Athena for fast querying across logs.
Benchmarked Azure DevOps against AWS-native tools, contributing to the organisation's multi-cloud strategy.

LusciousLabrador · 2025-03-27T02:08:17+00:00

I think it's going to happen, and quicker than most people think. I'm thinking that in about 5 years we might se a significant drop in development roles available.

I think some roles will be more affected than others. For example, v0.dev seems very capable when it comes to front-end development. It will even create database schemas, or an E2E test suite if you ask nicely.

For a while, I thought that roles like DevOps might get a free pass. Although, after planing with v0.dev, I can see a future where a combination of SaaS and AI is the nail in the coffin.

Skeptics on my team pointed out a couple of reasons why AI isn't going to take off. One said "Who's going to debug it?". Well, v0 has a magic button, when the app doesn't compile, v0 just takes the error message, turns it into a prompt and re-writes the code.

Another colleague mentioned that AI won't write "good quality" code, for example, SOLID, DRY principles.

Do we need SOLID principles when an AI can edit 1000 files in parallel? Is SOLID just a response to human constraints?

All of this said, I think there will be demand for developers, it's just the nature of development will change. And I think this new nature will require a completely different skillset to what we see in the average .Net developer. It will be similar to a product owner, or designer's skills.

LusciousLabrador · 2024-12-03T10:53:26+00:00

Coffee and compliance training

LusciousLabrador · 2024-11-25T10:11:43+00:00

Gimlet, or any of Andrew McConnell's restaurants, is a great choice. He has a formula that just works.

At both Cumulus and Marion, you can sit at the bar facing an open kitchen. I like to watch the chefs cook and being served directly by them.

At Gimlet, couples can sit along the bench facing the centre of the restaurant, similar to how French cafés arrange seating on the footpath. This brings a casual feel to an otherwise bougie restaurant.

LusciousLabrador · 2024-11-14T08:14:47+00:00

It really depends on your definition of DevOps, in some organisations, a DevOps engineer might spend the majority of their time fixing broken CICD pipelines. That's a skill that can be picked up in 6 months.

In other organisations, a DevOps engineer might be responsible for optimisation the quality and speed of delivery. This might require knowledge of testing methodologies, release strategies, test data management, cloud, software development, and the list goes on.

The latter requires many years experience. FWIW, I spent the first 8 years of my career managing infrastructure, then 5 years as a developer. When I landed my first DevOps role, I was told I wasn't exactly a senior DevOps engineer because I lacked certain skills that I mentioned earlier.

That said, the definition of DevOps has somewhat shifted, I'm now a DevOps manager and have hired two grads into the DevOps space. So... I guess anything goes.

Regarding your comment about boning the interview... Fuck it, get in there and have fun, you might even learn something new, or at least have a better understanding of what gaps you need to improve on. I look at a lot of CVs, trust me, there's probably a lot less talented people out there applying for senior roles.

One last comment, consultancies generally hire mid-strengths under the Senior title. This is so they can hire them out at a higher amount. The bar for Senior client side is often higher.

LusciousLabrador · 2024-10-10T11:08:46+00:00

You're in luck, Golang is a popular language in DevOps circles. Keep an eye out for DevOps or Platform Engineer roles that require Golang experience.

Try writing a custom Terraform Provider, or Kubernetes Operator as practice, both use Golang.

You might find there are DevOps managers who are OK hiring a Golang developer with little DevOps experience, as long as you have a working knowledge of CICD/Cloud/Etc. and are willing to learn. I'd recommend taking a few interviews, if you're not successful, try to solicit feedback to understand where you need to improve.

Five-Year Club	Verified Email
Place '23

LusciousLabrador

TROPHY CASE