"Fuck yooooouuuuuuuu. Fuck you, fuck you, Fuck You. Drop whatever you are doing because it’s not important. What is important is OUR time."
Most NPM packages.
Dear Google Cloud: Your Deprecation Policy Is Killing You
41–50 of 417 posts
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#42> I have been inexorably pushed away from GCP, towards cloud agnosticism.
On a side note I think this is what all of us should be aiming for. Every time someone on a team I'm working for starts trying to use some very complex tool that a SaaS/cloud has built for us I always urged them to look for a simpler solution.
Do you really need AWS Lambda/kinesis/etc or can you write your code and deploy it onto our cluster as a normal service/api/control loop?
If you make it really easy to write code, deploy it, and monitor it, you'll often find it's way less devops time to write your software as apis/control loops than it is to use a large amalgamation of cloud services. I also haven't found a good way to unit test cloud services and their interlinking.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#43So much ranting, yet not a single example of a GCP product that Google has actually killed. Got examples?
I mean, there's stuff like Python 2 support being sunset on managed services, but as Yegge himself points out that's on Guido, not GCP.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#44Earlier quoted context omitted.
Then why don’t you move to google if you know they pay better?
I've studied hundreds of hours, failed HC for full time once and I've concluded that I'm mentally incapable of doing so (I blame my parents due to the slight heritability of IQ). "Just move" is something someone without any empathy for other people's circumstances would say - most people aren't capable of "just moving" as if the only concern is choosing an employer.
Man you really shouldn't be so hard on yourself. These coding interviews aren't IQ tests. If it's any help, a good recommendation from someone in a company would probably be a stronger signal than a leetcode type question.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#45Earlier quoted context omitted.
> Fun fact for you - if I get promoted this year at Amazon to L5, I'll _still_ make less than a new grad at Google. This doesn't appear to be close to true based on levels.fyi, unless you're severely underpaid for an Amazon L5.
Levels.fyi is good, but it's still polluted with TC's from multiple regions in the US (California + NYC have higher base and higher TC by 15% due to taxes). In addition, promos always happen at the low-band and aren't negotiated. There's very likely some intersection between high-band L4 and low-band L5, and I'd be there when/if I promo. The only way to get out of the band is to get a high raise during evaluation sea…
Huh. At this point I'm quite curious if I know you.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#46“ it’s well-known that they refuse to host (as a managed service) any third-party software until after AWS has already done the same thing and built a successful business around it, at which point their customers hold them at gunpoint. But that’s the bar, to get Google to support something.” This isn’t true, of course. They supported managed Kafka before AWS did: https://cloud.google.com/confluent
Gcp doesn’t have a 1st party Kafka offering. Confluent cloud is still 3rd party just with some nice integrations with GCP.
If you have an issue it’s not GCP support or GCP’s eng job to fix the cluster. There’s real service uptime implications of this.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#47It's odd to see an article emphasising backwards compatibility, but not a single mention of Microsoft (I even ctrl+F'd the page source to check!) They've regressed a bit in the recent years but I'd still consider MS the gold standard for back-compat. I have Win32 binaries I last modified over 15 years ago, small (or perhaps tiny - size measured in KBs) utilities that I use daily. They worked perfectly on Win95, and s…
You missed this:
> I’ll also give a shout-out to our friends in the Operating Systems business: Windows, Linux, NOT APPLE FUCK YOU APPLE, FreeBSD, and so on, for doing such a great job of backwards compatibility on their successful platforms.
I share your desire for stability. I don't necessarily mind frequent updates for security reasons, but I'm getting to the point where if things are changing in big ways often, I'm just not going to use it --- I no longer find enjoyment in running on the upgrade treadmill, it's just work.
That said, I don't see a lot of hope for our outlook. Most people don't seem to have a concept of completable software. It would be nice if it were bug free, but getting to the point where the cost to fix bugs compares to the cost of leaving bugs as known issues is doable.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#48I'd be interested in some concrete examples of things GCP have depreciated. I'm an (admittedly fairly light) user of GCP and haven't come across any myself.
Personal experience: I have to support an internal tool for a company in app engine. The contract is part time and I have to prioritize what issues to fix. The answer is usually "those caused by Google deprecating something". The nosql db some hyped individual has chosen years ago - "deprecated, we don't bother with solving bugs there". Email service: "it is in python2, but not in python3, look for management approval to use external service". File storage: "this library is deprecated, use whatever service is fancy now". Task queues: "nope, we are changing the api and calling it cloud tasks now, so please refactor all of your files to use the new semantics".
The list goes on and on.
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#49Earlier quoted context omitted.
Then why don’t you move to google if you know they pay better?
I've studied hundreds of hours, failed HC for full time once and I've concluded that I'm mentally incapable of doing so (I blame my parents due to the slight heritability of IQ). "Just move" is something someone without any empathy for other people's circumstances would say - most people aren't capable of "just moving" as if the only concern is choosing an employer.
My feeling is that getting a job is like dating, a mysterious mix of luck skill chemistry etc, there are some rules but you can follow the rules precisely and still end up losing just because of some odd misfortune. However if you try long enough and put in a solid good faith effort, long enough being unspecified and possibly after you die or go broke, you generally end up with something decent.
That long enough part is the kicker and that terrifies me in every job search (to the extent I have sometimes jumped at the first half decent opportunity, and agreed to salaries below my potential). I find it does help to apply often and everywhere and not be invested in any particular opportunity.
With dating they say every failed relationship is a step toward finding the right one, and I think that same principle applies to job interviews.
Anyways, that’s my two cents
Re: Dear Google Cloud: Your Deprecation Policy Is Killing You
#50It's odd to see an article emphasising backwards compatibility, but not a single mention of Microsoft (I even ctrl+F'd the page source to check!) They've regressed a bit in the recent years but I'd still consider MS the gold standard for back-compat. I have Win32 binaries I last modified over 15 years ago, small (or perhaps tiny - size measured in KBs) utilities that I use daily. They worked perfectly on Win95, and s…
I went googling for some Raymond Chen examples of the great and terrible things Windows does in the name of back compat, and came up with this old thread: https://news.ycombinator.com/item?id=13450160