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.
I see a potential problem, see if I can solve it. See if it's already being solved, if not I pitch the idea to few people. If atleast 50% got excited. I pick this idea to build
I dont take more than a month to validate any idea
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.
Python, Erlang and then Clojure