eddd-ddde

It meets all your requirements. Markdown interop is very good. Always backed up and in sync. Supports offline access. Really easy to export everything if you really need to.

"It's so easy, I could have done that myself"

Well yeah, but you didn't.

Insanely easy and effective.

I _could_ do my job without AI, but it would take twice the time and I would feel miserable having to type out every single character like a caveman.

Just AI auto complete alone is a massive life changer. It reduces my typing at least in half, and is highly accurate to what I want to write.

It massively boosts my efficiency as just reading the code myself would take days.

Honestly the only thing that would making work from the office better is if the senior in my team _wasn't_ remote. Nothing against his decision, but I do feel like I've missed out on the organic growth opportunities from collaborating in person with them.

This is what it means to understand something. It's like P Vs NP. I don't need to find the solution, I just need to be able to verify _a_ solution.

Unlike the US your ID is just an ID and not a form of secret or authentication token.

The answer is development branches are forbidden but releases still use a kind of branching approach.

When you make a release you use commit A from main, then development continues, commit B adds a feature, and maybe commit C fixes a serious bug.

You don't want to make a new release at C because it includes new non tested features, instead you cherry-pick fixes to your release, test the new release candidates, and release that when ready.

Development still happens in main however.

Another big tool to minimise these problems is to separate the concept of feature release from the concept of binary release. You don't have to make a true deployment to release new features or roll them back, just use a toggle switch.

I don't think any single other platform has as good a search feature as TikTok does.

Another option is to just use cells and treat the execution model similarly to JavaScript where mutation is limited specific scopes.

I'm pretty sure it is possible, and it might even yield some performance improvements.

That way you wouldn't have to worry about deleted items impacting performance too much.

Just because you build a unique_ptr from a raw pointer it doesn't mean that it is now magically owned by the object. You also have to ensure that no other place already did that, which unique_ptr simply cannot enforce.

For larger distances you wouldn't even see the text in the screen, so you don't even know how much to jump. In this situation I just spam ctrl+d, then tweak with j.

Need a new secret offensive operation? Create a new JSON file with the coordinates, make a merge request and get Commander approval, merge it, and our new proprietary GitHub action runner will deploy a drone in seconds!

You can easily script it to decode passwords on demand.

What happens next is completely irrelevant. The maintainer can 100% decide to just ignore the issue or close it.

Opening issues doesn't create unmaintained software. In fact it helps.

That's exactly what happens when you read. Copyrighted input fed straight into your brain, a lossy storage and processing machine.

If I'm feeling really fancy I may enable vim bindings and add the fuzzy find plugin, but plain fish is so good on its own.