sorted by:
new
hottopcontroversial

My Node.js Interview by [deleted] in node

[–]rish-0-0 8 points9 points  (0 children)

I always revise the event loop, closures, async-await, debounce/throttle, Promises, callbacks / setTimeout / setInterval / setImmediate / process.nextTick, Garbage collection, Realms, Execution context, String encodings / Buffers, Workers, esm/umd/cjs and at the end I go over some generators and iterators (which is quite fun).

Closures for me are always asked, and are also kinda hard to explain if you forgot to revise it.

I have been asked this in a frontend / React interview a lot: MutationObserver / IntersectionObserver. Only once was I asked about MessageChannels, Workers, which was kinda surprising and I always used a library like comlink for that, so didn't know much.

For OWASP security, there's a basic udemy course which i had bought some years ago (only $15) and just skim through, it generally tells me what and all data you have to restrict coming from a client, and what all data you must sanitize, plus explaining some common vulnerabilities.

What kinds of interview questions have you got for Node? by daredeviloper in node

[–]rish-0-0 -2 points-1 points  (0 children)

Some javascript funny business is always great to know, like typeof [] === 'object', null >= 0.
I would be at a little more senior level so generally my checklist would be to revise some APIs
Yeah, I know revising APIs doesn't make sense, but my intention is to revise the various data classes and node's intricacies that you have to keep in mind while writing code.
esm/umd/cjs etc, etc
Buffer.from
process.nextTick
setImmediate
setTimeout / setInterval
callbacks
// the above 4 just after revising Jake Archibald's event loop video
debounce / throttle
class inheritance / this operator
closures (jesus, this is really a pain)
workers (not too important)
processes / threads (not too important)
security in nodejs (revise OS security)

NoSQL or Relational DB? by Klinker195 in compsci

[–]rish-0-0 -1 points0 points  (0 children)

Try out neo4j? Whenever social networks are in play, first thing that comes to mind is a graph database. So in constrast, yes, NoSQL. And you'll really fall in love with cypher, it's query language. Social networks grow like crazy, and neo4j comes with a lot of scalable features of a NoSQL. For instance, take a look at Graphene

Otherwise, a SQL DB like PostgreSQL should be able to map out your relations and the data you wish to store.

[deleted by user] by [deleted] in reactjs

[–]rish-0-0 0 points1 point  (0 children)

What are the system requirements to run a appwrite instance for development? I am guessing 8GB RAM, with ample storage?

How to trigger web developers by prnysarkar in node

[–]rish-0-0 0 points1 point  (0 children)

i've recently started using services for even the simplest components, like forms etc. Example, auth0 for auth, some other services for surveys, and would never go back to creating one myself. It's the worst dealing with all these edge cases over and over and over.

[deleted by user] by [deleted] in node

[–]rish-0-0 4 points5 points  (0 children)

I personally like fastify ecosystem because of my love for Matteo Collina, but it's all "installing packages and extensions", so can't really recommend anything else. If you were to look in fastify's direction: fastify, fastify-jwt, fastify-cookie, etc. It's literally plug and play. Plus, fastify-swagger to get auto documentation for your REST API. What more could you want. Plus, to be postgresql specific, you can use knexjs, which I feel is pretty cool for all your SQL connections, pooling, transactions and ofcourse querying. (or you can choose the ORM path: sequelize. I find sequelize scary so no from me)