Nah, he’s telling the news that he didn’t actually do any of this, he was just trolling or whatever. And fair, nothing on the internet should be taken at face value, for exactly this kinda reason. They’re gonna investigate and see if he actually did this or not.

Either that or he had a separate job, and was just a landlord on the side.

You’ve never met an average ASP.NET developer?

I suspect this is because of the looming end of Windows 10. There’s a large segment of Windows users, myself included, with Visual Studio being the only remaining tie to the Windows ecosystem. Extremely smart move by JetBrains, if true.

I mean, I don’t even particularly think it looks bad, not with the riser sections actually being enclosed, but how on earth do you get that to connect?

Please tell me those splitters are just cosmetic and don’t actually work with lifts clipped that far in…

I appreciate the “carrot with a bit out of it” icon.

Naaaaaaaaaahhhhh…

If you’re interested in detail, I can recommend this book: https://play.google.com/store/books/details?id=ncGVPtoZPHcC.

What the actual fuck is this? A constitution neither defines nor repeals laws, it defines rights and powers, of the citizenry, and the government. Is there just more to the story that the article isn’t covering?

I mean, I’m paraphrasing, too.

Even better quote, I love using this one.

“So, with AI writing code for us, all we need is an unambiguous way to define, what all our business requirements are for the software, what all the edge cases are, and how it should handle them.”

“We in the industry call that ‘code.’”

I mean, REST-ful JSON APIs can be perfectly type-safe, if their developers actually take care to make them that way. And the self-descriptive nature of JSON is arguably a benefit in really large public-facing APIs. But yeah, gRPC forces a certain amount of type-safety and version control, and gRPC with protobuf is SUCH a pleasure to work with.

Give it time, though, it’s definitely gaining traction.

#4 for me.

Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.

User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.

Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.

Yeah, you need a way to specify what you want with a high degree of both flexibility and specificity. We have a term for that in the industry, it’s called “writing code”.

Ligatures are a core feature of fonts themselves, even for “normal” fonts, so I quite doubt it.

It’s not that he has to have a residence in New York, it’s that the address that he listed as his residence, in New York, on the application for candidacy submitted to New York, isn’t really his residence. The article mentions other states may follow suit with the applications he submitted to them.

Inside the kernel, even!

My god, this speaks to me.

Is it just me, or does this seem like a reasonable solution? Assuming it’s technically feasible.