On my last job, the company was using NewRelic (for two environments we was using at the time) which had an ok cost and "suddenly" we'd been forced to use Datadog which costs way over for our budget and after the person responsible for the change and integration see the estimated high costs, started to cut everything possible to keep it low. So, our tools degraded and we wasn't able to test things on staging and collect metrics like we was when using NewRelic. FinOps is certainly a good approach, but we need it from the start!
Haha appears some managers change only the address but the behavior is the same, I already worked on a place where we had to use free heroku addons besides the paid PostgreSQL and the dynos
On my last job, since the project is based on Ruby on Rails, we implementei this https://github.com/toptal/crystalball and additional modifications based on the gitlab setup. After that, the pull requests test suite runs pretty fast
When I was in the college, I'd made some consultancies to final students from CS degree which don't know how to program and even bad, the project was a simple copy and paste some classes, change attributes and manually test it. So, the main problem I'd seen was they don't have the ability to figures out the system and it's a basic expectation!
I think many issues goes with bad version or, in some edge cases, not vendor dependencies. I'd good and bad experientes on multiple programming languages, some bad examples:
- bump patch or minor version from a react package but the maintainer rewrote the entire project breaking a lot of things, following semver it's bad to expect things don't break like that for such version;
- another example, the ruby gem is removed/yanked from rubygems.org and you'd to find a fork available
On the end, we need to ensure the good practices from software engineering about tests and good release management, the last btw is decades old
I liked the line of thought from the author and suffered similar points at a much small scale! Once, I'd planned to do a migration, which moved multiple columns from one table to another and the associated data, but calculated wrong the time to complete and the amount of CPU/RAM, if I'd the right tools, probably I'd scheduled better and planned a better approach.
The concept is great, my father, which is a doctor, bought a minibook at a newsstand about HTML for dummies. At the time (maybe 98 upto 2000) explaining the good old markee, blink and other tags besides the basic HTML document composition. So, I think learn HTML is for everyone!
About public healthcare it's pretty similar on Brazil! Many people can't pay for specialists, exams and etc. So, they have to go early morning (when it's dark yet), wait on long queues and many of them when finally is attended the local doesn't have more vacancies and need to go back another day.
Couldn't agree more! Yet, the companies still continue to hire those experts and dump on us the issues when things goes wrong. I'd at least two times at the same company, the CEO called me and want me to fix things built by the experts!
