krisdol

[1]: https://m.youtube.com/watch?v=CDeG4S-mJts

Spinning up multiple components generally takes a few seconds once the image is built, as it is not much more involved than spinning up a new docker container of an image that is already pulled. Each image might take a couple of minutes to build, but because there are no hard dependencies between images (unlike libraries in a monolith) any amount of them can be building and deploying in parallel.

It doesn't really matter how fast the "whole thing" can be built-and-deployed before, because in a monolith, you need every developer building and deploying their own library versions as well as the monolith. Meaning, not only do your changes to production have to wait in the queue for everyone else's, but you unintentionally pick up work from other folks along the way. That road leads down to the environment you describe, where every developer needs at some point to spin up their own dev instance and live on their own branch just to be able to test in isolation, resulting in an organization that requires merging, building, and deploying several times along the way in different environments before the change finally reaches production.

I also described a perfect use case of an HTTP interface (or RPC, or whatever language agnostic interface you want to use, it doesn't matter to me and rarely matters in the real world). Data science work is often in a different language space than web work. I'm not going to bundle native Python/R/Clojure dependencies with my node.js apps. It's too much work to maintain those bindings between runtime versions and app versions. I'm not going to force Data scientists to use JS because the library ecosystem is targeted toward completely different use cases. With HTTP or RPC or whatever transport, each team can use the best tools for the job.

I can think of a few off the top of my head:

1. Being able to scale individual, smaller components rather than one giant application

2. Being able to build-and-deploy any one module much faster than one monolithic bundle of local dependencies

3. Universal interface with language-agnostic applications. Do you need to expose big data statistical analytics, but can't find data engineers that are comfortable with Java/Node.js/Go? Doesn't matter, hire the best ones and let them use Python/R/Clojure. HTTP doesn't care.

Interesting that for me it was the startups that provided good machines while the enterprises provided 4 years old lenovo laptops with not so good batteries not the specs needed to use a VM effectively

Natural selection... More like dumb luck your ignorant persona was born privileged and not having to work your way up through the social structure of a foreign country several times. If it wasn't for public assistance we'd be dead or arrested for god knows what we would have done to put food on the table.

Social services exist to keep you safe from the poor just as much as they exist to keep the poor able to move upward through socioeconomic class

Although a more effective solution would be to scrap zoning laws and actually make the suburban blight towns convenient for workers and pedestrian residents.

When you hire for a company you want your dream team to have a diverse background of ideas and experiences but that doesn't mean you let them work on the goals and products they worked on at their previous employer with whatever processes they want.

Edit: to be clear, I'm not sure the specific minaret law is a downside from my experience, but that is not to say that your overall point on populist reforms is invalid. I was just focusing on the specific law.

Why not? If I want to wrap a callback function in a promised sequence, I don't see a way around it. Please don't suggest importing bluebird/promisifyAll because that only teaches me how to avoid thinking about the problem, not how it's actually solved, let alone why it's a problem to begin with.

  function promiseMeFoo() {
    return new Promise((resolve, reject) => {
      asynchronousFoo((err, out) => {
        if (err) return reject(err);
        return resolve(out)
      });
    });
  }

It seems incredibly arrogant to me that interviewers assume there is only one way to solve a problem, and that is by brainstorming on a whiteboard first. I don't feel comfortable standing up in front of the class to present a solution. I feel far, far, far less comfortable if it's a coding-related solution. I did significantly better, like pretty much 100% success rate on coding components when I could hit keys rather than display my chicken scratches on a whiteboard.| I move code around a lot as I prototype and it takes quite a bit of training for me to adjust to not having the option of restructuring as I code because the medium is a whiteboard or piece of paper. And every time I erase something my level of anxiety and nervousness just grows.

>As early as the end of September 1997 the employment offices were given instructions to systematically withdraw the work permits for Bosnians. Thousands of Bosnians, many of whom had worked in Germany for years, received duplicated forms, in generally restrained wording, notifying them that the employment centres had to first check whether there was a German available for the job.