dbergamin

I don't agree, serverless code in itself tends to be portable. It's the surrounding services that lock you in.

VSCode remote plugin is pretty great if you're doing heavy editing. Probably wouldn't hook it up to a production machine though, it leaves a bit of cruft around. You could also look to enhance your vim experience, a few plugins and most importantly, some practice, can turn it into an efficient text editor.

It is hard to say, as the requirement you have doesn't sound very standard so we might need to know a bit more to help.

On reflection my gripe with the post is really about vocabulary.

Half-arsing carries negative connotations - to me, at least, it is the 'bad' form of pragmatism, and as such in my book it is never defensible.

IMO we have other words to describe the scenario where an expert consciously makes a 'good' or reasonable trade-off to complete a task in a smaller window of time, and should use those instead.

I can't really get on board - for most situations, risk of 'broken window' effect is strong unless your team all operate on the same page with a common understanding of what tradeoffs are acceptable.

Perhaps reasonable in projects/tasks that you have full ownership of and intend to continue to do so for the foreseeable future. In general though, I think there's good reason to strongly prefer the 'if a thing is worth doing, it's worth doing well' side of the spectrum.

So what colour should we paint the bikeshed?

Fair response IMO, this is the type of issue that can attract a lot of noisy opinions so very reasonable to lock comments to contributors.

Another Jekyll fan chiming in. It was a good sign for me that it's not super-actively maintained, yet still commands a strong following in an arena with fairly low switching costs. Out of the box, it has most things you want and very little that you don't.

Principle 1 on the Jekyll philosophy is 'no magic', and that's why I love it. It tends to behave as expected, and what it provides is simple enough that I maintain a feeling of full control over the output. I've wrote some little bits of JS to add minor client-side enhancements, and the Jekyll plugin system is easy to dive into if you want to add some site-render features. Great tool.

Kudos to the author for putting something up for discussion. Replace the word 'The' with 'My' in the title and it's a nice exploration of where React tooling for static sites is at.

Keep publishing and sharing mate, you're good at telling a story and have more good content ahead of you.

If you are paying contractor rates, then that makes sense of course.

For a permanent hire I think it would be reasonable to ask more than half. Even working 50% hours, one does not usually completely unplug during other half - even if not active on corporate systems it's likely they're taking problems away and thinking them over.

I think you may be surprised by the output you get - when I have worked with part time technical staff in the past, it often seems to help grant a laser focus of sorts.