Hello Fakorede Abiola , Thanks you for your response. After reading it and the code again and again, I understand that I've missed a point: app.route take as many middleware as we want. Your cache middleware is scoped here and not global to all the app: app.get( '/repos/:username' , cache, async (req, res) => { So everythings is good. Thanks again for your article, this is a great discovery for me :)

Hello, Thanks a lot for this article 👏 Some though: IMHO, it's better if cache is agnostic. I mean if developers doesn't have to worry about how and what is cached while developing api. Another thing: I don't understand why you put the cache retrieve code in a middleware. I might be wrong, but right now, if I query GET /lmao/:username , and if the cache exist, looks like it will return me the same response as GET /repos/:username . So why not putting all the cache logic inside the cached route. I.E app.get( '/repos/:username' , cache, async (req, res) => { const { username } = req.params client.get(username, (err, data) => { if (err) throw err if (data !== null ) { res.send(data) } else { try { const response = await fetch( `https://api.github.com/users/ ${username} /repos` ) const data = await response.json() let repos = data.map(item => item.name) // save the repos to redis using the username as key and with an expiration client.setex(username, 60 , repos) res.send(repos) } catch (err) { res.status( 500 ) } } }) });

Could you be more precise about your servers and what are the different mail systems you are using ?

And this is how it looks like

Wow, so you're using terminal mail clients! Thats... wow! You're pretty beardy, right? :p I think I'm gonna try in a few days, but not sure it will do the job because most of my mails are html and not pure text. You're totally right, create something simple is rather complex. I think I can describe my ideal GUI mail client like this : One window One thing at a time, we are not build for multitasking Minimalist and content first (just like medium is for blogging) Tons of keyboard shortcut which are integrated to GUI (no need to look for the shortcut in obscure manual or on the internet) Yahoo mail is pretty good on the last point. Newton mail (but they're closed now) on the third. Thanks for the compliment :)

Hello, The same question came to my mind few months ago. And I found a (partial) answer in a podcast. It wasn't about code, developers or this kind of stuff, it was about "what advise would you give to yourself at 18". The speaker was Autodisciple, a french youtuber . Here's his answer: I'd say that the world is bad designed and the people don't really know what they are doing. Even the adult. Even people who look assured. Things are imperfect, unfinished. And people who look confident, assured are mostly just faking it. IMHO, this is pretty funny how this answer applies well to developement. We're trying. We're doing our best. And every day we're failing. I don't really know what clean, semantic HTML code is. But here is a list of things I do to make my HTML as clean as possible : Think about what I'm going to create How is it going to interract with the rest of my html Write something which work Wondering about the role of all that divs. Is it a header ? A nav ? A section ? Is there an HTML5 element which cover this role? Asking myself "why have I written this?" Is my code valid ? Improve things Go to 4, until there is no more improvements which came to my mind. Thank you for reading. Note: I'm a beginner when it comes to writing in english, so feel free to give me your feedback :)

I think the subject is more about open spaces than open office. But both subjects are interesting :)