ltrcola

The problem is that those candidates also support other things. If they donated money to these candidates, they are responsible for those other things too.

It sounds like a new car name. 2020 Toyota Vercel. Wasn't there a model called the Tercel?

I like Hangouts overall, but the killer feature that's missing is a good gallery view where I can see more than 4-6 participants at a time. Zoom is really good at this.

Why would someone bring it up at every meeting? That's a pretty big straw man argument. I'm sure there are outliers that do that, but they are rare.

On the other hand, many gay folks are afraid to even mention their partner at all at work, even casually in the what that most people do. In that case, the belief that "gay rights are political" that some folks have are creating a toxic environment.

Companies themselves are inherently political though, just by existing. They exist in the context of society and are made possible by the legal structures created by politics. And they generally advocate for themselves within the political system (a good example is lobbying).

So there are certainly limits in the workplace and there is a line to toe for toleration and polite conversation, but saying "politics do not belong in the workplace" is pretty absurd.

Netlify has been pretty great so far. My team was able to use the promise of a super quick CMS integration with Netlify CMS to justify getting out of building another nasty WordPress site (what our editors are familiar with). The actual Netlify setup caused no trouble at all and let us seamlessly move off of GitHub Pages, and now we can put in an integrated build process with NPM or whatever else we need.

Netlify CMS itself is a lot more raw but I see huge potential there, especially since it's open source. Our InfoSec folks loved the idea of content changes as commits. And the maintainers on Gitter are super open to help folks and work through changes. Already submitted a PR that was accepted and has made it into a release. And we haven't paid them anything yet, even with Google Single Sign-On integrated.

I wish they spent a bit more time on the CMS part of the equation. It's hugely important to enable content editors to make changes. The solution isn't that valuable if it's limited to devs only. I also don't think there's a clear winner yet. Maybe, Contentful if you have a boatload of money, but I certainly don't.

I did just implement Netlify CMS in a project though. Super easy to get set up and it's open source. It's missing some things from more polished CMSes that you might expect, like editor roles, but it's still pretty young. The project lead is really responsive and I have high hopes for it long term.

Hi! We do have some remote folks and I think we're open to it on a case by case basis. For this front end position we're starting a new team and I think remote would make that pretty difficult at first. Our Platform and Product Engineer postings may be more open to that right now.

Hopefully as time goes by we have more flexibility :)

I've had the misfortune of having to maintain and extend a new WP install now, where we used Umbraco before. Literally everything about Umbraco was better except for two things: 1) the requirement to run on Windows 2) the number of available plugins was smaller

The number of plugins thing is offset by the reality that Umbraco plugins were generally higher quality across the board.

What you gain, though, is a sensible way to create a content structure/ component blocks and templates that work in a standard MVC way with a data model and views. WordPress on the other hand... I want to cry every time I look at a WordPress template, even when using improvements over the core like Roots provides with Bedrock and Sage. It's all imperative functions that modify state, global vars and functions, exceptions to remove all sorts of random bundled scripts and an outdated version of jQuery, just barf-ola.

And that's not even getting into the fact that by default it runs basically everything on every single request unless you install a third party caching plugin. Good luck loading config values or whatever on "startup" because the concept doesn't exist. Umbraco had a much higher level of performance out of the box, and could use generally the same additional caching techniques and performance techniques if you want to.

I truly think these types of CMSes are on their way out, as they tie the presentation layer directly to content management. The future, to me, is looking like Headless CMSes linked to a static site generator like Gatsby or React Static.

Exactly. I don't think they are accounting for how some people react to interviews. I've had candidates who have been explicitly nervous and stuttering, and we've consciously had to decide not to hold that against them. They turned out to be a great hire.

I think I can do okay in coding interviews, but only if I prep for that style of work first. It's definitely different. I'm perfectly (or at least acceptably) competent in my day to day.

Not sure if I communicated what I meant. I think if I was going to set up something using a headless CMS, I would integrate it with a project like React Static. When a user publishes something in the CMS, it would trigger a build of the generator that would result in putting some files out in S3 or something equivalent.

That way if you see a traffic spike or a DDoS attack, it's directed only towards static files on S3 and you can let Amazon take care of it. I don't want to be too critical of how people have things set up because I'm sure they have their reasons, but that said I don't think a page request on your site should map directly to an API request to the CMS.

Ideally, a spike in traffic to your site shouldn't result in taking down your CMS. That's why static site generators are so popular.