I’ve asked ChatGPT to search and summarize the highlights from the DevDay 2023 promoted by OpenAI earlier today, and I gotta say they line up very effectively with what I saw.

The topics listed below are the result of asking for a list, extending it a couple of times, filtering some items, deepening each topic and listing references, and finally edited to make it cohesive and better stylized.

If you’ve ever marveled at the linguistic prowess of OpenAI’s ChatGPT, you’re far from alone. But behind the allure of its capabilities lies a question that any pragmatist looking to integrate it with their application will inevitably face: What’s the price tag on this computational eloquence? Whether you’re a developer with an idea, a business leader looking to automate customer interactions, or a hobbyist keen on exploring artificial intelligence, this article aims to dissect the often convoluted pricing structure of OpenAI’s chat API.

Building a search component poses an interesting challenge and opportunities for exploring React’s features and various optimization techniques. This article walks through a basic implementation and expands into key areas where performance and usability can be improved - such as an auto-complete functionality, debouncing the input, and memoizing the results. We start with a simple Search component that consists of a text field for the query and a button that triggers the search.

As web applications sprawl and user interactions grow in complexity, keeping track of global state can become daunting to maintain. This challenge is often met with the use of libraries like Redux and MobX, but they come with their own labyrinth of opinions and learning arcs. A simpler alternative can be achieved with the mathematical simplicity and precision of a State Machine. This article delves into this issue comparing popular solutions, followed by a quick explaination of the theory behind the concept and provides an example implementation in React.

I set out to refresh my portfolio and decided to document my journey to the realm of Static Site Generators. Gatsby was chosen as the initial route, as it is a popular modern option for those accustomed with the Node and React ecosystem. However, insurmountable memory issues during production deployment led me to reconsider that choice. Then I reverted the course to trusty old Jekyll, which has kept this ship afloat for almost a year.