We were talking to the reptile caretaker at the Abu Dhabi zoo and we learnt that
- snakes are actually cuties. And more like babies. They do not have strong fight or flight ability like mammals. If they get hurt, they go into a corner and just give up
- they're extremely misunderstood beings. When a snake is hissing, it is because it it actually very very frightened.
- their eye sight is very very bad. They detect mostly by that body heat. And they've a very hard time detecting friends vaa foes. A ball python actually curls into a ball when tensed up. The caretaker had to pet the snake to help it relax.
A bit ingenious to say we do nothing when you have CloudFlare in front of your servers. Cloudflare by itself can automatically detect and handle DDoS without explicitly activating the Under Attack mode.
The comments here are needlessly pessimistic and dismissive of a new data flow paradigm. In fact, this looks like the best NoSQL experience there is. SQL while is a standard now, had to prove itself many times over and also was a result of a massive push by few big tech backers.
Rama still looks like it needs some starter examples - that is all.
From what i could gather reading the documentation over few weeks... Rama is an engine supporting Stored Procedure over NoSQL systems. That point alone is worth a million bucks. I hope it lives up to the promise.
My Remarkable 2 E-Ink notebook for sure. I'm a pen and paper notes taker - R2 has been extremely useful in freeing me up from the pen and paper books. And my notes are searchable and tagged!
Functional programming combined with the process dependency tree of Erlang.
Up until a point functional programming with PHP or Python were always littered with small state time bombs which could change at any point in time. Only after thinking about state explicitly in Erlang based programming, was it clear how the state enclosed in OOPS is a total digression from reasoning about state and behavior separately.
On the contrary, I've seen product teams assume the pain of the consumer and relay the same to engineering; and then engineers having to push back on the insane requirements.
Nevertheless, product which work in an agile model without collaborating with tech is doomed to fail
Brother, my 2nd startup was 5 years old, lost a ton of money and time. Had to kill it and pivot to a 3rd one at 36. This one is doing better, much better.
It is tough. But if there was no risk involved in doing a startup wouldn’t every tom, dick and Harry have done it already? You put yourself through big risk for asymmetric gains, isn’t it? This pain is the risk that played out this time.
Just take a break; get onto the salary wagon for a few months; gain back your mental peace and confidence and then come back.
Right. Having the client handle everything only after receiving events / data from server works great for a long time till one comes against the real-time multiplayer games. Without doing some lerping on the client side the client is always going to run a few ticks behind the server.
There are far too many variables to say that server side calculation is the only real way to program.