276 karma · joined February 11, 2016
I've worked in large companyies very successfully using TBD and releasing quarterly to enterprise customers using our software on their systems.
But as of late I've switched back to just making regular ol' drip coffee in a cheap coffee maker with Chock full 'o nuts coffee.
As easy as an aeropress is compared to other quality brewing methods, I still find the drip machine much easier -- load up the filter and water, walk away, come back and pour a cup. (Plus, I can't seem to get my aeropress not to also pee down the side of the mug as I press it down)
Somehow, my coffee experience hasn't degraded at all. No, it doesn't taste the same, but to me it's still totally fine, and almost always a better coffee than the drip I get from most coffee shops.
Amazing coffee in an aeropress is just a white whale for me.
That about sums up most things Google does for developers.
At WeWork tech is so secondary to their requirements. Sure, they can make it more and more required -- just like fridges do these days. But for WeWork the tech is about as necessary for you to derive value as a touchscreen on a fridge is necessary for you get get value from the fridge. _Just because it relies on technology doesn't make it important to it_
What am I missing here? There was no harassment of any sort. Alternative headlines could have been:
"Twitter has an algorithm that helps you gain more followers"
"Twitter has an algorithm that helps you drive awareness"
"Twitter has an algorithm that helps you get more twitter followers for your cause or business"
"Twitter has an algorithm that expands your social impact from beyond your sphere."
---
In other news: public posts on public site go.... public.
This actually reminds me a LOT of making websites around 2006 - 2012.
I'd imagine you could use Segment (or source(s) that plugs into it) to accomplish much of this.
Routine is useful. My life is full of mini routines, although not necessarily making as cohesive as a picture as they could, there are certainly plenty of gaps.
I have a bad problem where things go to shit if a normal "auto-pilot" task of mine has to changed.
Simple example, I always have my keys in my pocket, I feel for them as I walk out the door. They're there, I continue. Same thing with my truck (it has manual locks) - I feel for the big plastic on the key, then close the locked door.
However, when leaving the house without pockets (in dirtbike gear), there is room for things to go wrong for me.
I can't just check that pocket. So I either have to replay putting the keys in my bag or not be lazy and check the bag.
I've had to learn to not be lazy and require physical proof... because last time it turns out they were indeed in the bag, _but the bag was in the house_.
My extremely limited knowledge of diesel engines is something like "they go a ton of miles, then need a major overhaul, then go a ton more miles". If you're at some kind of major overhaul milestone, then I could see the response you're getting.
'99-ish Ford kicked off the Super Duty series, but it isn't sufficiently interestingly old to a lot of people, so I can understand their the why-bother attitude.
But it's not free, you just said they're paying you for at least 8 hours no matter what. Sounds like you're saying certain things are below that plumber and he won't do them, but still wants to get paid.
Mind sharing what you like about it, why Asana wasn't enough?
Non shitty logging takes minimal time, like, so minimal. It will make many bugs and customer issues trivial to fix. In the least, use something like Sentry. Makes up a lot for not logging because it adds the context with your uncaught exceptions.
I get smoke wafting in from outside via window air conditioner - and I think my neighbor occasionally smokes in his room.
I'm planning to setup another to better cover my open floorplan.
"We are investigating an issue with Google Kubernetes Engine node pool creation through Cloud Console UI."
So, it's a UI console issue, it appears you can still manage
"Affected customers can use gcloud command [1] in order to create new Node Pools. [1]"
Similarly, it actually was resolved in Friday, but they forgot to mark it as so.
"The issue with Google Kubernetes Engine Node Pool creation through the Cloud Console UI had been resolved as of Friday, 2018-11-09 14:30 US/Pacific."
Was having manageable lower back pain when my pack suddenly froze up. It feels like your body is just stuck, and moving it will cause your spine to rip out - all from just muscle spasm tightening it.
It causes this mortal fear to rise up inside you. wondering how long you'll be incapacitated, living in pain, and useless.
Fortunately it was about 3 days like yourself, but you don't know that when it starts.
You keep the ability to exercise a fair amount of control, easily, and clearly. And you don't sit inside really opaque execution environment.
Sure, the scaling and provisioning of those Docker containers is opaque, but I'm much more willing to deal with it at that level.