TheHarpyEagle

Dude can pry my debugger from my cold, dead hands.

To be fair even the most technically adept person can have tunnel vision where they start digging before ruling out all the simple stuff. Yes it can feel tedious and a little condescending to follow all those steps, but you get humbled the first time it really is just an unplugged cable.

I feel like there’s a specific peak between total technical ignorance and a weary understanding of how fickle technology can be. On this peak is the height of arrogance, where you believe you’ve really got everything figured out. Part of learning is understanding that, yes, sometimes you really did just forget to plug the modem in.

You take that back, python is my homie!

In all seriousness, I freely admit that I’m biased towards python because it was my first language and remains my favorite. I use an IDE for anything but the simplest scripts, so I’ve very rarely had any issues with spacing.

I want to say that stick-built homes are really not so fragile as people seem to think. There’s tradeoffs, of course, and ways to build them that make them uncomfortable at best and blatantly unsafe at worst. That being said, they’re pretty sturdy, fairly easy to repair and modify, and relatively quick and cheap to build.

Thank God freedom units give us the liberty of doing away with that commie nonsense.

I tried it for a moment, made games stutter like hell, switched back. I know I need to go in and figure it out at some point, but it’s hard to muster the energy when X, for the most part, works fine.

From what I’ve seen, it probably has to do with my Nvidia GPU.

I’m learning that I’m just enough of a front end dev to make a very ugly site. Navigating all the various CSS and JS frameworks feels like pulling teeth.

At our company, the person who specializes in that is dubbed Software Architect. Every dev is expected to uphold those values to a certain degree.

But we have antitrust laws and everything!

Back when WB threatened to block the release of a finished series on HBO Max (Summer Camp Island), the creator more or less threatened to leak it herself. I think most devs would feel the same. At least I would. Not like it’s making them any money either way.

Nah, no need for this kind of gatekeeping. Anyone who deals with js and its billions of frameworks on a daily basis deserves to be called a developer.

I had such high hopes for HBO Max as a bastion for animation before they got completely fucked. They nuked Summer Camp Island (a very wholesome, charming, and slightly weird show) right before its final season came out, delaying the premiere more than a year and with zero notice to its creator, Julia Pott. Pott implied as legally as she could that the season would get out there one way or another, so either someone at CN has a heart or her threat worked.

And to this day they deny that Summer Camp Island, OK KO, Infinity Train (one of CN’s top performing shows!), and others even existed, while cutting funding for even more shows. I’m still devastated, we had a beautiful revival in the 2010s, but now there’s barely anything new on at all. So many up and coming creators utterly shafted no matter what network they work with.

All we really have left is Prime and Netflix, and god knows those aren’t reliable. What a mess…

It’s actually really fun to compare the pilot with its equivalent episode in the show, cool to see what little changes they made.

Important to note as well that both Edge and Opera along with Chrome (and many other niche browsers) are based on Chromium, giving them an even bigger spread of users that are using the same browser from a compatability standpoint.

Indeed, I hate it when people are like “you shouldn’t pay that much, you need to shop around”. Assuming you even have multiple hospitals to choose from, tell me you don’t get “I don’t know” 9/10 times when you ask about the cost of a procedure.

It’s pretty confusing, but basically your insurance won’t cover much until you meet your deductible for the year. After that, your coverage depends on the policies of your insurance company. Some stuff may be totally covered, some partially, some not at all. And there’s really no way to know what costs what until you get it done.

For your vector issue, I’d go the route of some static examples if possible. Do you have a way to manually work out the answer that your code is trying to achieve?

For side effects, that may indicate what I referred to as tightly coupled code. Could you give an example of what you mean by “side effect”?

For unit tests, you should know the input and expected output from the start. Really responsible devs write the unit tests first, because you should know what you’re going to put in and what you’ll get out before you start writing anything. If you find yourself making the same mistakes in your tests as you do your code, you might be trying to do too much logic in the test itself. Consider moving that logic to its own testable class, or doing a one-time generation of a static set of input/output values to test instead of making them on the fly.

How granular your tests should be is a matter of constant debate, but generally I believe that different file/class = different test. If I have utility method B that’s called in method A, I generally test A in a way that ensures the function of B is done correctly instead of writing two different tests. If A relies on a method from another class, that gets mocked out and tested separately. If B’s code is suitably complex to warrant an individual test, I’d consider moving to to its own class.

If you have a super simple method (e.g. an API endpoint method that only fetches data from another class), or something that talks with an external resource (filesystem, database, API, etc.) it’s probably not worth writing a unit test for. Just make sure it’s covered in an integration test.

Perhaps most importantly, if you’re having a lot of trouble testing your code, think about if it’s the tests or the code that is the problem. Are your classes too tightly coupled? Are your external access methods trying to perform complex logic with fetched data? Are you doing too much work in a single function? Look into some antipatterns for the language/framework you’re using and make sure you’re not falling into any pitfalls. Don’t make your tests contort to fit your code, make your code easy to test.

If ever you feel lost, remember the words of the great Testivus.

deleted by creator