The main benefit list gives you comparing to vector is a stable memory. This is often an important property. But lists are slow with an element access. This problem is solved by deque.
Therefore, I argue that alternative to deque has to have a stable memory property. Otherwise, you can just use a vector.
This implementation is trying to do so, btw, but for some reasons it operates with a raw memory under the hood instead of just holding a vector and rotating it here and there. Such approach is unnecessary complicated and error-prone
Ah, I see the numbers in the example are the numbers of matched rows, not a total number of rows... Make sense. I do not work with databases, did not know that you should pay attention to the order here.
The article states that order of join matters because then nest loops differently. But we still go through entire loops everywhere. Where do those numbers in the example come from? If we have 1000, 20 and 200 elements in 3 loops, algorithmically, it does not matter in which order you iterate. Complexity is always 1000×20×200.
rr looks interesting. It should be useful for debugging race conditions or something "random based": once you record the issue it becomes 100% reproducible in your debugger.
Will try it next time when I have such issue. Thank you!
Manger mode is "hire good people and give them space to do their job".
Founders mode is Steve Job's way "<same as manager mode> + make those good people feel important".
There are many founders, who failed to scale their sturtups, because they did something wrong. But it is not because they ALL in fact did the same mistake. It is just many of them can match their particular mistake with the vague concept of "bad manager mode advice".
This TUI looks pretty, but I cannot imagine situation, when I would actually use it and be ready to pay for it. Probably I am not living in a right environment for it. But in my experience, either people are happy with something truly minimalistic or they try to please a user with GUI right away.
For example, YouTube link in the article showed a possibility to display table with highlighting cells. Why would I need that as TUI? Probably if I want to navigate through table with highlighting active cell I would also need a bunch of other stuff and eventually I would need a proper GUI.
If you want your code to contain specific assembly instructions, code in assembly. Programming language by design is an abstraction of a higher level and when you use it you shouldn't care that much about actual assembly it produces.
When I say "naturally" I imagine the situation, when you stand in a "social desert" and there are two people in front of you. They are the same age, the same profession etc. But the first one is from your native country and the second one is local. In order to communicate with the second person you need to use language you are not native in. There is also some cultural/mentality difference, naively you are not sure which topics you should avoid in discussions. Obviously you will feel a lot of pressure, at least in the beginning, speaking with the second person. When there are no such hurdles between you and your person. You can use your language, you know where the social borders are etc.
In order to make a connection and support it with the second person you need to overcome those hurdles. They may be not big for you. But my point is that they are there. And if human has a choice they naturally chose the easy past.
My point is that if you migrate you rather need to seek (work on) making friends with locals.
When, surrounding yourself with people from your country will happen by itself.
Of course I do not know what is the situation for everybody.
But this is what I see around me.
In the article they talk so much about funding schools which will improve immigrant literacy. But I think, that funding is not the problem. When you migrate to a new country you just naturally get into a bubble of your nationals. Its much easier to make a connection with other people from your country because of your common experience and culture. Then you just live in this bubble. You are in US, but all your free time you are still talking in your native language with your friends and family. Probably, read news and books in your native language too. So English language just needs to be on the bare minimum to give you a job. Hence low English literacy results.
Yes, stack is much better than long-long log. After some time you're log becomes too big and if it contains some points you want to return to, then they are just lost. And if you lose something in it you stop trusting it and do not use it. At least this is my story.
Yes, I completely agree. The story sounds like fairytale: migration was announced to happen in 3 months and in 4 months it was done by removing old API.
Where are all those clients, who are happy with current API performance and do not want to spend their money on making API owners life better? What happened to them? Did the company just decide to let those clients go?
At large scale, when your company developed a significant tech debt (~1mln lines of code), you will especially value people who understand what is going on in all that code. I am afraid, that with smaller teams "renewing teams" will be too quick for new joiners to grasp what is going on. I mean, everyone from "old" team will leave before newcomers are ready to own the product.
Therefore, I argue that alternative to deque has to have a stable memory property. Otherwise, you can just use a vector.
This implementation is trying to do so, btw, but for some reasons it operates with a raw memory under the hood instead of just holding a vector and rotating it here and there. Such approach is unnecessary complicated and error-prone