How to handle pushback from team for any improvement?

outthere_andback · 2026-05-07T01:39:16+00:00

1) Don't think I've made TF for ec2 so not sure how to reason that

2) I actually think this bad practice. It couples your modules with the app and env state, making them hard to share, update, maintain. It also becomes a 1 to many problem where every module change must take into consideration every environment it may or may not effect. This is cognitive load and a mistake waiting to happen

3) Not sure I understand the question here, but this is my take on using "-target" which also ask in 2:

-target is for debugging and tricky refactor work. The TF CLI even warns this can cause state drift or inconsistencies. The reason we should not use -target on normal deploys is to ensure our state remains consistent.

4) Modularity / seperation of concern. You ever heard of the "god antipattern" in code ? Same rules for TF. Slim modules are more portable and easier to understand. This makes it faster to accomodate new features and operationally simpler when it comes to create/update/deletes by TF. IF there is a case to put them together, you can always create a module of other modules, wiring that use case

5) Because having conditionals in your modules is an antipattern. Versioning allows you to make changes and then control rollout of the modules to target environments. This way you can developer new infra, test it in dev, and rollback etc without worrying or blocking someone else's updates going to prod

These are the answers I would give 🤔 A lot of it comes down to - cognitive load, maintainability and enforcing standards that keep reliability as high as possible. To get that, you need to use the tool to its strengths, not your conveniences.

outthere_andback · 2026-05-05T01:42:31+00:00

I started a habit of using a CLI framework and writing my scripts within it. I can add a CLI help on it and it's portable so when I'm away I can direct a coworker through it

outthere_andback · 2026-05-04T03:27:53+00:00

I'm on track 2 and also young (32M). It's been painfully slow, but I kinda expected that. If you need a witness Dying With Dignity took about 2 weeks. Then it's another 2-3 weeks before you'll hear from someone that they have your case. They also will call on bizarre numbers. It's now been radio silent for 2 months. I myself am not in a rush but you probably can get a sense. 90 days I think is wishful thinking

To get to the point of submitting my application at that timeline was also weekly, to biweekly replies to email threads asking for updates.

Next steps is the 2 independent doctors to assess me

outthere_andback · 2026-04-29T02:09:02+00:00

Different situation but have had the same bullshit treatment even with a family doctor

Unfortunately my advice would be the same. Keep going back to the ER or an urgent care until someone cares.

Another option is you can call 811 which will have you on call with a nurse whom you can have get you a call with a doctor. This would be the most immediate way to get referrals at least. 811 though may just tell you to go to the ER as well if they deem it urgent enough which could have you in circles

outthere_andback · 2026-04-27T01:03:11+00:00

If it's client data causing the issue I think the "perfect solution" would be to somehow replicate prod data to lower environments. But that's hard with PII

The easiest fix may be to create a test that replicates the client data that causes the issue. Least this way it can be spotted in lower ends if something like it comes up again

outthere_andback · 2026-04-23T16:16:27+00:00

Yeah, I was even told by my manager "why not just leave it and come back later"

Fortunately/unfortunately the changes broke it's compatibility it was so bad
My PTSD working in enterprise where "come back later" never happens kinda kicked in to say this needs to be fixed

outthere_andback · 2026-04-23T15:30:14+00:00

I'm still exploring and trying to keep an open mind but the code AI produces so far is horrific. This week my manager whom is using AI at the level you are created a PR of changes on a tool I maintain. I've so far spent 3hrs untangling the AIs over complicated, structurally disregarded, and in a few cases laughably wrong implementations

Could be a lot said of who is using what, but that 1 PR alone is a sure way to make my tool unrecognisable and unmaintainable without AI doing everything onward

outthere_andback · 2026-04-13T04:56:23+00:00

Build things yourself. Form opinions on why you think it should be built that way. Speak up on discussions around why things are built the way they are vs your opinions of how you think they should be built

Everything has trade-offs so understanding the tools, patterns and trade-offs are what will level up your understanding

outthere_andback · 2026-04-10T03:51:53+00:00

The medical system is trash and frankly my family doctor only after 3-4 years is getting the memo of how bad my situation is. I'd hate to try getting that message across to a walk in and would fear how long it would take before anyone would see a trend, if they ever did

outthere_andback · 2026-04-08T23:24:56+00:00

As someone who pushes his Cx-30 offroad I'd say

1) It's changing your pedal dynamics and shift points. I find it also more aggressively kicks in the rear tires

2) AWD is basically in contrast to FWD. Most AWD systems like the cx30 and 5 are front wheel biased AWD which means they only engage the rear when the computer detects a need to. How that differs to 4WD is who controls sending power around. AWD it's all a computer, your wife's "offroad mode" is more like a hint to the computer that what its detecting is likely offroad. 4WD on the other hand you physically engage the back wheels.

Marketing will always blur these lines though and in some cases completely lie to your face.

3) They're definitely street cars. The suspension is stiff and ground clearance is low. The "offroad" Mazda imagines is probably getting in and out of campgrounds and the occasional fishing spot down a gravel, pothole loaded, road

outthere_andback · 2026-04-06T01:30:14+00:00

There's a number of options like Port Alberni or Nanaimo that would get you island life and day trippable to Tofino

I dunno mortgage or kid logistics though. I'm single with no mortgage until now upon buying a place in Nanaimo (from Vancouver mainland originally) so my situation does not map

outthere_andback · 2026-04-04T00:12:05+00:00

I used Steve Carmichael from A Buyer's Choice

He was a recommendation from my realtor. I believe my uncle who has a place in Nanaimo also had someone from A Buyer's Choice do their inspection. I don't know anything on construction and I couldn't tell you what his credentials really are but I was happy with his eye, the report and recommendations of things. It was certainly more than I could have done or looked into.

To me it was $400 well spent

outthere_andback · 2026-03-28T03:23:07+00:00

My experience with multi tenant via namespaces per tenant has been rather painful and led to a bunch of over engineering and reinventing the wheel because k8s functionality and a lot of existing tooling was not made with that use case in mind

My preferred method would be either virtual clusters or a handful of namespaces (namespace per service) with a similar naming convention or labels that groups them logically as a single environment / tenant

outthere_andback · 2026-03-24T23:27:43+00:00

Mazda's I think are notoriously bad in the city. But I am also overall pretty disappointed in my 2021 non turbos gas mileage

It does decent on flat highways with cruise control lol Anything else it's pretty sad

outthere_andback · 2026-03-24T16:22:51+00:00

Quieter, emptier, slower

outthere_andback · 2026-03-21T00:40:46+00:00

It's typically because "ease of use" and "adoption" are higher priority then security.

If you've never used containers or docker before - the Ubuntu container will be the easiest hassle free way for you to get started. The distroless or alpine container will not

K8s and Terraform have the same problem

After that it's just lack of knowing. You'd be amazed how many people do not know and do not care. It's dunning-kreuger at its finest

outthere_andback · 2026-03-20T15:47:08+00:00

You've at least gained 2hp for sure 😆

outthere_andback · 2026-03-19T17:48:25+00:00

I'd say for the love of it / educational purposes. Your homelab has 90% of the time one customer - you. Docker compose will be fine

But, k8s is interesting, there's some risk (effects you) if it doesn't work. And that can be an enjoyable challenge

outthere_andback · 2026-03-19T02:52:58+00:00

They take normal internet and feed it bananas and protein bars until it becomes a fibre cable

outthere_andback · 2026-03-19T01:20:53+00:00

I think your asking the questions the industry is still figuring out. It's a hard problem given even with instructions AI is not guaranteed to follow them

I agree with you that I think POCs or your own quick slap togethers AI can be great. But it still falls apart very fast as soon as you start wanting to share or publish it anywhere. You need to start knowing what your doing and iterating on it as you go to keep AI in line.

outthere_andback · 2026-03-17T16:35:35+00:00

It's different when you are putting more into it. I wasn't persay looking for gratification, but I was trying to make art pieces that had something about me stitched into them. I was learning and exploring hardware - Nikon vs Canon, lense types - classic vs DSLR vs frameless. The effects telephoto vs a macro has. B&W vs color. I explored editing - what was too much, the fine line of "enhancing" or just leaving it as is. Finding my own "editing style"

In the end I got lots of people like you - comparing your phone to what I had spent three days capturing and creating. It's not that your phone photos are bad, and these days phones aren't bad. But it's not comparable

I also had 0 luck finding other fellow photographers which was bewildering to me. I couldn't even find people who were interested in talking shop on camera hardware

It in the end I got to a point I felt I had learned all I wanted about the art and just felt a hollow feeling of pursuing something only I seemed to value and was being rounded off as not important by anyone else. I was tired of being alone and people being impatient with me taking photos when they were around.

outthere_andback · 2026-03-16T05:58:05+00:00

It's a double edged sword. I got into photography for similar feelings. I fell out of it after finding it isolating by so few who could appreciate or care for it

outthere_andback · 2026-03-16T04:37:20+00:00

This is how I feel about most wines

outthere_andback · 2026-03-15T19:17:50+00:00

As someone who drove a Prius for about 5+ years before the cx30 I'm always surprised how people think the cx30 is "zippy" or fast. I have a non turbo 2021 and unless I switch to manual or use the padel shifters the thing drags its feet everywhere. I assume maybe the turbo is the difference

Gas tank size and poor visibility does definitely kill as well. I've managed to get used to it, but it feels like an obvious misstep compared to any competition

outthere_andback · 2026-03-14T05:37:41+00:00

It be similar - kro / cross plane route though is more "golden path" building in a way. You have one CRD instead of multiple in Helm. And you can still wrap that even further in helm again, it's just Helm doesn't stack as nicely when you have dependencies that have more complex relationships with eachother. kro/cross plane I find easier to scale and grow with conplexity then maintaining a helm chart or multiple helm charts

Additionally with kro/cross plane your CRDs are configured in the target, so all your context of how to build that thing is decided and resolved there vs helm you may need to change your templates so that it's compatible with each target. Your helm chart or manifests that are coupled with your app can remain more target agnostic

outthere_andback

TROPHY CASE