I mean if you don’t like camp, maybe. If you do, then this movie has some big shoes to fill!

What are you suggesting then?

barf. barf barf barf barf. wtf!!!

Above and below the page/plane is the z-axis.

But some people “hold” the page up in front of them, or down on the table.

Ds9? I don’t watch shows anymore, though I like remembering it

The underwater episode is great though, tbf

I certainly wouldn’t know what this could possibly be referring to since I’m on a yacht and have just taken some very powerful amnestics. As far as I know I’ve never been on the internet.

There are a bunch of people here wearing baby masks. They all have hammers, which is odd because as I said we’re on a very large (expensive) yacht.

It’s the bear all over again innit

Why do you assume the least charitable assumption? It’s good advice in appropriate contexts

Yarrr, I might take a gander

You could also just show up to a board meeting or similar and keep pushing them to the ground until they stopped trying to stand up, then tell them to give all their money away or you’ll just keep bullying them in increasingly humiliating ways.

i mean it depends what the job is for

“Thanks for your time, but this job isn’t for me. I wish you good luck finding your candidate, though.”

You’re going to want to follow the “campsite rule” everywhere you go, and also sneak in positive refactors into your feature changes (if business is not willing to commit time to improving the maintainability of the codebase).

Read up on good software design principles. I don’t know you experience level, but for instance, everyone agrees that appropriate abstraction, and encapsulation make code easier and more enjoyable to work with, and will let you run tests on isolated sections of the code without having to do a full end-to-end testsuite run.

Having tests that you trust, especially if they execute quickly, will increase your “developer velocity” and let you to code fearlessly–knowing that your changes are reasonably safe to deploy. (Bugs and escaped defects will happen, but you just fix them and continue on.)

Good luck!

The fact that documentation and comments can’t “fail” if the underlying code changes is a real problem. I’ve even worked at places which dictated that comments had to go directly above or even beside (inline) with the code they were explaining, so they would show up in any patches changing the code.

What do you think happened? Yup, people would change code and leave the outdated (and wrong) comment untouched, directly to the right of the code they just changed.

Hell, I was one of those people, so I get how it can happen.

omfg that’s over 1 MILLION characters 💀 💀 💀

vomit

Translation: please help us understand our codebase. We’re paralyzed by fear.

Nice!!! I actually just submitted a technical takehome, so🤞they liked what Ruby I could remember.

Is your technical oral, live coding, or takehome? Feel free to PM me if you want someone to bounce ideas off of. I’ve had some experience in all of them.

Not just expensive but uncertain