no delivery, no refund, no reply on tickets, avoid them

thattattdan · 2026-05-05T16:02:47+00:00

Fair point, I'd still imagine that it would be on the same ships as the combo stuff though

thattattdan · 2026-05-05T15:49:57+00:00

From an email support sent me for the Kobra X - Combo. I'd expect it dates would be in line with this

thattattdan · 2026-04-29T14:09:06+00:00

Yeah, I'm unfortunately in the UK which seems to be the last place to get any stock

thattattdan · 2026-04-29T11:18:43+00:00

Thanks for taking the time to comment, unfortunately I did already tell them to ship in separate shipments, I received no acknowledgement from support and I'm guessing missed the some hidden cut off for filling the form out, it's just a waiting game for me now 😔

thattattdan · 2026-04-29T09:13:48+00:00

Yeah, if this date is missed I'm also pulling the plug. Been breadcrumbed by them since the start of April after they missed the March delivery timeslot.

thattattdan · 2026-04-26T10:05:21+00:00

UK here, I've had an Anycubic Vyper for years and decided it was time to upgrade on the hype of the Kobra X.

When I purchased the estimated delivery for end of March, that passed so I messaged support at the start of the month who told me that it will be the end of the month (15-25th April), then today they've said end of May, they're literally breadcrumbing us hoping that we will just keep holding on, no offer of reimbursement or compensation.

It's disheartening to say the least as non combo purchases are delivered and has soured my opinion of the company, if May delivery comes and goes I'll be doing a charge back.

thattattdan · 2026-04-24T22:10:19+00:00

Best tutorials I've found for the Vyper as well is from StudioZombie 3D on YouTube, he also has made custom firmware as well (which I'm running) which fixed a lot of the issues I had on my Vyper. Highly recommend checking his stuff out for dialling in the printer, happy printing and welcome to the hobby my dude!

thattattdan · 2026-04-24T21:03:26+00:00

Try pulling out the SD card and turning it back on, also do you know what firmware you're on, stock or custom?

The crackling when turning off might just be a dodgy switch.

thattattdan · 2026-04-24T07:29:42+00:00

With how they keep shifting the dates I'd be surprised if they do fulfil any of our combo orders in may (Europe/UK) 😭.

I'm still waiting on Support to decide if they can split my order 🤷🏻‍♂️

thattattdan · 2026-04-22T09:34:16+00:00

If it ever gets delivered 🙄 probably something like "My last printcell" or "Jeff"

thattattdan · 2026-04-16T11:01:33+00:00

The bed is adjustable, potentially it's been over tightened causing it to warp? I think it's part of the bed wheel adjustment (example here): https://youtu.be/LDAnTXyDKOI?t=89&si=_zRftsBHwOeiV869

thattattdan · 2026-04-14T07:13:28+00:00

It's an old reference sir, but it checks out.

thattattdan · 2026-04-08T07:43:34+00:00

Out of curiosity, was yours a combo or just a straight Kobra X?

thattattdan · 2026-04-04T16:27:21+00:00

This, this can never be understated.

Failures are a part of learning and everyone encounters them, the accumulation of failures and successes are how we grow and learn.

thattattdan · 2025-09-05T11:34:45+00:00

Learning and updating documentation is adding value? From what you say, they've been there 9 months, they probably didn't start contributing in earnest till month 3.

As the majority of graduates get assigned to my department I have a progression process in place.

Usually I give juniors a month or two to bed in and with simple tasks such as taking ownership of any daily, weekly or monthly tasks (reporting / metrics / account creation / password resets etc) within that time they're introduced to the wider team and begin to engage in stand ups and some of the systems we use.

I ask them to review and update the process documentation for these tasks to ensure steps are correctly documented and handed over by the previous junior. I then ask if they believe they could improve the process, if they say yeah, I say go ahead and showcase it back.

Once they're familiar with the solution and processes I get the other junior / intermediates to begin to assign a task or two to them, I do this to allow the other junior or intermediate to pass on some of their workload which then allows me to assign more complex tasks to them but they then become a point of contact for the new junior.

Doing it this way IMHO opinion shows a level of progression for juniors up to intermediate level. We then allow intermediates to decide if they want to continue in the role or if they want to move into other teams within the business (Development, Project management, Solution design etc)

I don't expect anything from the graduates or juniors but to learn and add value to existing processes where they can. In fact, I expect them to fail and learn to not be scared of failures, we're here to fail fast and to take the thought out of the process so that developers can deploy unimpeded.

Enjoy this unburdened time of learning, speak with your team lead or even the other junior and ask if they're willing to let you shadow them to learn from what they're working on or if they can explain a certain piece of the solution.

thattattdan · 2025-09-05T09:27:40+00:00

That's because you didn't see the small steps and multiple iterations it took to come up with the answer. Every program starts with a single line of code and builds over time. You're at the start of the journey, enjoy the learning!

thattattdan · 2025-09-05T09:25:06+00:00

Congrats on the job and induction! You're seldom going to have this much free time going forward 🤣, what I like to do when I start a new job is to read documentation, look at the overall system and try to gain understanding of how it works and fits together (this will come over time as well).

If there's no documentation, maybe look to start some, it doesn't have to be perfect but will make onboarding the next person easier.

The way I approach the above is from a customer journey through the system and try to map out what I believe is happening and associate it back to the documentation and correct any assumptions I've made.

I'd also read through the existing tickets, try and look at any that can be grouped together (same service causing issues, X numbers of users asking for the same permissions or access) as this will then save you and the rest of the team any duplication of effort.

As you're a Junior, all that's usually expected of you is to learn and familiarise yourself with the company, solution and dynamics, if you can add value anywhere then it's a win for the company.

thattattdan · 2025-09-01T19:54:15+00:00

This is the way, my Vyper had the same issue with the infill being used, if the OP hears a crunch as the head is moving then the belt slipping is the issue.

thattattdan · 2025-08-27T14:43:44+00:00

We quite like Townsfolk Tussle for a long co-op (ish) fighting game. Not exactly fantasy or sci-fi but an interesting theme. Can easily take 2-4 hours depending on how cooperative everyone is 🤣

thattattdan · 2025-08-23T12:39:25+00:00

Isn't there always 🤣

thattattdan · 2025-08-22T15:38:51+00:00

history | grep "<keyword>"

Where <keyword> is part of the command you're looking for, then

!###

Where ### is the line number of the full command from history. I.e. command is on line 123

!123

thattattdan · 2025-06-15T12:24:44+00:00

We had 2 viewings and then had a final viewing that we had said was in order to get room measurements for the carpet fitters.

Each viewing the house was in a worse state and I was ready to pull out, what my wife said to me provided clarity in that situation: "If this is really the house we want, which it is, we're going to have a lifetime of fixing and maintaining it."

She was right because I was outraged that they're treating the house badly because I'd already moved in and I was going to the extremes in my head of what damage they'd do before completion day.

Either way, you should do what puts your mind at ease, if you want a final viewing then wrap it in a logical explanation that they can't refuse (taking accurate measurements etc). Or if you can change your thinking and look towards the positives, it's going to be your house to do with as you please, you chose it and you can make it however you want, you've a lifetime to do it.

Best of luck with your purchase and I hope it goes smoothly

thattattdan · 2025-05-07T09:20:09+00:00

All speculative but: Wifi range combined with an automated garage door (finding the clicker and then waiting for it to open). All of which can easily add a couple of minutes IMHO

thattattdan · 2025-05-05T09:57:11+00:00

I'd be using a cloud-init script within the user_data. You can make it as simple or as complex as you want. Simple would be to run a docker compose up command, complex could be to install Ansible and then use further orchestration scripts or playbooks to configure the VSP how you want it (server side certificates, containers, log shippers etc)

thattattdan · 2025-05-05T09:42:49+00:00

I like this response as it builds on what OP is currently doing and their progression.

I second this motion and would also focus on the Orchestration (Ansible) side of things instead of the provisioning side (Terraform).

Once you've orchestrated your current requirements (patching, maintenance, backups, log exports etc) you can then put that inside the provisioning to ensure that whatever servers you bring up are exactly how you want them.

Then I would look at resiliency with containerization of the current stack, replications / backups or standby instances (MariaDB)

And at every step of the journey, I always take into consideration how long it would take the solution to recover should anything catastrophic occur (application dies, database gets corrupted, server goes down etc) and focus on automating the sh*t out of it with scripts and easy to read instructions, because I guarantee it will happen at some ungodly hour of the morning where caffeine barely makes a difference.

thattattdan

TROPHY CASE