I’m a staff software engineer at Sunrun, the USA’s largest residential solar installer.

I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.

  • 2 Posts
  • 430 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle

  • I’m honestly astounded at how many people are suggesting Mint. I recently switched full time to linux and even as a software dev, Mint has to be one of the worst experiences I’ve had with a computer. Not only driver issues, but software issues and general buginess. Along with being butt-ugly, I do not think any windows user is going to confuse Mint for Windows.

    I switched my wife to Bazzite (not necessarily recommending that) and she literally didn’t notice it was a different operating system (even though I told her it was and walked her through it). Bazzite has a nice UI for installing pretty much anything a normie would be thinking to install. The only issue we’ve had so far is that Dropbox just outright does not work on it. I’ve filed a bug with them and have been awaiting a response from their dev team for like two months now. I’m sure they’ll fix it eventually, but if you need the Dropbox UI (you can use rsync otherwise) then don’t choose Bazzite.

    As for myself, after trying out like 6 different OSes, I settled on CachyOS. There are still issues, but it’s pretty dang stable and they’re very fast to fix issues. It’s not for a person not willing to touch a terminal at least once though.







  • Anything but the last one. Don’t duplicate the http code in the body, else you’re now maintaining something you don’t need to maintain.

    I’m not a fan of codes that repeat information in the body either, but I think if you had used a different example like “INVALID_BLAH” or something then the message covered what was invalid, then it would be fine. Like someone else said, the error data should be in an object as well, so that you don’t have to use polymorphism to figure out whether it’s an error or not. That also allows partially complete responses, e.g. data returns, along with an error.







  • It’s also just a huge fallacy. He’s saying that people just choose to not write memory safe code, not that writing memory safe code in C/C++ is almost impossible. Just look at NASA’s manual for writing safe C++ code. It’s insanity. No one except them can write code that’s safe and they’ve stripped out half the language to do so. No matter how hard you try, you’re going to let memory bugs through with C/C++, while Rust and other memory safe languages have all but nullified a lot of that.