Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 32
  1. What cheap code solves

    A few months ago I built a coffee tracker.

  2. The map coding left behind

    A year ago, I started delegating most of my coding to AI agents.

  3. I've been chasing better code since I started programming.

  4. Earlier this year I joined Sana and opened the backend codebase.

  5. Newsletter to RSS feed

    Earlier this year, I shifted back to RSS feeds for my news consumption.

  6. I often need to juggle between different Git settings depending on the type of project.

  7. I have recently migrated my website to host it on Vercel.

  8. Back to RSS

    Following the recent events at Twitter, I've chosen to delete all my content and discontinue using the platform.

  9. Engineers need to write well

    In a remote-first company like Acast, written communication is an essential skill to master at any level—from IC1 to CEO.

  10. The code below is a pattern for client-side applications or for serving static files.

  11. AWS CloudFront Functions

    AWS recently released CloudFront Functions—a new serverless scripting platform that allows us to run lightweight JavaScript code at the CloudFront edge locations.

  12. API Gateway-first approach

    The "API Gateway-first approach" is the idea that, in the context of an AWS cloud stack, when we build a new service, we first consider using API Gateway.

  13. During a presentation—held internally at Acast by my colleague Daniel Grefberg—I discovered a one-line change that reduced by 2 minutes the execution time of my current project's CI pipeline. - working_directory: ~/my-project-name + working_directory: /mn…

  14. Write more, but shorter

    I recently stumbled upon an article from Mike Crittenden, Write 5x more but write 5x less, in which he shortly explains why we should write more, but shorter.

  15. <span class="intro"> For the past six months, I have been using <a href="https://roamresearch.com">Roam</a> as my primary application for note-taking and knowledge management.

  16. API Gateway has built-in support for caching endpoint’s responses.

  17. Accessibility is often viewed as making your site work on screen readers.

  18. I wrote about the component library side of our design system at Acast.

  19. How to keep small PRs

    Pull Requests (or PRs) are an essential part of team collaboration.

  20. Enzyme has been my weapon of choice since 2016 for testing my React components.

  21. In this article, we will touch upon how to use useCallback, useEffect, useReducer and useState hooks.

  22. In this article, we will walk through the setup of GitLab CI/CD pipelines to run the tests and deploy the latest version for each merge on master.

  23. When working in a team of developers, it's important to share what you attended to achieve with your code and why you did it that way.

  24. VSCode as a Vim editor

    In 2013 I started to use Vim as my primary editor, the journey hasn't been without frustration, but in general, I really enjoyed using it.

  25. In this article, I used TypeScript v3.

  26. Redux is widely used and a great way to manage your data flow in a React app, but a common complaint is that Redux requires a lot of boilerplate code.

  27. When we work in a team of developers we all have our way of programming which may end up with an archaeology type of codebase, where we can guess who has written which part just by the way the code is formatted.

  28. Promises are convenient to deal with asynchronous code in JavaScript, but at first glance it can feels tedious when it comes to unit test them.

  29. "Code formatting is important.

  30. Vous pouvez lire la version française de cet article. npm has played an important role in Node.js success.

  31. Component(1) is a front-end package manager created by TJ Holowaychuk.

  32. From Sublime Text to Vim

    Sublime Text has been the first text editor I really enjoyed to use.