Hacker Newsnew | past | comments | ask | show | jobs | submit | amrox's commentslogin

As a vim user since the 90s - this is what I've landed on. It pretty easy to disable the vim plugin if you're sharing your computer with a muggle.


I'm having a similar experience. I turned off my “looking for jobs” status a few weeks ago, and just turned it back on, expecting a flood. Never came ¯\_(ツ)_/¯


It's slow season wait till the budgets refresh in March.


Yep - I just now saw this but that was my similar reply too.


Beautiful. I have a couple of the NuPhy [1] keyboards so I'm definitely in the target market.

The Rotary Encoder is a dealbreaker for me though. I want something slender that I can easily slip into a case or backpack. If it was optional, you'd have a customer!

[1] https://nuphy.com


For the page:

> You will need real hardware to run it.

Why doesn't it work in a VM?


It is strange. Just downloaded and tried to boot in a KVM+Qemu VM targeting FreeBSD 13 (virsh). Booted but kernel hung with an obscure launchd dispatching job message. I haven't used FreeBSD consistently since the 4.x days so I have no idea what this means.

Looks interesting enough to play around with but for such an ambitious project VM support should be one of the first dev priorities not only for dev and testing but for users wanting to take it for a spin.


That does not sound like my experience.

Are there GitHub issues for the bugs you mention?


Yes, there are more than 100 open issues, which unfortunately I don't think the author has enough bandwidth to triage. Bugs keep piling up. https://github.com/asdf-vm/asdf/issues


It’s all relative but 100 open issues doesn’t sound bad for a somewhat popular project to me. For example, rust-lang/rust has over 8000.

Regardless, I curious if there were _specific_ issues you had.

And following that, I’m also curious what you moved to instead.


> What it fundamentally boils down to is that your org chart determines your architecture.

This is Conway’s law

https://en.wikipedia.org/wiki/Conway%27s_law


M


praise: I came here to suggest conventional comments as well!


thought: reading this style of sentence would get annoying quickly.

I don't get the point of these TBH. The usefulness of conventional commits is that they can be easily aggregated to get an idea of the types of changes that were made.

Code review comments are purely meant for human communication, so requiring a specific structure is both annoying to write and to read.

I tend to use one, at most two prefixes. "Nit", and rarely "blocker". Though I'd rather specify if something is a blocker once I make my case about what needs to be changed.

Every other comment is assumed to be a suggestion, and depending or not I block the PR by "requesting changes", it's up to the author to either accept my suggestion or provide reasons not to.

Any other strict guideline about how to write prose is silly to me. Especially the decorations section. C'mon now.



Find a company whose product is primarily physical. I work at a robotics company and much of our staff never went remote.

My team is primarily remote but I’m actually hiring an on-site person for IT.


This is the best answer. In the U.S., something over 2/3 of the populations works non-remote, and always has. The "everything is remote now" perspective is a very professional-class one. So, if you work for a place where most of the jobs by their nature cannot be remote, it will not be weird to want to be at work, it will be standard.

One bonus is that a lot of these places need IT help, and you may be appreciated more. Plus, a greater diversity of backgrounds among the people you work with.


Agreed. I am also at a robotics company (see profile) and most of our staff only had a brief time at home and have been working onsite for almost all of 2021. I joined half way through the pandemic and was surprised to find that I was very happy to return to the office.

Our challenge, as I'm sure you've guessed, is finding smart, motivated people like yourself who would prefer to be in the office. We are finding that many people, even those local to our market, would prefer to WFH.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: