tiredofsametab

I’d love to at some point but, last I heard, it breaks the felica and wallet integration which I need to do japanese government stuff (and use the train and such)

It’s bamboo common here in rural Japan. We have two types, one of which has edible shoots in the spring so there’s that at least. It does hold the ground together along the riverbank so I never plan on fully ripping it up; last thing I need is for a chunk of my property to slide off in the next big quake.

I’d rather some more of it be human food, but maybe that’s out back. I’m slowly turning areas around the house I just bought into native stuff and food. It is, however, a constant battle against kudzu strangling and bamboo encroaching. I generally avoid having anything that tall and unkept (as some areas look to be) due to venomous snakes that can bite when surprised :/

Not necessarily. Maybe because I’m old, I don’t think being out in public and having that delivered to an audience way bigger and further outside that area without consent is right. If I’m walking by in a shot or something, I don’t mind at all. But if it’s someone sitting nearby when I’m at a restaurant or bar or something, that starts to get weird for me. I did also have a stalker once which definitely did shape my view on this more.

I should have the right to not have my voice or likeness recorded and sent to some unknown, private company without my consent.

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.

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

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 didn’t like Lemmy at first, possibly because it had this weird auto-refresh thing and other issues. I found mbin instead and have been with it since. I may check out Piefed at some point. My instance recently has been struggling with donations and I can’t really help right now.

I don’t use an app for mbin, just browser. The one thing I will say is that images are broken on mobile (Android) as there is no X to close the image, annoyingly.

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.

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.

im not sure how true that is considering that they can always just open a gate for fish to pass

That’s not how that actually works. Damming has huge impacts on downstream, now much drier, ecosystems. Even if there were a way to “open a gate for fish”, that wouldn’t solve the problem that their habitat is now gone. This is among reasons people have fought for dam removal. This also ignores the flooding of the environment that becomes the reservoir.

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.

A friend told me about rust around 8 years ago and this was very much my first experience (at least with &str and lifetimes and borrow errors).