boring work stuff, they entered wrong data and made a ticket to fix it several months after the fact. That data they enter is the input for a bunch of calculations, so cleaning up that mess is a lot of work and I’m the only one equipped to do it. They should be well aware of the importance of being exact with what they enter and only signing off on it when they’re 100% sure it’s correct, yet they keep messing it up. They made a stupid excuse about having to sign off on it even though they knew it wasn’t 100% done, when it’s been made perfectly clear that this is unacceptable regardless of circumstances because of legal ($$$$) ramifications

edit: I should add that those ramifications are potentially severe enough to bankrupt us. That particular administrative body does not fuck around and will tear us a new one if they smell blood

today, I used the word negligent in a work email. They done fucked up and I’m tired of their shit

catch(error) {
  // todo
}

doesn’t sqlite explicitly encourage this? I recall claims about storing blobs in a sqlite db having better performance than trying to do your own file operations

you know what I do like me some mechanical keyboards but I recently switched back to a run of the mill scissor switch keyboard because I think I like low profile keys more. Now I know there are some low profile mechanicals out there but I’m not sure I care enough to spend the money to get one. I think I’ll give this one a go for a while, maybe I’ll switch back later

I’ve done worse

my wife was having some problems finding the right W11 drivers for our Brother HL-2030 and dared to utter the thought of replacing it

I shut that down right quick

a) you don’t have the ability to understand what the client actually needs

the client doesn’t understand either. This I have had to learn to accept and not blame the client for, it’s OK and we’ll figure it out together

b) if you over-architect your solution

we can’t figure out what we actually need by overarchitecting something to death. If and when you find you’ve coded yourself into a corner because you didn’t architect well enough 6 months ago, then congratulations it seems like what you’re doing is good because you’ve made enough progress to actually need a better architecture

obviously I’m oversimplifying and people more experienced than me understand better how to walk the tightrope between unmaintainable spaghetti and an overengineered mess, but me, I try to keep shit as simple as possible because you never know

the java VM itself is actually pretty damn fast, sometimes even faster than native code because it can optimize code paths while it’s running

applications built with it tho, I’d say hit and miss but honestly we all know it’s a miss most of the time

you might not be testing your code, but it is always testing you

that’s a crime against humanity

it has a lot of cruft and gotchas and lacks a good standard library (which is why npm is a thing). That means there’s a lot of bad javascript code out there and a lot of people who have had bad experiences with it. But, if you take care to not shoot yourself with the included footguns and you know your way around npm, it’s a perfectly fine language for its purposes in front- and backend development IMO

repeat bottom panel and you get pretty close IME

const a: any = “You have no power here!”

yeah well NPM, it’s either this or I nuke the very ground you’re standing on

exceptions are just fancy gotos

well of course it is!

int variable => local scope => my int from the perspective of an instance

static int variable => class scope => our int, for all instances of a class