Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 32
  1. Building is the fun part.

  2. I know that we “moved on” from prompt engineering but it’s still a huge gap for tech and non-tech AI users, developers, consumers, etc.

  3. Hit Your 1 Rep Max with AI

    In the gym, your 1 rep max is the most weight you can lift for a single repetition.

  4. This is a quick run through of the setup and configuration needed to use Firebase Auth in a Chrome extension built with Plasmo in offscreen documents.

  5. These are some Dockerfile examples for setting up a Scrapy project with uv and Playwright for quick web scraping and automation.

  6. This is the last post in the series on developing browser extensions with Google Sign In using Google OAuth.

  7. This is a continuation of the series on developing browser extensions with Google Sign In using Google OAuth.

  8. Google Auth in Chrome Extensions is fun 😏 If you’re building OAuth into a Chrome Extension you’ll likely start with chrome.identity.getAuthToken and then realize that it doesn’t work in other browsers outside of Chrome, even Chromium-based ones like Brave.

  9. The Scrapy crawl stat logs are useful for tracking and monitoring the performance of a spider.

  10. When crawling websites with Scrapy you’ll quickly come across all sorts of scenarios that require you to get creative or interact with the page that you’re trying to scrape.

  11. I’ve been using Lemon Squeezy to handle subscription billing in several projects.

  12. In GitHub issues, if an issue is transferred to another repository or if the issue is converted to a discussion (or vice versa), the URL reference will change.

  13. I recently added support (v1.1.0+) for bringing your OpenAI API to dossi as an opt-in feature.

  14. dossi is now open source

    dossi, a browser extension and web app to keep track of your own private GitHub notes is now open source.

  15. About

    I sit between developers and product, translating what developers actually experience into what gets built.

  16. If you want to change to the application type from SSR to SSG, or SSG to SSR, then the platform and framework type needs to be changed in your application settings in Amplify Hosting.

  17. This post steps through setting up Amplify Auth with the Amplify UI React library in a Next.js SSR application.

  18. This is a quick follow to Deploying Next.js SSR and Prisma on Amplify Hosting.

  19. In this post, we’ll set up and deploy a Next.js SSR app that uses Prisma as an ORM with a PostgreSQL database.

  20. Just a quick note on configuration changes needed for the Slack provider to save the authenticated user correctly using the Prisma adapter.

  21. This post is part of an ongoing series focused on tips and tricks when building fullstack serverless apps with AWS Amplify.

  22. This post is part of an ongoing series focused on tips and tricks when building fullstack serverless apps with AWS Amplify.

  23. This post is part of an ongoing series focused on tips and tricks when building fullstack serverless apps with AWS Amplify.

  24. Open RStudio from the terminal like VS Code A quick Zsh or Bash function to open an RStudio project from the command line similar to opening Visual Studio Code with: $ code .

  25. The last step in creating a Vue component library plugin is to publish it as a package.

  26. Deploy VuePress on Netlify

    Documentation is no fun if it isn’t public.

  27. Documentation time!

  28. At this point, we have a structured approach for creating new Vue.js components and consolidating them into a single module export.

  29. Overview In this post, we’ll step through the initial project structure for your Vue components.

  30. In this series, we’ll focus on structuring a Vue component library as a plugin for use, and reuse.

  31. The settings below are my defaults for Vue development in VS Code.

  32. The initial jump into the netlify.toml file is a bit daunting at first, especially if you only want to make a small change.