I'm trying to stand up a docker container to read a storage queue with dotnet and invoke ffmpeg to convert some videos. For a whole day I fought with this wrapper (FFMpegCore) which kept throwing file not found errors on the ffmpeg binary itself. Locally (windows) it worked fine.

I spent a ton of time trying to install the Debian package, trying to add it to the path manually, trying to just use the wrapper just to generate the arguments I wanted (I'm not an ffmpeg pro, so the fluent API the wrapper has is super useful) and running it manually, nothing worked. Finally, I realized it wasn't getting to the part where I ran it manually: just using the fluent API to get the arguments was invoking ffmpeg and throwing.

I took away the wrapper completely, start ffmpeg manually and it works...

Ay carumba. Things just can't be easy.

Damn it, why does the power company not use their notification system for planned outages?

Ugh power's out.

Luckily it's pretty warm out so we're not suffering. I'd normally have a fire going but my fireplace is out of order.

I hauled in my portable generator in the hopes that if I was well prepared the power would come back on and it would have been wasted effort but I may end up running it later to cool down the refrigerator and maybe charge a few batteries.

Hopefully I have power by morning or I'll have a hard time getting our services deployed...

Anyone learn about Bloom filters in school? I was watching a lecture and he mentioned using a Bloom filter with a few hash functions to create a cache you can use to avoid querying a table if there's no match, which is a neat idea. I've never heard of this but I also didn't study CS in school so I'm curious if it's common knowledge.

I feel like being a doctor is like being a contract dev. You're thrown into a bad situation, you know the stack but you don't know the project history, best practices aren't followed, and the only dev is also the primary stakeholder who learned everything he knows from w3schools.

YouTube: new rap video?

Me: menu > not interested.

Later...

YouTube: new rap video?

Me: menu > not interested.

Later...

YouTube: new rap video?

....

I get gold from YouTube's algorithm sometimes, but it should know by now that I couldn't care less about new rap videos.

The MS Teams SDK is bullshit. It's so half baked and comes with instructions like "you'll probably want a better implementation for production, good luck cause you'll have to write it yourself."

Oh and don't forget to cache your installations in a file called "notifications.json"

Deploying will create 2 app registrations (OIDC) and about 6 resources in Azure... But "you'll probably want to log to app insights in production"... So I hope you're very familiar with Bicep cause you'll have to figure out how to add that to your template properly and there are about 7 Bicep files to decipher and it doesn't create an app insights out of the box.

Probably written by an intern.

Be interested. Try to do whatever you're doing the best way possible. Do research, keep up, roll with the punches, and don't take things personally. If you like being a dev, it should be easy to find the fun in it.

Why is the bar so fucking low in this field?

Razer + Windows = haxxed

https://google.com/amp/s/...

Clearing the backlog before the sun explodes.

I just think about Microsoft and Apple and how fucked up their shit is and it makes me feel better.

Screaming and stomping and jumping and shaking the whole house from my wife and children.

Manual serializer. I've found some of this in our code and wonder who could be that insane.

I took a web scraper that took several hours, made it multithreaded and got it down to about 15 minutes. Pretty satisfying.

Spent the day figuring out how to maintain injected dependencies in scope when they're requested asynchronously later in the pipeline and then be able to clean it up later without having any lifecycle hooks to use.

Seriously considered switching DI frameworks before I just added an event when it's OK to dispose of the scope and I think it's finally working (without the memory leaks it had before).

Who else has to try something every possible way before you can be satisfied?

I've mentioned this before, but I never really understood bit flags until I tried out Cocos 2D and read about how you implement hit detection. You identify different rendered objects with an enum value, and it would spit out a result every frame that you use bitwise logic on with the enum to determine which objects were touching. Such a simple and elegant way to represent combined state.

It may be elementary for some folks but I was not a CS major.

I had to make an account for my kid's school.

Last night I start. I put in a username, then it has a quality meter for the password. I put one in and it goes to like 90%. Ok, fine. I submit and...

Validation error on the username field. Message? [object Object].

Try all different kinds of username: no numbers, all caps, etc. But no luck so I give up.

Today I try again and get stuck again. Then I think... "Maybe the devs suck worse than I think..."

I change the password so that it's rated 100% and submit... Success.

Fucking devs.

Spent the day migrating to a different mocking framework for our unit tests.

Still a few hours of work to do until they'll all compile.

After that, who knows what'll still need fixing.

Pouring myself a tall one.

Self reviews. They're stupid and people aren't good at it.

Just tell me how I did.

Your dumb post passes!

var result = qualityService.Evaluate(yourDumbPost);
Assert.IsFalse(result.IsFunny);
Assert.AreEqual(Wittiness.BelowAverage, result.Wittiness);
Assert.IsNull(result.Value);

Why are these SAMPLES NOT WORKING!?

It's supposed to just be reading and writing OAuth2 tokens from session.

I'm THIS CLOSE |__| to getting things working and I had to leave work. The fucking worst.

On the bright side, I think I finally understand how OAuth2 works. I need to write an article that actually explains it properly because I've had to read dozens to get a good grasp on it.

When your users are this dumb, it's hard to decide between making things obvious (but inviting potential errors) vs. adding a step to reduce the chance of errors (but potentially confusing people).

It would be easier if people actually read release notes...

I'm tasked with a light redesign of our public site and it's a fucking shit show. It's using this old-ass grid system with pixel-based widths and it's just totally fucked and whoever put it together had no clue.

...I keep going back and forth between trying to work around it and unfucking it because, while I'd like it to be unfucked, I don't want to spend all week on this and I hope we toss it all out and do a proper full redesign in the next year or two anyway.

Not letting Google (overtly) use your data has its drawbacks.

For example, lately I've been getting senior dating ads in my Gmail app.

I mean really, Google, I know you know I'm 30 and married; who's kidding who?

Tdd isn't very effective if the spec keeps change as you work.

I was trying to be good and write tests as I went, but it just ended up taking twice as long since I had to keep rewriting the code AND the tests.

Tonight was my first experience with bazel.

It seems cool, but I still haven't gotten anything to work yet and it's been about 4 hours.

It hasn't helped that it doesn't work too well on Windows.

A colleague of mine was very smart, but didn't know how to use classes in .net or object literals in js, so he organized his data with arrays.

It worked, of course, but, god, did I hate working with his code. It would take hours to make simple changes.

C# Collection class had me pulling my hair out for hours the past two days.

With a list, you can do new List<T>(IEnumerable<T>) and it creates a new list with the contents of the parameter in it.

With new Collection<T>(ICollection<T>), however, the new object is a reference to the parameter passed in.

Is it just me, or does that seem fucking bonkers?

Dev DB just auto shutdown in the middle of a restore.

From an online backup.

With NORECOVERY.

Shit.