I am now feeling old for using Capistrano even today. I think there might be “cooler and newer” ways to deploy, but i never ever felt the need to learn what those ways are since Capistrano gets the job done.
It’s not a simple plug in and stream product, but ever since replacing Sonos with Control4 we’ve been incredibly happy. Josh on top of it for voice and it “just works”.
As I said, not a direct comparison, but starting to think consumer level stuff like Sonos and HonePods just doesn’t have the right incentive structure anymore to deliver the level of quality we all seem to be asking for.
Half-Life, and Valve generally, were such a big part of my life in the late 90s and early 2000s. Exploring this definitely brings back a heap of memories.
Not sure if it is new or not, but really glad this history has been preserved.
We just went down the rabbit hole of trying to migrate to Microsoft 365 Family with custom domain. You (officially) need to move your domain to GoDaddy, which was unfortunately a blocker for us as they don’t support our domains TLD.
From what I read DKIM also isn’t offered on Family which is disappointing. Business plans get expensive quickly when you want Office apps as well.
I found some info on setting up DNS for other providers, but it isn’t officially supported and for something as important as email I don’t want them randomly breaking it one day, which they could since they expect all customers to be configured through their API integration with GoGaddy. No need to advise in advance of MX host changes etc when it’s supposed to be entirely managed by them.
I understand their target demographic here might not be super technical, so the deep integration with godaddy makes sense, but would be nice for a supported advanced user pathway too.
v11 update was the straw that broke this Tesla owner's back. We just purchased a new EV from another manufacturer and are selling the Tesla.
I'm so glad there are an increasingly larger range of EVs to choose from. In Australia the choices are comparatively limited still, but more and more are becoming available. When we got our Tesla the choices were really Tesla or cars with really limited range.
I used to think I'd get used to the touch screen and muscle memory would allow me to do things while driving easily. Hasn't happened - I use the steering wheel buttons for changing the temperature, but everything else requires taking my eyes off the road for too long.
Test drove the new car and was surprised by how better physical buttons were. The cognitive load to drive it was so much less. After years of Tesla touch screen land, I think I'd forgotten how much easier and usable traditional interfaces are.
So not only that you need special training to ride the Tesla pony, but it's also objectively worse even for those who put in the effort. It's not even like switching to Dvorak, it's like switching to Qwerty in a world where everybody uses Dvorak.
As an alternative viewpoint, I also have a Tesla and a "normal" car, and I don't find the Tesla requires any "special training" or is objectively worse.
Things are in different places in different cars. Switching keyboard layouts would be significantly more complex.
Can you share which car you ended up buying? I was gung-ho on Tesla for a long time, but the lack of physical controls in the 3 is a dealbreaker for me.
It sets the expectation for a lot of people that they should be checking and responding to messages at all hours.
I’m a night owl, I like to do thought work after the day of busy meetings. I don’t want my direct reports feeling like I expect them to reply at 11pm when I send them an email, or on Sunday if I’m working. So I schedule it to arrive in the morning or in the next work day instead.
You can tell them until you’re blue in the face, but actions speak louder than words.
If you don't want people to feel that this is expected then just tell them that you don't expect immediate responses.
By scheduling the message to send in the morning you are just setting the expectation to be awake and respond then, you aren't removing the issue you mentioned, you are just picking a different time to set the expectation.
There is an expectation that during core working hours people will be somewhat responsive. That will differ org to org, and perhaps in your org there are no set working hours. In that case my current approach probably doesn’t hold as much.
My experience has been that simply telling them not to feel obliged to respond doesn’t really cut it, and people feel obligated regardless. This may be a cultural thing too, and again will probably differ company to company and region to region.
No idea why you want to miss out on an opportunity to show your boss that you're working late. The only use-case I see for scheduling is to do the opposite and schedule it in the night to pretend to be "going the extra mile" by working outside business hours.
I’m talking about the opposite where you are the boss. I don’t send emails at night so my staff don’t feel the expectation to be constantly checking and replying to me. Just because I work weird hours doesn’t mean I expect my staff to.
If one of my team sends too many emails at weird hours I’d make a point of talking to them about their workload and life balance at an upcoming 1:1 to make sure things aren’t getting too off track.
Because teams want a cultural expectation of normal work hours. I am often a night owl and I’ve sent messages late at night and gotten asked my manager if I’m overworking and since then try to avoid doing it unless I’m responding to someone.
You're getting downvoted but I have known a lot of people who will set non-urgent emails to delay send at 7:30-9pm so they look like they are working late. It's silly but most of those people ended up getting promoted.
Thanks for the list! The one that I've read (about half) are great, which makes me want to read the rest. (Just Culture and Accelerate, in particular, are so great I think I'm going to consider adding them to my list as well.)
The town of Mallacoota is essentially surrounded by a moat of fire at the moment. The residents are trapped inside this ring, one part of which is the ocean. The Navy, as well as supplying, are evacuating people off the beach as there is no other safe way out of that part of the country at the moment.
You can definitely just send the trucks in. Whether anyone will be actually alive a few minutes later is a very different proposition. I'd advise against it. People underestimate just how hot fire can get and what it actually means to operate next to and within an environment that is essentially a furnace. A furnace that stretches all around you and up into the sky and is moving all the time. The air is hot and thick. Your protective gear is hot. Embers are flying around and if they touch something flammable they become a fresh new fire.
A few "trees across the road" means many minutes to clear that road. Which is surrounded by fire. Or soon will be. That wind could change any minute. Or the logs are still smouldering or on fire. So you clear the road and then a few hundred metres later you reach more fallen trees and massive ditch you can't pass. Now the fire has crossed the road behind you.
I haven't gotten a chance yet, no. My recent projects have been tiny things in PHP, or large ancient things in Java. Looking forward to an opportunity to try it out, though.
Interesting, my own experience has been the opposite. From what I remember v1 was constantly broken, initial v2 was not much better but now everything is very smooth all the time.
I had massive issues with Airdrop 2 when it first came out. After many lengthy chats with Apple support it managed to resolve itself. All I can offer and a working solution is signing out and back into iCloud on each affected device. This of course comes with the resync penalty.
reply