Saying goodbye to Microsoft - What I gained, lost & learned while working for Microsoft. (medium.com)
It wasn’t a ‘golden cage’ I was in, it was a bubble of illusions that popped once I signed my dismissal papers. Illusions of importance, mission, friendships and luxury.
I’m 28, have learned to put myself first and spent plenty of time on self care, enough to be able to share this publicly and hopefully not to make the same mistakes in the future.
The author shared her story of being burned out by putting work as first priority and oversee life. Work is not your identify, and you need to build up your own life. When some day you need to switch job, or role, you will not end up regret not spending time for family, relationship, hobbies, and life.
Why Google+ Failed (onezero.medium.com)
Google Plus didn’t fail because Facebook is invulnerable.
It failed because of deep flaws embedded in it from the very start.
It’s no news that Google is shutting down its products or services. The author worked in Google+ team and has seen how Google+ end up being one of those. He not only told us the issues and problems that caused the failure, but also what prevented it from being fixed or corrected along the way from product perspective.
Stop Learning Frameworks (sizovs.net)
The longer a technology is on the market, the safer investment it is.
Don’t rush to learn new technology – it has a high probability of dying.
Time will show which technology is worth investing in. Time is your best advisor. Learn to wait.
Remember – frameworks, libraries and tools come and go. Time is precious.
I loves to learn new technologies, which often turned out to be just learning new frameworks/tools. I have learned Angular, Vue, and React just to build a blog in different ways. Instead of spending time learning new frameworks/tools, we should focus more on fundamental things (Web, HTTP, REST, JS) that empower these frameworks.
Microservice Architecture at Medium (medium.engineering)
At Medium, our technical stack started with a monolithic Node.js app back in 2012. We have built a couple of satellite services, but we haven’t created a strategy to adopt the microservice architecture systematically. As the system becomes more complex and the team grows, we moved to a microservice architecture in early 2018. In this post, we want to share our experiences of doing it effectively and avoiding microservice syndromes.
It’s been years since we started talk about switching to microservices architecture from monolithic app. It’s worth reading how large scale companies have successfully went through the switch and what are their principles and strategies to get full benefits of microservices.
More stories about embracing microservices:
This Is Silicon Valley (onezero.medium.com)
Everyone wears Patagonia and North Face, everyone has AirPods hanging from their ears, and everyone goes to Lake Tahoe on weekends. And everyone talks about the same things: startups, blockchain, machine learning, and startups with blockchain and machine learning.
As Jeffrey Hammerbacher, a former Facebook executive, told Bloomberg, “The best minds of my generation are thinking about how to make people click ads.”
The Silicon Valley author described is exactly what I see in the Silivon Valley. What’s more is some smart minds I see are also talking about buying homes, stock investment, and job promotions. People I see are homogeneous, they have similar backgrounds (Computer Science), similar jobs (Software Engineers), similar hobbies (Hiking, Board Games, Skiing in Tahoe), and similar interests (tech, stock, house, promotion). If you are not living in Silicon Valley, let’s go with the author and get to see the sides of the Silicon Valley you may not know.
UTC is Enough for Everyone, Right? (zachholman.com)
It turns out humans have had a long, long history of poorly dealing with time, so when you hammer your head against the wall trying to deal with a timezone bug, well, you’re just the last in a long, long line of human beings that are terrible at all this! Congrats. You’re pretty unremarkable.
The author talks about long history of time and how horrible we have been dealing with time. To solve this problem in programming, we need to make it as simple as possible and leverage standards (e.g. UTC, ISO 8601).