tiredofsametab

Why would I want to create an array called ‘layer’?

We’re stuck on Mac at work and I hate it.

English is notoriously awful regarding orthography vs pronunciation. I actually thought you meant something that rhymed with Bach just looking at the name with a longer ‘a’ for some reason (which is weird since vowel length isn’t phonemic in English).

Edit: you probably also could have said “hard a” or something since it probably literally thinks ‘long a’ means ‘hold the a sound for a longer duration’ (which makes sense to me)

Raych?

I’m old enough to have been through this in IT (that and leapseconds) and it’s what my mind first jumped to (well, other than enshitification).

move things, breakfast

Ah, sorry. Stupid race conditions.

Boring answer: older repos are master, newer ones are main. I’ve worked at companies that did other things such as having the prod branch be a branch called prod.

I despise that idiot and his republican enablers and supporters. I want the Epstein files released.

That said, people say this shit at least about Hawaii all the time. I don’t know if the same is true for Alaska. Is it dumb? Yep. Is it especially stupid being a president? Absolutely. Do I think that means “he’s already given it away” or something? No way.

A child reads the headers and encodes each message brick by brick. Several receive the same message due to frequent errors

That or really bad tape was what I was thinking.

I have tortoise git on a windows machine and GitHub desktop on a Mac. I do some things from the command line when I’m not feeling lazy.

I switched companies. I started go when replacing php at a previous company. I wanted to do rust at the time, but my options from the CTO were go or newer php (we were 5.x IIRC). I chose go.

My current company decided on go before I started. There’s some python ml stuff and some other things in functional languages, but we’re primarily go. I don’t know why specifically it was chosen. The old codebase was a bit of go and the original legacy in Ruby. I’m definitely glad they decided to move away from Ruby slowly (and compleltely in the new codebase).

I’m mostly making sure they didn’t completely lie about being able to work in the language and can explain what and they would do, why, and how they respond to feedback. I expect people to be varying levels of nervous and that’s fine. I work with people to get them focused and take the edge off as much as possible.

What I ask for usually is related to what we need to implement, but a more basic chunk of it to, for example, show that the candidate understands concurrency and can use basics in the language to do something with that (which we do frequently).

For many positions, we do not have homework and this is the only coding we get (kinda depends on role and project).

As a newer company and still technically a start-up, the boss paying the bills can decide we need to chase something else and he isn’t being talked out of it. This can lead to very fast collaborative design and coding of PoCs which can be more intense than the interview. I don’t like it but it is what it is. Not everything we do is nice, stable, and long-term.

I can relate to needing that job; I’ve been homeless, so I definitely kno the hat that pressure feels like and why nerves alone are never a deciding factor for me.

I give live coding tests generally based on the level they claim to be at in the language. It doesn’t have to be perfect as I’m more concerned with why they’re doing a thing. I usually pick something fairly basic with some edge cases just to see if they mention it.

As opposed to homework, it also proves that you can at least basically work in the language in question (I’ve had a couple of people who got to my round but seemed to know almost nothing about a language they claimed a lot of experience in (like declaring variables and struct members wrong… seriously). We also caught someone that didn’t seem to have done the homework themselves.

If the candidate makes mistakes or gives an imperfect solution, I try to gently guide them to where we need to be. I ask them to explain why they made decisions they did, any edge cases, and how to improve performance or scale it. I expect them to ask questions when something is vague (and usually something in my problem can be interpreted one or two ways for this reason) because these are things they will encounter working with stakeholders and other engineers. If they can’t do that live and on-the-fly, they’re probably not for us. I fully expect nerves to be a factor and account for that; we’re all nervous in interviews.

I used to work in Java and now work in Go writing backend services. I think I enjoy writing Go more than I did Java most of the time.

Pure speculation: ;possibly to identify sexual nudity and “inappropriate” content as some kind of legitimate usecase. What was actually done, I have no idea.

Well, it would have been if people updated it when making changes; now it’s just all an incorrect snapshot of an older version of wheel that no longer reflects reality.

To be clear, I don’t think the choices are a coincidence; I think the general idea is one.

My guess: someone messed up trying to split an array and split a string from it and hilarity ensued.

One of my teammates used AI (our company heavily encourages it) to write code. It did what it was supposed to and the tests passed, but it was the most ugly and unmaintainable shit ever. For one example, I don’t want to have to untangle a for i = 0; i++; i <= len(foo) {} that has multiple ifs inside that separately increment and decrement the loop counter i when trying to troubleshoot an issue.