techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#ado

5 posts5 participants0 posts today

I would've loved to share photos of the Ado concert but I saw multiple people kicked out for having their phones out. Literally, no phones allowed once you entered the arena proper. They are VERY serious about protecting her identity.

It was a great show. She seemed to be obviously worn out during the first half of the show - her voice work was not her best, likely because she's just exhausted at this point - but the performance was still captivating, and she brought a ton of energy, as she does. We even got some very heartfelt words from her in English (and jokes about Starbucks)

So glad I got to see her live. What an experience!

EDIT: She deserved a better venue too. Tacoma Dome acoustics suck ass and the stage was very limited

#music#live#Ado

Soooo many of the people I work with don't know how to use the #git CLI to quickly extract data from a repository's logs.

I was given hours on a project that I contribute to on an "every few years" basis. Most recently, their automated build had stopped working. When I checked the (
#ADO) logs, I found an error message that I wasn't really in a place to do anything about. So, I asked them to open a support case. They eventually did so and the #Azure support person pointed out a bug in the script (I originally wrote the script but the bug was introduced a year+ after I'd turned it over to them). The person working with Azure's support fixed the bug and the automation returned to a functional state.

Since all of the code is managed in git, I asked, "can you check when the breaking-change was made". I got a "that's going to take me a
while to do." I was a bit perplexed by the response, as it's a task that takes not much longer than it takes to type in a simple git log-search command. I have to assume that dude was planning to pore over the entirety of the git logs — and/or all the deltas between today and when the code last functioned — and try to snuffle out a change. I'm further assuming that whoever made the breaking-change probably didn't include the change-information in their commit-log (this site ain't great about ensuring that commit messages are meaningful/useful). All in all, very much a "no, dude: just use the git client's native search capability".