not at all. it's used for configuration and stuff. having a lot of it can be a real bummer depending on the context. like a puppet config or perhaps a super weird docker compose setup. I've never heard anyone complain about the markup though. it's like blaming json for a crap api or something or idk blaming the coffee cup for burnt coffee 🤷
Wow that's... exact.
Mannnn. Outer Wilds is so freaking good. I had put it off for a while, but then last year I decided to go through it. It managed to be the perfect game at the perfect time. Raw intrigue and fascination turned into somehow helping me cope with the loss of my sister and dad who I had lost very recently at the time.
I guess it would be doable by trying to write a bunch of wrappers around engine specific stuff, but holy shit development would be... ugh. Slow and ultimately a confusing mess to maintain still
God. Him face planting into a rock in the background utterly slayed me 🤣
Huh... now that you mention it, I guess that's what people like Bob Martin and mpj (along many others of course) might classify as. Would any guru fall under this category?
Oh I like the work item number idea. We've been putting in a line to explain why the change is being made. Being able to link directly to a card or something is noice.
Holy shit can confirm. Am also fighting off some burnout or depression or both?
Get called out for being slow, yet their "fast" development time seems to be related to the projects we have to keep revisiting as they keep failing publicly 🤔
Like yea it needs to be delivered, but do we really want to be so careless with employee and customer trust? Also, wouldn't there be value in keeping things structured well enough to be consistent with our delivery times?
I get that it can be polished later but later never seems to come. The tech debt just keeps stacking and I find myself being the only one scraping up the turds.
I feel like I'm being gaslighted sometimes...