For sure! If you'd like an example of how to work with env variable and functions when accessing an external API in Netlify, I wrote a blog post recently that may be helpful, complete with code samples to play around with. Also, more importantly, it comes with free pizza recommendations if you ever find yourself in Chicago! -> https://www.netlify.com/blog/2019/05/29/creating-a-map-of-the-best-pizza-in-chicago-with-yelps-fusion-api--netlify-dev/

I love questions about productivity and organizational hacks! Especially since talking about this means I now have to be kept accountable 🙈 Organization for my day usually starts at the top of the week, since it lets me set an intention and goals that I want to accomplish. On our team, we all fill out a form noting everything we worked on last week, and the things we're planning to work on that week as well as any challenges that stand in our way. This form submission gets emailed to everyone on the team, so we're all kept in sync. As for day to day tasks, I try to note everything I want to do on todoist when I start my day. It's so easy to lose track of time when I don't do this, because I tend to jump on things willy nilly if I don't have a specific goal set for myself. I additionally try to be intentional with my time by using a pomodoro timer app of sorts called Forest, it builds a cute tree for every block of time you focus! Also, I'm more of a morning person, so I do heavy, time/labor intensive tasks at the start of my day; it's a productivity hack known as "Eating the Frog", if you're into productivity hacks :)

I too came across zzz.dog and it is amazingly fun! I've seen examples of people using it alongside React Spring for instance to create really neat 3D renders and animations. You can find lots of those examples on Codepen. Also Josh Comeau wrote a wonderful post complete with code snippets to explain using CSS 3D transforms, which was incredibly mind blowing. https://www.joshwcomeau.com/posts/folding-the-dom/

We do lunch and learns at Netlify quite regularly. These are great opportunities to share what we’ve been working on with the rest of the team in a pretty informal setting. There’s also a product demo meeting biweekly where we get to share and also hear from others on the team and what they’ve been working on. It’s a great way to sync up esp since so many of us are remote! This is tough, as swyx mentioned, nothing is guaranteed. But in general users power a lot of decisions we make :) We usually do yearly reviews and that’s oftentimes when this evaluation happens. Since we’re still early stage, this process hasn’t yet been formalized but will be very very soon! If you’re interested in general career progression at other companies that we kinda sorta emulate, check out progression.fyi Number of years isn’t a great way to evaluate candidates. I’ve seen developers with 10 years of experience who are not as “up to par” as a developer of 3-5 years or experience for instance. It’s all relative. Having said that, we do look at what you’ve worked on/have been working on and try to gauge if a candidate is enthusiastic about a specific area of expertise. Also, if they’re willing to learn and adapt quickly. This is hard to gauge but a coworker of mine Jacob Schatz puts it so well in this tweet -> https://twitter.com/jakecodes/status/1135677610053251073 For me motivation is tied directly to whether or not a task resonates with my own goals and aspirations. Sarah puts this so well in this tweet-> https://twitter.com/sarah_edo/status/1131424076726132736

Thanks for your question! You’re absolutely spot on, auth is a really hard problem to get right! When it comes to JAMstack, auth can be handled using any auth as a service library like Auth0, Okta or Netlify Identity, which is an auth service we offer to Netlify users. As for API keys and making sure those don’t get leaked, serverless functions as you mentioned are really handy for that. Netlify support env variables, so you could pass in API keys to your functions that way. You could also use a service like AWS Parameter Store to store your secrets, and I believe that integrates nicely with the Serverless Framework, if you choose to go down that path. The downside to the approaches ,mentioned of course if that it’s possible for malicious users to abuse functions since environment variables can become exposed as a result. One way to potentially counteract this is to make sure that your function end points are not “guessable”, meaning that you could do a redirect so accessing /api actually routes to /.netlify/functions/WHATEVERFUNCTIONNAME which performs an API call to whatever service you're trying to access. Hope this helps!

Hey! Thanks so much for your question! In short, yes! The JAMstack stands for JavaScript, APIs and Markup, which is an architecture for creating sites (both static and dynamic using JavAcript, API and prerenderred Markup). Basically what makes a site JAM-ey is its ability to be statically hosted on a Content Delivery Network like Netlify or Amazon’s CloudFront. The nice thing about the JAMstack (for me) is the APIs piece of it. This allows you to make a site incredibly dynamic like processing payments and doing database read/writes etc. So in a sense you get the nice bits of a full stack app without the performance latencies that often comes with it. Hurray! There are so many ways to build a JAMstack site, so it’s hard to list them all here. But a great starting point is to start with a static site generator like Hugo, VuePress or Gatsby. It’s a great way to get started working with a JAMstack frame of mind! You can find a longer list of static site generators on https://www.staticgen.com/ As for securing your applications via API keys, Netlify allows you to save your environment variables in the dashboard so you don’t have to manage that yourself. You can access that via site settings > build and deploy > environment. The really nice thing about this is that it works seamlessly with the newly released Netlify Dev workflow, which lets you replicate the netlify workflow right from your local machine. When you use Netlify Dev, and run it via netlify dev , the CLI pulls down your environment variables so you don’t even have to have a .env file on your project! Hope that answers your questions!