tiredofsametab

gRPC does not use HTTP status codes. I meant that I might be making a similar mistake with gRPC status codes though, after checking just now, not so much (there are only 17 total codes, not all of which apply to my APIs).

Yeah, I know how http status codes work. I just followed the existing pattern at my current place with gRPC and this post made me realize I don’t know most gRPC error codes and best practices.

Assuming there was some API key system in place, could just check on the key to see if it belongs to one of those clients. If yes, 200. Else, real APIs.

I looked into it once at my last company, but none of us knew it and we had a tight deadline. For our scale and usecase, it definitely seemed like needless complication for most things compared to any payoff of switching.

me with gRPC error codes: nil, parameter error, app error – OK, you fucked up, we fucked up. Edit: forgot NotFound.

I really should read about the various ones that exist at some point, but I’ve always got bigger fires to put out.

Edit, since it seems unclear, gRPC != HTTP and does not use the same status codes. I meant that I felt like I was using fewer than I should, though I just checked and basically not.

if it doesn’t have both _draft and _final in the name and at least one (1) in it, are you even really versioning?

India is the one that I know of that differs in some way. I’m sure there are more.

It’s… Beautiful.

step 1: unsafe fn()…

Now call that C program from some other program in another language.

This is why I love test coverage and metrics (though there’s always the chance jimbob from accounting calls it once or twice a year).

I inherited an old Japanese codebase. Tons of stuff was just single-letter variables. Apparently, this used to be at least somewhat common here. I spent a lot of time just updating code to replace vars with something meaningful (and found bonus bugs due to improper scoping with same var names as a bonus). Didn’t have an IDE that would easily do it for me at the time and running something like sed felt too risky.

I split the middle with en-JIN-iks (which is how I heard it said long before I saw it written)

I’m referencing this, but I’m not actually sure: https://www.ssa.gov/OP_Home/handbook/handbook.14/handbook-1401.html

I can’t read plain-text, uncoloured HTML

That’s all we had back in the day. The only difference that jumps out to me is having attributes, but that’s still not that crazy. Even back when I did web stuff, I used notepad++ without any particular higlighting the vast majority of the time for plain HTML (though not JS).

As the user posted, one human can have more than one SSN in their lifetime. Many humans will never have an SSN. Some of those humans may have a TIN. Some humans may have at least one TIN and one SSN at some point.

I begrudgingly switched to vscode a few years ago. I’ve never had any issues like this with it. My only issues have been with a plugin that I installed optionally (and that was later fixed by the plugin author).

As someone who speaks conversational Japanese (well, probably more since I do banking, doctor, etc. on my own, but my grammar is far from perfect), and fluent English, Google’s AI can make some… questionable choices when translating at least. My wife (fluent Japanese speaker who knows a little English) and I decided to play with its translator function when I got a pixel phone and once again a bit latter trying to come up with some English practice for her.

Japanese is definitely a bit more difficult to work with since it’s so context-dependent and has lots of homophones (one reason translating things into Japanese and back can be interesting, particularly in the older days of Google Translate). It’s fine for short, concise, and non-complex sentences, but even certain formal grammar and honorifics can be bad with the AI translation services.

People can pull <table> from my cold, dead hands.

(though I’m usually only using it to display some status just for me and not for external consumption; the UI side can have a JSON if it ever comes to that).

I used to be a full-stack dev, but I’ve been pure backend for so long now, everything I knew is outdated or deprecated.

I physically reacted to this post with a combination of disgust, anger, and fear. Do tests. All of the tests. Randomize the order in which your tests run. Cover all branches.