Readit NewsMy workaround to this has been to email the company telling them I want to cancel. Once I either don't get a reply, or get a reply saying "just call us and we'll cancel!", I dispute the next charge with American Express and have the email record of trying to cancel. I believe they also offer a "stop allowing charges by this merchant" feature that cuts off future charges.
The best workaround (imho) is just using virtual cards. My Venture X allows me to create a virtual card on the spot restricted to that merchant where I can also enter an optional lock date. If I want to try something, I just create a new card and set the lock date to the next day. Even if I forget to cancel, good luck charging my card :)
As a Google engineer, it's really saddening to see the Welchism completely taking over Google. There are more than enough examples showing focusing on bottomline to increase shareholder value doesn't work in the long run, but it's obvious the current leadership doesn't care.
Seeing all this stuff I can’t help but think that if programming doesn’t just come naturally to your brain such that you would need all this stuff, then you’re probably better off pursuing something that does come naturally.
This books isn't about that at all. It's more about how our brains work and how we can use it to make our code better (read: easier to understand).
If anything, the book tells the exact opposite: you can write your code so that it's naturally easier to understand.
This was one of the best books I've ever read. I'll actually go ahead and say this is probably the only book I can confidently say that every professional programmer* should read.
You know how sometimes you can "smell" something doesn't seem right? Or seems a lot harder [to understand] than it should be? Yeah all those little intuitions we develop through experience is explained using "brain science" in this book.
*: More specifically anyone that writes code in a collaborative environment.
It indeed is hard, and a good code search platform makes life so much easier. If I ever leave Google, the internal code search is for sure going to be the thing I miss the most. It's so well integrated into how everything else works (blaze target finding, guice bindings etc), I can't imagine my life without it.
I remember to appreciate it even more every time I use Github's search. Not that it's bad, it's just inherently so much harder to build a generalized code search platform.
ayberk commented on BBC: Big Tech jobs have lost their glamour bbc.com/worklife/article/... · Posted by u/test1235
I'm torn about this. I've been in FAANG for a while now, and while I do think I'd be more successful/happier at a smaller company (and I actually was), I don't think "smaller" tech is necessarily going to be better, especially right now.
Maybe we should just accept that these are just jobs, and no glamour is necessary -- so maybe big tech jobs losing it is not the worst thing. Let the talent spread and create more "glamorous" jobs.
ayberk commented on jj init – getting serious about replacing Git with Jujutsu v5.chriskrycho.com/essays... · Posted by u/chriskrycho
I hope they change the binary name since "jj" is a common <ESC> binding for vim users :)
ayberk commented on Tear up unused parking lots, plant trees danrodricks.com/2024/01/2... · Posted by u/jbrins1
I think he really hit the nail on head here:
"Part of this is a result of poor planning and ordinance-making that long ago overcompensated for the wide use of automobiles. Henry Grabar, a staff writer at Slate, mentions this in a book published last year, Paved Paradise: How Parking Explains the World. ”On a national level, certainly, there’s far more parking than we need,” Grabar said in an interview. “There are at least four parking spaces for every car, meaning that the parking stock is no more than 25 percent full at any given time. And some of those cars are moving at any given time, so parking may be a good deal emptier than that.”
I'm still reading this book, but so far it's been one of the few books I'd recommend to anyone. I try to be as stoic as possible, but contents of this book has managed to actually anger me. It makes it so clear that how much corruption and bad policies impact our lives.
Now it’s just a way to make the number perpetually go up, sucking every last drop of value out of the system.
Plus the complete lack of vision or strategy from Google’s senior leadership.
I didn't like working at AWS for the most part, but I have never seen Google-level dysfunction there. There were a lot of times I disagreed with decision, but I could always understand the reasoning behind it. On the contrary, I can't explain most of the decision being made at Google. The enshittification from the very top has been amazing to watch, even for someone like me who joined only 3.5 years ago. Both senior and mid-level leadership lack a clear vision and the execution has obviously been horrible. Google needs a hard reset if they want to be successful again. I'm not buying the "too-big-to-fail" bullshit.