Interesting article.
Our PO often almost demands estimations from us. Usually I am already responding in a best/worst case fashion.
In the end PO only seems to remember the best case and takes it as commitment. Since I was fooled by this a few times, I am now collecting a paper trail and am quiet reluctant, when giving "just a ballpark figure".
My key takeaway was, that estimations mostly aren't about accuracy or getting a value, but rather managing people's expectations and navigating corporate politics.
"According to France’s privacy watchdog CNIL, Youtube users only had to click once to accept cookies, whereas refusing cookies took multiple clicks.
CNIL’s complaint stated that Google purposefully made the consent mechanisms more complex to push consumers to accept cookies––a clear violation of the GDPR’s requirement that companies provide equally simple ways to opt into or out of data collection."
So these dark patterns are officially violating GDPR.
However there are still tons of websites implementing this.
Can you elaborate what is improper secret handling in your opinion.
I personally use sealed secrets, but I think generation of them is sometimes tricky (tied to the namespace etc
I am not sure if this kind of transparency will be beneficial to the employees or not.
Like the article mentioning there is leverage missing for salary negotiation.
That mean, that some folks would earn less assuming the model was adapted everywhere. However it may clean up inequalities.
In the end people are divers. There are hires with only 2 years delivering better results, than one with 5 years.
The article reads like the author uses Big Tech as synonym for only Google and Facebook/Meta.
However is is making some good points about the future of ad driven revenue streams those two companies heavily rely on.
In the end I think it will definitely not be big tech in total. Apple, Netflix, Airbnb and Uber e.g. have other revenue streams
In my opinion implementing strong interfaces and good modularization is something, that we should talk about more, than doing Microservices. In the end it might be easy to rip of a Microservice, when needed, if the code is well structured.
Actually you are right, that was my first gig after college, however I actually know of Swoole and researched a bit, but when codebase and tech stack is already given to you by people worshipping their choice you haven't a real handle.
Like written above my statement was meant like: there are people out there, the are so in love with php, that they would (ab)use it for everything.
I also know it is my fault to hired with these guys in the first place, however it definitely teached me how to not do things.
Sorry for unclear phrasing. I meant I used php from 2018-2020.
And honestly I don't know why to use php for the task.
I started at the company 2018 and the tech stack was given.
A good compensation and praising like "PHP has changed and now supports types etc." let me take the opportunity.
My bad, because it took me a lot of time.
I needed to do benchmarks were actually PHP turned out to have comparable performance in the scenario under test (concurrent consuming of message Queues and heavily write operations to databases), however it took more than 4 times the effort to get there with php.
In the end I resigned and switched to a new opportunity doing golang solving similar issues.
My point is, that there are folks out there (ab)using PHP for all and everything.
And finally php has made a lot of improvements but it is just catching up with other languages. There are still a lot of libraries, that still use older versions and probably never will get updated.