I’m mostly joking, but most of what I code lately is integrations and data tools where 90% of the thing is configuration and lining up different tools.

It’s a lot of load data form yaml, build json, throw that into a tool and the build a report kind of glue. I’ll use pydantic and stuff where it makes sense, but I’ve been spending a lot of time lately between lua and python and javascript.

I used to do more system and engineering stuff which actually required a lot of planning, but that’s just not what has paid the bills for me the last few years.

but we still get that tech debt sprint?

And halfway interesting means beyond a medium blog written by someone with 3 months experience trying to pad their resume, and not following standards beyond default linting rules at all

Lately my approach to dev is “I don’t care about your language feautures, I’m going to treat it like lua and just stuff objects with data and write bare functions to process them”

Unless I need to engineer something complex, everything is dict[any:any].

I’m sure you’ll get a sprint to clean up the tech debt and a pizza party. Management promised!

That takes me back

I’ve been party to dumping legacy systems and lift & shifts a few times.

Good fucking luck.

Knowing nothign about this, a project like this would take at least 2 years even if you are dropping a ton of use cases and dependencies.

I’ve been trying to pair down my extensions, so I’ve been using ale’s fixers to do formatting.

I’m not a huge fan though, I’ll probably go back to vim auto format.

The first symptoms include talking about dots and arrows with no interest in archery, and discussing associativity despite not associating with friends.

Advanced symptoms include casually perusing the Wikipedia List of Lists and Category of Categories pages.

That History section is exactly what happened to me

I’ll have to see if there’s a nvim equivalent, or if I can make my own

I used to have my vim set up to trim excess whitespace on write.

I had no idea how many errant diff’s that would generate, I had to turn it off.

I can already see the 10,000 line PR touching 50 files and the sole review comment “👍”

Sweet dreams are made of exes Who am I to deprecate? I travel the kernel and the seven seas Everybody’s looking for something

Some of them want to use you Some of them want to get used by you Some of them want to abuse you Some of them want to be abused

Sweet dreams are made of this Who am I to deprecate? I travel the kernel and the seven seas Everybody’s looking for something

I’ve always stayed away from tree algorithms

Is this how duck typing works?

That works, thanks

So it was a probably shitty external HD… that’s a whole other can of worms

Can you screenshot or something? I can’t load that link

Are you telling me there’s a difference between an inner and a cross join?

Cross join is obviously faster, I don’t even have to write “on”

I have when a misconfigured spark job I was debugging was filling hard drives with tb of error logs and killing the drives.

That was a pretty weird edge case though, and I don’t think the drives were melting, plus this was closer to 10 years ago when SSD write lifetimes were crappy and we bought a bad batch of drives.

Holy shit if this ids lm issue that’s too funny