2024 Tax
11h
1827
Biden’s new tax proposal is wild
Layoffs
Yesterday
37422
Google CFO confirms 'large-scale' layoffs (Apr 17)
Tech Industry
18h
2447
Go woke, go broke: Google fires 28 employees involved in pro-Hamas protest
Health & Wellness
12h
4399
Why are women naked in gym?
Tech Industry
Yesterday
48980
Goog Employees Arrested
How is the work in devops? What % of development and operations activities will be there? Will this needs to work in shifts?
But costing your projects should be the same because developers are just as efficient when they’re dividing their time dev’ing and ops’ing
Before launch it’s 100% development, post launch it’s 100% operation. I hope people realize devops is mistake after all these years.
Any idiot that thinks developers can churn out the quality code when they’re gathering requirements, testing their own code, supporting it, and losing sleep for on-call, isn’t going to realize that DevOps is a huge time-sucking mistake.. It’s like making your surgeon do your 24-hour care after your surgery. It’s like putting your mechanic on cashier duty. It’s like making a judge walk each prisoner to jail (or release). It’s like forcing a factory worker to sell the car after he builds it. It’s like a windmill farm worker coordinating with my refrigerator maker to check the light bulbs in my refrigerator. It’s like the chef at a restaurant following me home to ensure my BM is okay after finishing my meal. It’s like Trump inspecting border walls
.. actually that last one is a bad example because it should involve someone who has enough attention span to follow through and admit they may have made a mistake in releasing the product
Agreed. It *seemed* to work and unfortunately it happened in a successful organization. Then people thought it really worked and started to copycat. People didn’t realize that it could’ve be better without devops. No, it doesn’t work.
Is the prevailing wind now that Devops does not work? Knew this before it was widely adopted. People acted like Op’s and service management was something without skill - which is untrue, which is why so many Devops teams fail... next on he dumpster fire should be Agile - rates of change are simply too fast to have any focus on decent test cases - least of all building strong code coverage.
What about sites reliability?
Site reliability is another name for ops. Google’s doing it because they are smart enough to protect their engineers from operational bullshits.
Am DevOps, AMA.
Wrong way of thinking about DevOps. You should think of you built it, you deploy and support it is the future. Separation of dev and ops is going away.