isaacaggrey

What would you say is comparable experience wise to 1Password? I’ve found particularly the 1Password Family plan there’s not really a good alternative of rolling with KeepassX, Bitwarden, etc.

The answer could be nothing and I still respect the choice to speak with your wallet.

I wouldn’t delete any items any backlog items. Much better to always close with a reason. You can make this a first class status in whatever platform like a “Closed - Duplicate”, “Closed - Unneeded”, etc.

This helps with searching for rationale in the future, looking back to similar items, etc.

You can’t stop someone from putting it back but you can close it as duplicate and link it as related.

Edit: also if the person putting work in the backlog is not a core contributor or product you should formalize some other intake process that can triage whether it meets the bar to get in

If you bought the device, then you have the right to do what you want with the device (modify, tweak, repair).

I agree but this particular example showed nothing about leveraging skill, experience, or intuition. If anything, this is another straightforward example of a one shot ask.

edit: that said, I understand this particular post is about model capability

Very neat. Thank you for sharing! I assume this was one shot as well -what sort of prompt did you use?

I’m sure folks would be interested even in a blog post comparing just this process with different Anthropic models if that’s something you do and need a content idea. :)

I understood it in the spirit of “code is a liability not an asset.” Code still needs to be maintained, changed, etc whether that is by a human or LLM.

In other words, just because more code can be produced quickly does not mean that it is cheap.

edit: I’m maybe hearing your point is that LLMs may change that POV but I think that is TBD.

It's interesting how this is both a nebulous yet concrete idea and how definitions and implementations vary widely. I was having the _exact_ same questions since I've had to newly lean more into the data engineering space at my current gig, so it's helpful to hear these takeaways from folks experienced in the trenches (not just the newbs).

I agree with your parent post but why would a breakup not equally apply to Apple?

I think other commenters are overstating the change from staggered to columnar. I type just fine (100 WPM+) going between my Moonlander (split keyboard from ZSA) and my Lenovo/Macbook (typical staggered layouts).

In hindsight, the biggest issue I ran into switching keyboards was that I was too ambitious playing around with the key configuration. The configurability is a big draw but I took for granted that I had already built up years of natural tendency for certain things - which thumb I use for space, preferences for Ctrl/Alt/Command/Option, for Shift, etc.

The default for these keyboards probably don't 100% align with what you're used to, so you should directly map what you're doing currently over to the keymap of the keyboard and then you can fiddle with making it yours over time.

I will say that if you're not already a touch typer, then a split keyboard is not going to help and it will be more difficult to get used to.

edit: also, if anything, going columnar helped me actually consistently hit number keys!

Could you elaborate?