jbreiding

No need to worry if you just use the same shell through WSL. The integration is with the shell not the os.

Any reason you wouldn't use resource groups and db/collections for segregation instead of encoding into the collection name? I believe all of that hirearchy ends up in the resource URI if you really need it encoded there.

Having the azure table storage be indexed into azure search with an azure function as the indexer delivers a pretty powerful alternative that isn't exactly batteries included, but close.

No, you can query a collection of these entities and get back the resulting set with pagination.

Whose failing would that be though? The interview should gauge capability and motivation which should accrue towards fit for the team and role. There should be some expectation of learning in the role and not just hit the ground running.

Or don't forget about the boot camps which boast high placement rates because they hire the students that don't find outside roles to continue teaching until they find a better outside role. I find that practice deceptive especially because they are paying well under the rate they are advertising the student should earn upon graduation.

There does appear to be a mirror on github for sessionc, https://github.com/sessionc.

So basically no single fix, just a generally healthy lifestyle accompanied by a healthy balance of stress.

While I can agree on the stated reason being not perfect. Production bugs converted to tests do help validate the bug is fixed for ci/cd and understanding for the necessary rca.

I'm interested to understand the delta here too. I used cmder daily for work and iterm2 at home and I am quite happy with both. Sure they are different, but they are always going to be.

Xmind has the outline editing mode that I find very useful for this very reason. Sure it's not just a simple text file but it also doesn't require edit and presentation on different places/apps.

It's easy to argue you are just rattling off buzzwords if you don't provide examples.

I would also argue that not based on a schema is even more brittle as you end up implementing validation logic and client marshalling that the schema would allow you to just generate.

One of the main difference I see at first glance is draft requires a pod/service vs skaffold doesn't. This means it's lower cost on local resources right?

In the middle of this book right now, specifically the unreliable clocks part. The explanations have the right amount of depth. It's a great read in so far.

If this is the same as this site talks about, https://access.redhat.com/documentation/en-us/red_hat_enterp..., then it would seem to be a first class citizen.

Why not just check the inner exception type instead of the contents? This seems more accurate than relying on the contents to contain a specific string.

I think this depends of the levels of nesting and complexity, but a libsax based parser is not "incredibly" slow.

A Dom based parser could be, but also depends of number of nodes and nesting.

In the spaces you mention not hearing about fish are ones where you generally don't look for interactive applications/features. You also generally don't take a dependency like another shell when you are likely installing ruby or python already.

The two shells target different use cases. Hopefully they are both successful in attracting a good audience.