A Hexagonal Blog (in JavaScript)
Somehow I came across a good example of applied hexagonal architecture in JavaScript, it's CΓ©sar Alberca's blog. He has all the source code on github.
Somehow I came across a good example of applied hexagonal architecture in JavaScript, it's CΓ©sar Alberca's blog. He has all the source code on github.
A while ago I optimized some images for the site you are looking at, by using the
webp format
because I had forgotten to do that, and
PageSpeed Insights
suggested to do so.
I forgot how to do that, so I am writing it down now. Read on if you also want to know how to convert any kind of image to webp and embed it in your site.
Archijs
describes itself as "A package to test javascript architecture".
TL;DR - it is not ready for use yet, I would not.
What advice/rules I may give to junior developers about the Ruby on Rails app design?
This article is not only relevant for Rails developers, but also very general. I feel that rails devs need more support here, because Rails makes it especially hard to use magic.
Make sure to open the hood and understand how the engine ticks!
The original article where Alistair Cockburn describes Hexagonal architecture is the best intro and a good read, no matter what year it is.
Finally I learned how to abort a fetch, see the post React useEffect and fetch API by @Jaime.
Coming across "unary operators" might happen in JavaScript, or (m)any other programming language(s). A couple examples for what is a "unary operator".
In JavaScript you may find: +1
, -42
, + "1"
, !true
, delete x
. All those are unary operators as you can also read on
MDN
and in the
spec. But what does the "unary" really mean?
And why is 1 + 1
not using a unary operator?
I am gladly using codeberg (as github alternative) for as many projects as I can, really support their mission. "Independent and powered by your donations and contributions".
I struggled a little bit to figure out the URL that works
for a package that is not on npm yet, but exists just as a codeberg repo.
I am currently working on a React Native app that uses redux saga heavily. My main concern with it is the traceability of code that goes together, the modularization. It is hard, if not impossible to know what belongs together, what is needed in combination with what.