UlisesAC4

What about a top to bottom and then a bottom to top design ?

That is my biggest grip, Google is known to do great experiments and then closing them. Better wait to more info and maturity.

That is why you keep a dream journal. To understand what is real and what is not in the long run.

It is ok. But keep in mind that in the overall graph BTC trend is upwards.

You only lost if you were actively trading on December.

Actually yes. Doctors have told me that I should wait til 25 to see If I am candidate to eye laser operation because that is the average age where people stop developing his muscle eyes.

Guys your opinions are great, I just hope that if you really care about FF leave you comment in the blog post too.

You do not really see it lately.

Well if we can say things we can say that any abstraction is magic until insiders are seen, the question is how much abstraction you are willing to take in order to feel comfortable.

You have a point, in a more relax comment, how much learning is enough? As personal opinion just reading the documentation of your tool of choice can lead to vast amount of knowledge, default params, recommended practices, all of that is included in a well documented project, but how much should I dig into the rabbit's hole when using node?.

In my opinion node is better if you have experience, Express is so bare ones that you are going to write almost all of you functionalities.

I am also kind of a beginner but I could not stand the way the node ecosystem is spread apart. Do not let others fool you about how npm is a chaos. The problem is the bare boned node ecosystem.

I literally spend hours reading the documentation of passport js for account creation because it did not make sense to me, it implied that you knew how to do some validation, then I had to choose the hashing algorithm of storing passwords, setup the email verification system and even roles and I was about to implement everything by hand. When read about other frameworks like hapi and feathers. Checked them did not really offered that much and ditched js for backed for good.

If I want to do everything from ground I would better choose Phoenix (erlang web framework) at least app would be real multithreaded by default.

I am really frustrated but do not get me wrong node is beautiful, Middleware idea is incredible but you are alone. But There is not even a way to exclude Middleware from routes unless you do a hack as a middleware.

In my opinion node has advanced greatly by the advancing of js itself, but once you start to program you are kind of alone. You are better using rails (not my favorite does a lot of magic) or some python tech (I am using Django btw).

Maybe you could see them as in memory files. Or buffers of files.

Exactly, remote working is not about tech expertise but more about effective communication.

That is something bad at our industry. Managers or whoever do that decision believes that being senior automagically makes you a genious, when it can be the other way around, the more senior you are, the more averse to change you are. I doubt that senior could easily change to remote lifestyle after years of onsite.

People must learn that anyone can be remote, the thing is that everyone must agree to communicate better instead of more.

That point is a little bit bad worded. It is more pointed to old school managers who think that by controlling working hours they are controlling productivity.

After all in remote work productivity is measured about communication, issues , commits and pull requests done.

When javascript Is disabled you just loose the pwa features, pages are full loaded as html.

For SSR you are sending the HTML text instead of JSON. Time ago you needed nodejs for SSR I do not know the alternatives today.

You do not have to go that far to that kind of apps, fou can check f-droid or fossdroid for free and opensourcer android apps.