HN user
[ my public key: https://keybase.io/chrismccraw; my proof: https://keybase.io/chrismccraw/sigs/RU2VG84FyFOxrWUuLQzcg0oB7ZktQEbWYFp9O7wAzYo ]
...Unless you're savvy. Thank goodness for the availability of https://publicsuffix.org/ (as long as you only use your main domain and don't need to share cookies with your own subdomains), and the includeSubDomains directive to HSTS! But - if you already set this up, you probably are savvy enough to avoid the problems created (or your provider is)
Yup. some implementations provide similar ANAME, and Cloudflare has flattened CNAME which is probably the best implementation I came across in years of supporting folks trying to use these kinds of records on a large CDN.
If you liked that, check out also his newsletter and his fiction writing - both are stellar (his is the only newsletter I read, even though I pay for other ones!)
the info on glassdoor is not correct.
Yay, my congressman continues to introduce legislation I support. It's a rare treat in our political system of "lesser evils" and obstructionism.
(I work for netlify).
You are aware that any headless CMS works well with netlify, right? (even some less headless ones, but these are easy): Contentful, Sanity, Ghost, Forestry? Our CMS is an open source project that is community maintained these days, not managed by us :)
Safeway no longer accepts that number at least in the 503 area code, I found out upon trying as was my custom, a few years ago. The cashier recognized it and laughed with me as she scanned her own card which they keep on hand precisely for these reasons, as I understand it.
It's not that it's less work!
By one measure it's "more work" - if you think about the time that each person spends creating their content in advance, vs what they could spend wall clock time talking in the meeting - 30 min meeting can only have thirty minutes of talking - vs N x 10min pre-writing. It's just parallelizable outside of the tiny synchronous need as the mutex is passed, and a better use of everyone's time - you can write the status update any time before the meeting, whenever you have downtime.
These are probably the two best interesting aka "seemingly not in wide use" ideas we've tried, with great results:
- create a culture of actually RSVP'ing for meetings (yes or no!) so that people know who will be in a call and you don't waste 5 minutes wondering if X will be joining or if anyone will be joining at all. Pairs best with a culture of actually being on time for meetings and ending on time (so you can all be on time for the next one).
- to facilitate this, if you have a good agenda, people can opt out of coming if there are no relevant topics, or in some cases they can share their feedback on to a colleague or the organizer who will pass it on to the group on their behalf. As a result of this process, some of our "best" (from today's point of view; they used to be the worst in terms of getting through the agenda or understanding if this instance will be relevant to you) meetings have morphed into an actual commitment to have every participant spending 5-10 min to write down status updates in advance, with 2 minute actual "live meeting" check-ins: "anything besides the notes we all left for eachother, to discuss?"
This second one has been especially effective for our distributed management team in very different timezones where "overlap" meeting times (usually beginning-of-day-US/end-of-day-EU) are at a premium. You can do a few of those ("whole product team + stakeholders" "whole back-end dev team" "all engineering managers") meetings in one traditional-meeting time slot if you keep the agenda razor focused.
I run the Netlify Support team, and this statement from @michaelmior is correct: apex domains are served using redundant, global CDN if you use Netlify's DNS hosting, or Flattened CNAMEs from Cloudflare.
More details for folks who are curious about optimal config using Cloudflare's DNS hosting, can be found here: https://answers.netlify.com/t/support-guide-which-are-some-g...
This should not be the case; if you'd like, Netlify's Support team will be happy to review your settings to help discover why it didn't help you out (start from https://netlify.com/support) and ensure that you are "futureproofed"!
Can confirm netlify DNS hosting was never a requirement for branch deploys, using your domain name (staging.you.com) or netlify's (staging--yoursite.netlify.com). This article shows how to configure using other DNS hosting: https://community.netlify.com/t/support-guide-how-to-use-net...
I like to think of this as having a tremendous ripple effect - when I smile and thank the postman, he smiles at the next person he sees and maybe they're nice to the worker in the drive through at the restaurant, who goes home 1% less frustrated to their family.
Probably a bit overstated in that example, but if you walk around doing it consistently, I think that on average you're still making a small difference, while fighting apathy and politics of hate.
more specifically, npmjs.com and nodejs.org are not available from Netlify's datacenter due to this outage.
But when they do, it can be amazing. https://www.atlassian.com/blog/statuspage/how-to-write-a-goo...
Availability of nearby services such as those is a pretty major component in the walkability scores I've seen like https://en.wikipedia.org/wiki/Walk_Score . I agree they are very important, but I think they are considered. Where do you see them missing?
You're missing out on the brave new future! netlifyctl is dormant, upgrade to netlify-cli: https://github.com/netlify/cli
I wish I'd had "a real plan" in jobs past as an individual interviewer in a series, instead of a vague goal like "talk about his technical chops" or "see if she can work across teams". I turned out not to be very good or consistent at either freestyling questions completely OR reporting reliably whether a candidate was "successful" in my area without planning and consistency.
I'm a former developer, turned hiring manager for a very technical support team and employ several things I feel are fair and useful and I believe would also have been in that past life.
0. repeatable interview process. When comparing candidates, the comparison should be apples:apples. "check for culture fit" isn't; "ask questions 1,2,3 of each candidate, with goals of finding out x,y,z and help to N degree if requested" is. Leave room for the candidate to demonstrate personality and style of course, as well as (short) tangential conversations that come up during the Q&A process. The goal isn't to make it robotic/automatable.
1. There is a take home exercise. It has a clear scope:
- accomplish goal X (create a website)
- with tools like Y (your choice of static site generator)
- in Z fashion (public github repo)
- in less than 4 hours.
Encourage questions before candidates begin the exercise, so that people work on the right problem rather than guessing wrong. Don't force a timeline ("you have until the job closes which won't be sooner than a week from now"), and use an objective grading rubric for each section of the task.
Here's an example of the objective rubric: 1 point for grammar, 1 point for each of two distinct points of content, and 1 point for providing the context as to why those are important points. Few of the questions have only one correct answer and it is not always obvious to candidates what we're looking for in an answer; but it is known in advance to the grading committee what is being sought, e.g. "perspective over plot".
2. interviews are in slack. We're a remote team who communicate 95% via writing, and it doesn't matter if you stutter or what you look like or how you present. Get comfortable in your PJ's with a cup of tea, or use your standing desk if that helps you feel sharper. It only matters how you communicate in writing.
Once again, the interviews are structured - "interviewer 2 will ask these 5 questions" and the criteria for success aren't "this woman was well spoken" but instead "she showed ability to think on the fly about something unexpected, demonstrated empathy in communication, and made a compelling argument for her proposed solution". Not quite as objective as the take home test, but still "gradeable". And, in case of a hard choice between two candidates, other stakeholders in the hiring process can review the transcript of the chat, providing their grade considering the pre-specified criteria, to help decide.
It's not ideal, but it is practical, allows for cooperative interviewing (anyone can help a candidate start the well-documented interview process; anyone can do any stage of the interview and know that we cover all the questions we want asked before the end), and encourages consistent judgment.
It's worked well for us so far and people have appreciated it; it also lets us give concrete answers to "what could I have done better?" to candidates we reject who ask for a follow-up. I feel pretty strongly that you spent your time working with us (particularly on the take home exercise) so I can spend time explaining how you could improve (often it is useful to other applications for other jobs: "your code should have comments to explain confusing things or highlight clever things", "consider using git for revision control rather than only committing your completed project", "you'd benefit from using a grammar checker"). We've had many repeat applicants who answer better with each iteration.
I work for netlify. We support 2FA on any tier, since you can auth via git provider and require 2FA there.
We presently don't support REQUIRED 2FA (you can also set a password) under the enterprise account level, since that's what enables SSO using a SAML-based identity provider and enforcing those limits there.
I work for netlify, and yes, we ask you to upgrade, don't just turn you off if you go over.
Netlify | Several roles | SF, CA | remote or on-site | Full-time | https://www.netlify.com
The web is changing — and we’ve made it our mission to make sure that it changes for the better.
We’re working on tools that help developers build a fast, healthy, and scalable web. There’s no shortage of interesting problems to solve — from creating a intuitive and powerful experience in our core app, to building the resilient and secure infrastructure that powers it, to crafting open source tools that drive the ecosystem around it, to getting to know the developers in our communities and making sure they can be successful with the JAMstack.
We are hiring for the below roles:
Data Engineer Technical Writer Sr. Marketing Communications Designer Platform Developer Community Manager Front-end Developer
For more information, see https://www.netlify.com/careers
Is there an elsewhere for creators to take their accounts? I give via patreon because it is the only platform I'm aware of that exists that anyone really uses in this way. I give to some creators via their own systems - but as far as a generally accepted mass market solution - I'm interested in hearing about others but don't know them yet.
Disclaimer: I work for Netlify.
Minor correction to your 2nd footnote: We put your assets on our CDN - some of which is served by amazon's Cloudfront. We don't use Cloudflare's services to run our CDN :)
Netlify | Multiple Positions | Remote for 2 positions, ONSITE in SF for 3 positions | 4x Full Time, 1x Part Time
Netlify aims to perfect a unified platform that automates code; creating highly-performant sites and web apps. Push your code and let us take care of the rest.
We are looking for the following in SF:
- product manager - communication designer - office manager (part time)
We are looking for the following local or remote: - support engineer (Asia/Pacific or Europe timezones) - solutions engineer (within 3h of US/Pacific)
You can read more about and apply for all of these positions at https://www.netlify.com/careers
probably the best reason is: we have our CDN spread over 4 different cloud providers. AWS and Digital Ocean could both go down (completely - though we're in several different data centers for each) and it would keep on keepin' on.
Do you need any paid features? The only things you get for $45 are:
- simple password protection (basic auth or single-password-no-login)
- small division of power - not everyone can delete the site and invite contributors.
Everything else is included for free.
This is definitely the most flattering insult we received in this thread ;)
Disclaimer: I work for Netlify
If you check out this blog post about one of our biggest customers, you can see that there are some non-static services involved (look for the list of 4 services all called Go<something>):
https://www.netlify.com/blog/2017/03/16/smashing-magazine-ju...
So - while I wouldn't say we're planning to become a DB host or anything - we are both open to providing some glue needed to bring some missing pieces together for static sites without vendor lock in (all of those are open source and you can run your own instances - they are also all being polished up right now so keep an eye on the one(s) that interest you)...and we are trying to enable other services we don't want to reinvent - things like auth0 and firebase - for interoperability with our service.
oh yeah, and we also open sourced a CMS that uses Git as a backing store so your content editors won't have to learn markdown or git... https://github.com/netlify/netlify-cms
So - we're not done yet :)
disclaimer: I work for Netlify.
We've changed pricing models 3 times since I've worked here. Each time we've grandfathered people in at their old pricing level, and the last change also gave away substantially more features for free. Never have we moved someone's cheese from "free" to "not free".
I understand that this is still a risk - I'm not promising it will never happen - but we have a killer track record of giving away more, not less, over time, and never have we changed the pricing for an existing site (except to give away enough features that many folks downgraded from paid to free with the last change - and even that was opt-in in case you for some reason wanted to keep paying us :D )