davidsergey
We use microservices, because we acknowledge that we don't know how final product would look like, and we mitigate risks associated with adding and removing unknown number of features.
Facebook was creating clone of Twitter, well known product, well known path. There is no need for microservices.
But I guess that most people are not interested in open platform, only tinkers like us are. And if they make it officially closed platform, they don't have to deal with our complaints, when something does not work, or more likely underperforms.
And if somebody would present this article to me – I would not take it seriously. The fact that author is using very interesting language when refering to React and Angular does not help. I'd love to hear customer-centric or product-centric reasoning. * Don't use SPA because customers hate it when you change entire app on them. * Don't use SPA, because customers of our particular product require faster turn-around. * Don't use SPA, because they are harder to test in our organisation.
Obviously my BT keyboard did not yet connect to the computer, since it was before BT drivers loaded or something, so I had to buy a wired keyboard to press "F2" and proceed. Would be nice to have 2-3 buttons right on a case to interact with BIOS. Or you know…load BT drivers.
These days I order food, knowing that it will allow me uninterrupted work (I'll just receive a package and get back to work). If I have to interrupt my "flow-ish" state anyway, I'll just go out or make an omelette in 10 minutes.
Context: I live 10 minutes away from a high street in London.
Very glad that we've got superb TypeScript datamodel, but jesus, it took a long time.
But I'm software engineer, and I didn't know about it. I don't think most (as in 95%+, even in tech) people would know difference to care. My point is visibly – firefox seem to be just as ad-hungry as competition.
They could be better behind the scenes, but customer wouldn't know it.
That said, I don't understand, why would somebody use Firefox instead of Chrome, Edge, or Safari if they ad in-browser ads.
I was so tired completing user stories that I knew will be either too expensive to maintain or plain useless that decided to climb up towards the source, and help people set up requirements and measurements loops.
So yeah, why do people hire software engineers who are extremely good at analytical thinking, and then try pre-digest every bit of requirement?
>12 or 24 months is stable, technically? Hm. Faster iterations are better, usually, again if we understand the context, but I see a lot of companies that are too quick to go into full panic mode. An example would be recession – If you plan to invest for the next 60 month, and a recession hits you on month 20, the right choice would be to ignore the inputs, and keep investing. Those who pull their assets when prices are low usually lose.
Quick or long iterations are not be all solutions, once always have to keep the context in mind and use first principles to understand what is that we are doing, and trying to achieve.
It's effectively a job of an exec / director to make bets. Hopefully they are educated guesses, but there are times when somebody just have to flip a coin too.