TechIsCool

Since the monitor I was working on was CRC32ed I could have patched the version numbers forward. For all intents the monitor thought it was upgraded a minor version. It just uses a CONST for the actual version number within the build that I didn't change. It read the version from the zip file name which seemed less smart all things considered.

I love reading about these types of firmware "bugs" fixed by AI in a few minutes with the correct context. I recently patched my LG monitor that had a blinking white LED in standby. Why any designer thinks why yes lets blink this 1 second on 2 seconds off when I go to sleep is deranged.

Well now I can sleep easily because of the same style of patch. I also hit the version refusal but found that you just lie to the upgrade tooling that it's newer and then the version number doesn't change after flashing.

I think the rotating photos create a poor UX. The purpose of this layout it seems is to let users view the images carefully and study the details, but the slideshow effect makes that difficult.

I agree, 2-3x pricing because you have more people always felt like a cash grab, similar to an SSO Tax. We also have a lot of complex Pagerduty configurations and their APIs are painful. Why do timestamps drift, templates get updated but don't show drift, and identifiers are not the same between UI and API. I regret implementing within Terraform and would rather just let teams manage their own on-call sadly.

Feels like a sales pitch only due to the abstraction of Provider A,B,C vs actually naming the products. Guess thats what you get for a vendor blog.

At the GitHub Enterprise level, you can see that reflected if you look at any of the users profiles https://github.com/mghaught

This collector is one of my favorites to ask Copilot Agent to use for validation when the stack is missing tests. You give the agent a couple well written prompts of what you expect to happen and since the app has distributed tracing enabled. all logs flow to text and are consumable by the agent.

I am not shocked by this, as I have asked for writing a support case about AWS SCP and it wrote it in the style of the scp-wiki. I got a good chuckle out of it and wondered if it made sense to add it as a joke to my default prompt.

Didn't we hear this tune from Sony in the Playstation 3 days with Developer mode and then it slowly faded away after a couple years of application/product releases...

I am surprised that the use of a messaging queue through MQTT is considered a misuse of their technology when in reality it appears that the other application just was using an internal API that could change without notice. I also could see how certificate based authentication could be viewed by some as a time based expiration on the firmware.

I love dive and its something that I use in my tool kit multiple times a month.

I am curious if anyone knows how to get the contents of the file you have highlighted, a lot of the times I use dive to validate that a file exists in a layer and then I want to peak at it. Currently I normally revert to running the container and using cat or extracting the contents and then wandering into the folders.

Agreed, the snapshot does output a message in the logs but based on our conversations with AWS it was suggested that we use the SQL Command to determine the LSN. Sometimes depending on revision you won't get the logs and other times the log line is emitted twice based on the internal RDS consistency checks. Makes me long for GTIDs from MySQL MariaDB Galera[1]. They worked super well and we never looked back at my last company.

[1] https://mariadb.com/kb/en/using-mariadb-gtids-with-mariadb-g...

Yeah its been nice to leverage this while working on some of our larger multi TB non-partitioned clusters. We have seen snapshots restore in under 10 minutes across AWS Accounts (same region) as long as you already have one snapshot shipped with the same KMS keys. We have been upgrading DBs to lift out of RDS into Aurora Serverless.

If anyone here knows how to get LSN numbers after an upgrade/cluster replacement. I would love to hear about it since its always painful to get Debezium reconnected when a cluster dies.

With the mention of AWS RDS and Aurora, I am curious if you had thought about creating a replication slot, adding a replica to the cluster and then promoting the replica to its own cluster. Then connecting the new cluster to the original with the replication slot based on the position of the snapshot. This would save the large original replication time and also keep the sequences consistent without manual intervention.

Site Reliability Engineer (SRE), DevOps Engineer, Systems Engineer

Location: Clinton, WA (Greater Seattle Area)

Remote: Yes (preferred)

Willing to relocate: No

Technologies: Linux, AWS, Docker, Golang, Ruby, Chef, Bash, Ansible, Teamcity, HasiCorp [Vault, Consul, Terraform, Packer], Prometheus, MariaDB, Galera, jMeter

Résumé/CV: https://www.dropbox.com/s/jn5z4lgwtiwffng/David%20Beck%20Res...

Email: techiscool+hn19@gmail.com

Github: https://github.com/TechIsCool and https://github.com/Techcadia

Linkedin: https://www.linkedin.com/in/david-beck-7824a4b7/

Strengths in Linux and Windows automation, tooling and deployments. Seeking a challenging position supporting complex Infrastructure.