224 karma · joined September 5, 2018
- gamalarcossi+hackernewsletter _at_ gmail.com - github.com/officer-rosmarino - linkedin.com/in/galassim
I was hoping for more real life examples where you can see the effects of concurrency parallelism.
Check out mobileJazz, they seem cool and were looking for a software engineer proficient in Nodejs etc, so it might fit you.
I was looking to submit it myself, but I have a stable job right now and I think I won't lose it so it could be of more help to someone else. Hope it helps you.
Buona fortuna, e se vuoi scrivermi la mia email è gamalarcossi at google
Bar, pubs etc will be closed.
Stores will be open like 8-18 and will be closed on weekends.
Honestly I don't understand how this is going to help: say that 100 people go to the store in a week.
- 10 Mon
- 10 Tue
- 10 Wed
- 10 Thu
- 10 Fri
- 25 Sat
- 25 Sun
Those 50 people that go on Sat/Sun will go during the week, resulting in
- Mon 20
- Tue 20
- Wed 20
- Thu 20
- Fri 20
- Sat 0
- Sun 0
How is this going to help?
This is interesting, but how do you do it? I mean, unless you are "lucky" enough to find a moment when everyone people are stressed and reacting badly, how do you evaluate that?
In general, without "interviewing" someone who already works there, how do you think just walking around is enough and how do you evaluate that?
What would that be?
I love hiking but I often rely on mountain huts here in the alps, limiting tent
1) I don't really get the "100 Users: Split Out the Clients".
It definetly helps in terms of understanding your customer profiles, whether they prefer the mobile app or the web interface for instance, and it might help from a usability point of view, but how does this help scalability per se if the API layer stays the same?
Splitting client happens, obviously, at the client level..
2) Also, I don't understand "This is why I like to think of the client as separate from the API."
Who considers the client and the API as the same thing?
You can consider the API as the client of the DB, sure, but why would you mix the user client and API together?
3) Caching: here I lack some knowledge. "We’ll cache the result from the database in Redis under the key user:id with an expiration time of 30 seconds". I assume that every access to Redis will not refresh the cache (aka reset the counter), otherwise you could potentially never get an updated data, right?